Command line for max players is still incorrect

[Mavick]

As I mentioned in my ticket, you had it originally at sv_maxclients, now you have it as si_maxclients. The correct command is si_maxPlayers. I think that is actually the correct command too, because when I throw it in the new server.cfg you guys came up with, and restart, mine goes back from 8 man to 16 man. I've also added it to the server_objective_standard_vs.cfg as well. Figured I'd mention it anyway tho, so other people aren't provoked to having to set that in the other .cfg's.



And on that note, it seems odd to me, that the server is basically being told to use the "standard" playmode/ruleset, which by default is 8v8, yet I'm still having to tell it to set a 16 player limit.

[Mavick]

Actually, nevermind. For some reason everytime players join it, it goes back to 8 max players. Not sure why. Maybe the Command Line being incorrect is causing it.

[Brett]

Thank you for letting us know. It looks like when Eric updated the command line, he just changed "sv_maxclients" to "si_maxclients" rather than doing the full command. There was some misinformation posted on the game panel forums, which is where "sv_maxclients" came from. I went ahead and adjusted the command line to use the proper command.



I am not sure this is the cause of the issue you mentioned though. We have about 25 servers running with this command line, and all of them are showing as 16 slots (minus the ones using campaign/etc configurations).

[Brett]

I just checked your server.cfg and everything looks the same as everyone elses except yours is has the slots set in the config and is running 8 slots. I see players connected right now. If you want to reply to your ticket when it is a good time, I will be happy to tinker with it to see what the issue is.

[Mavick]

I won't be able to sit here today to figure it out, but tomorrow I will.



In the meantime, I looked at the xfactor servers in the steam list, and I see one that's running a full 16 players, actually on it, server IP: 208.122.57.242:27017. I'd be curious to know if there is any difference at all between my setup and whoever has that one, including the server_objective_standard_vs.cfg, because I've modified that one too and maybe that's causing a problem. The only files I've edited at all are the server.cfg and the server_objective_standard_vs.cfg

[Mavick]

I removed the maxPlayers setting from the server_objective_standard_vs.cfg and so far it's run fine through a map change, with players on it. I'll check it again later tonight and update my ticket if necessary.



Thanks for changing the command line tho Brett, I don't know why it would possibly affect mine and not others, but perhaps that was it. So far I've been very happy with the service here, considering the brave new world I'm sure these Brink servers are providing you guys lol.

[Mavick]

I just came across something else as well:



http://www.splashdamage.com/forums/showt...hp?t=25255



Apparently they misprinted the server hijacking command in the guide. I looked through your command line and also the server.cfg, and they both have the incorrect command. I changed mine in the server.cfg, but you guys will have to change the command line as well for custom ones.



Correct: net_serverAllowHijacking 0

Incorrect: net_allowServerHijacking 0



I think what might have happened is that I got up, someone had co-opped my server earlier (I think it defaults to on) and it stayed, for some reason, at 8 players. It was running correctly earlier because I was staying on the server, so nobody could co-op it, until it filled up.

[Brett]

Mavick, I appreciate you providing us information that you find. I also noticed that people were talking about this on other forums, and apparently si_maxPlayersHuman was defaulting to a value that it shouldn't be for them. Most of our shared game servers seem to be running 16 slots fine, but our dedicated machine clients seem to be having the issue of the server going to 8 slots when someone joins.



Can you try setting si_maxPlayersHuman 16 in your server.cfg to see if that fixes that issue?