|
Notes |
|
|
|
Is there at least a "SUDDEN DEATH" message when the timer is hit?
Also, with sv_maxlives it's not completely obvious to declare a winning team. What should be the criterion(s)? The team with the highest cumulative "lives left" count wins or the team with the most players alive (this may be different)?
If tied on the first criterion, the teams with the highest cumulative health left wins? |
|
|
|
|
When normal LMS has a timer on, Sudden Death does appear when the clock hits 0 regardless if sv_suddendeath is true or false. Not sure if this is also bug because with sudden death off, the round should end with a tie and no one gets the win point. With teams enabled, there is neither a timer or a SD message.
For deciding the winner, if sv_maxlives is 1, then the team with the higher player count would win the round. If there is only 1 man per team left, then it would be treated the same as LMS with the player with the highest health winning. If both players have the same amount of health, then SD true means the first to take damage after the timer hits loses and SD false ends in a tie with no win point rewarded.
With a life count of anything greater than 1, the winner of the round should be the team with the highest cumulative amount of lives. When the timer hits, if there is an equal amount of lives on both teams, then sudden death would begin and the first team to lost a life would lose the round. With SD false, the round would end in a tie with no win point awarded. |
|
|
|
(0011317)
|
|
AlexMax
|
2015-01-07 02:19
(edited on: 2015-01-07 02:20) |
|
I'm not so sure that it's a good idea to have two different means of counting the winning team for different maxlives settings. Here's my vote:
- Winning team has most total team lives
- If tie and SD disabled, winning team has most total team health, or tie.
- If tie and SD enabled, both teams have all live players reduced to 1 life and 1% health.
|
|
|
|
|
After considering what you suggested, I can agree with the criteria of using most lives followed by health then tie with SD disabled. If this was the rule, then it probably would be easier to code and keep things consistent regardless of sv_maxlives. Plus with maxlives=1 (the standard), then using cumulative lives would still translate to 'body count' such as the case of 2 red vs 1 blue when the timer hits.
As for SD being on, I considered different scenarios that could occur and I think the idea of the first to take damage (which is how LMS handles is) should carry over to Teams. The whole point of SD is to have a 'sudden' end to a tied round. In addition, this would lead to full consistency across team and non-team lms.
I'm not sure it's worth the coding effort to explicitly drain down health and lives to 1. But if it is coded in this way, SD in regular LMS should also be drained explicitly as well. |
|
|
|
|
|
Another LMS Sudden Death idea - take damage per second as if you were standing in slime. |
|
|
|
|
|
No. That idea is awful and it would probably be more work to implement. Your original suggestions are far better. |
|
|
|
|
|
Gonna agree with Rust here. |
|