[TF2 Feature Request] Add mp_timelimit_min
to control the min time limit required to switch maps after a round ends
#1206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notes:
mp_timelimit
Proposal
Currently, once a round ends and the time limit is below a hardcoded 5 minutes, the map will change rather than playing out the remaining map time, and if
mp_match_end_at_timelimit 0
then the full round would play out before switching maps. This PR proposes a new convarmp_timelimit_min (default: 5)
that allows server operators to change the minimum time limit to any number they'd like. The requirement ofmp_timelimit_min
being under the value ofmp_timelimit
is still required.Theory Behind The Old Hardcoded Value
In September of 2007 there was a patch note
When a round finishes, if there are less than 5 minutes left on the time limit, the server now goes ahead and switches level right away, instead of going into Sudden Death.
, wherein the hardcoded minimum time limit was most likely to have been added. There was also a comment left next to the code explaining why this change was made.If there's less than 5 minutes to go, just switch now. This avoids the problem of sudden death modes starting shortly after a new round starts.
Sudden Death will trigger under two conditions
mp_match_end_at_timelimit 1
and the time limit hits 0mp_stalemate_enable 1
and a stalemate occursWhy I Believe The Hardcoded Value Is Outdated
In January of 2008,
mp_stalemate_enable (default: 0)
was added for server operators to decide if they want Sudden Death to occur. However, the hardcoded minimum time limit of 5 minutes still takes effect regardless ofmp_stalemate_enable
's value. This doesn't make sense because the comment suggests that the minimum time limit of 5 minutes was set specifically to prevent Sudden Death from occuring when rounds were given less than 5 minutes to play out. In 2025 where server operators have the choice of enabling Sudden Death, and when Sudden Death is off by default, it makes sense to me that server operators should have the ability to modify the minimum time limit. For example, iftf_timelimit_min 0
maps can run the fullmp_timelimit
and start new rounds up until the very last second before changing maps. Any rounds which start in the last few seconds could be considered a bonus round withmp_match_end_at_timelimit 0
. Should servers want Sudden Death enabled then the default value ofmp_timelimit_min 5
is there to accomodate them. Servers have been running with this minimum time limit for over a decade and a half so I believe having the default value mimic the hardcoded value of 5 is justified.Video Preview
Note: When the scoreboard appears and my weapon disappears, that means the server is going to changelevel.
mp_bonusroundtime
is set to 5 secondsmp_timelimit_min_demonstration_1.mp4