On 13/02/2013 09:05, ics wrote:
I don't think anyone dynamically does this
You think stuff and it happens like in this film? http://www.imdb.com/title/tt0078158/
Wow.
Valve's recommendation is 24, so simple solution would be that if server cvar sv_visiblemaxplayers is changed, Valve will check if it's over 24 slots or below and adds increased_maxplayers immediately, thus alerting quickplay system and everyone should be happy, except the people who try to avoid that tag.This also works two ways, if you have 27/24 players, increased_maxplayers is added during mapchange, making the server 27/27 and then the server loses 8 players, you will be left with 19/27 (or possibly 19/24) with increased_maxplayers tag, thus giving quickplay penalty.
How are we happy if we join a server via quickplay or the server browser, after reading 24 slots, expecting and wanting a vanilla 24-slot server and then the player count goes up mid round?
Messing with the slot count mid-game has to be a no-no as far as quickplay and the server browser goes. Your server has to be either 32 slot or 24 (or something else). You can't say "it's 24 slots until we get 24 people and then we change it to 32" in any reasonable, honest way.
It's clear the only reason someone says "it's 24 slots...oh no, it's actually 32" is to trick either quickplay or TF2 players into joining the server.
It would need a tag if there were any valid reason(s) for it other than gaming the quickplay system (but I doubt there are)
-- Dan _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
