|
Notes |
|
|
|
|
I definitely agree with this. IMHO, server hosts should have as much control as possible. |
|
|
|
|
|
I'd like to hear as much opinions on this as possible. It certainly won't be a problem to add a CVAR that lets the server admin disable the reset. But if I'm going to touch this, we should rethink the feature as a whole. For example I think it's very strange that the reset is only done in game modes with teams. Why shouldn't it be applied to all competitive game modes? |
|
|
|
|
It sounds like it was implemented as a built-in "map rotator", minus the rotator part. If that's the case, then IMO, it should affect all game modes, competitive or not. But apparently it only resets the current map, according to what ant1991331 said.
What is the practical purpose of the reset?
IMHO server hosts should at least be able to disable or enable it by choice, no matter what the game mode is.
Going further, if it was intended to be a map rotator, you could make a separate map list and specify which maps to change to after x minutes. And add an option to randomize the rotator. |
|
|
|
|
I'm guessing it was implemented so that players wouldn't be joining a game that has already been in progress and then left unfinished (IE, blue team rage quits at 10 kills, while red leaves shortly after with 40 kills), instead they'd be joining a freshly started game.
For modes like Deathmatch or LMS, I don't think it matters because player scores are cleared once they've left the game. In Team modes, the team scores aren't reset (or deducted by the amount of what the player had upon leaving) when the players left. |
|
|
|
(0000341)
|
|
unknownna
|
2010-10-11 14:14
(edited on: 2010-10-11 14:28) |
|
In that case, IMHO the server should just instantly reset the frag/point counter every time the last player in the server leaves. Would anything break that way?
|
|