It does. There's multiple ways to change it after that command line option is set. With or without plugins. Most of which have already been discussed in this thread.
Again, there's better things for Valve to focus on than this. All the big GSPs already had this value monitored for years. There's no reason to lock anything further now. On Tue, Jan 3, 2012 at 6:11 PM, PharaohsPaw <[email protected]> wrote: > IIRC what you set on the commandline *IS* the highest you can set it, and > although I'm less certain about this, I don't think any attempt to set > maxplayers to a higher value than what was set on the server command line > will work. > > > > > You can change the cvar maxplayers before the game starts. > > When you put this two lines in your autoexec.cfg the maxplayers cvar is > > overwritten and fixed (tested with css): > > > > maxplayers 64 > > map de_dust > > > > Maybe Valve can lock maxplayers, when it is set with -maxplyers in the > > start command. > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
