29.01.2015, 00:29
I dont really see why anyone would need that. Browsing through 500 players in the list to find a friend or something would take much longer than joining the server and asking if your friend is around in the chat.
However, I cant understand how the 100-player limit should prevent server overload. Actually its just 5 times that much data for a 500 player server. The data for 500 player names (500 * 24 bytes) + 500 scores (500 * 8 bytes) would result in a ~17kb big network package, compared to ~3.4kb for 100 players. Sure this would be quite a big difference for small servers, but 500 slot servers already cause several megabytes of upstream per second. The 14 extra kb for player data would barely make up a single percent, even if queried several times per second.
And the servers query-spam protection already works well enough to cause no trouble. People cant abuse it to lag the server by spamming 100-player requests, so they also wont be able to lag it with 500-player requests.
So imo, if people really think they need to list all 500 players, why not give them the option to do so? After all they can still reduce it again afterwards if their server/connection isnt strong enough for that.
Alternatively you could add an additional querycode to get all players, that gets sent if the player really scrolls down in the player list.
However, I cant understand how the 100-player limit should prevent server overload. Actually its just 5 times that much data for a 500 player server. The data for 500 player names (500 * 24 bytes) + 500 scores (500 * 8 bytes) would result in a ~17kb big network package, compared to ~3.4kb for 100 players. Sure this would be quite a big difference for small servers, but 500 slot servers already cause several megabytes of upstream per second. The 14 extra kb for player data would barely make up a single percent, even if queried several times per second.
And the servers query-spam protection already works well enough to cause no trouble. People cant abuse it to lag the server by spamming 100-player requests, so they also wont be able to lag it with 500-player requests.
So imo, if people really think they need to list all 500 players, why not give them the option to do so? After all they can still reduce it again afterwards if their server/connection isnt strong enough for that.
Alternatively you could add an additional querycode to get all players, that gets sent if the player really scrolls down in the player list.