订阅以下载
High Ping Kicker

Version: 2.1
ID: 6802773
Build independent + supports automatic .entry loader system
Fully Server-Side

Gives the server administrator the option to enable kicking of clients who exceed a max ping limit, set by the administrator.

NOTE: A bug in NS2 is currently stripping away the custom max_ping setting from ServerConfig.json, which requires you to manually enter an sv_maxping value into the console every time the map changes...

The ping check ONLY occurs when the client first connects to the server, i.e. once, to avoid kicking clients in mid-game. Once the client has finished the connection process, the check starts after 30 seconds and will continue to multisample for 20 seconds to achieve high accuracy. Before being kicked, the client will receive multiple warnings and explanations.

Set the ping limit in milliseconds either by issuing the concommand sv_maxping VALUE, or by adding the settings entry max_ping in the ServerConfig.json file. To disable kicking of high ping clients, set the limit to 0.

I recommend that the max ping is set to stepping multiples of 33 ms near multiples of 50 ms.
These values are: 200, 300, 400 ms etc. I.e. so effectively multiples of 100 ms!
This is due to the fact that player updates are sent from the server to clients in the frequency of 20 Hz = 50 ms / update. Player updates are sent from the clients to the server in the frequency of 30 Hz = 33 ms / update. Other latency values would have no different real positive effects on gameplay experience but make it more inconsistent.

If you don't know what max ping to set, I recommend 300 default, and 200 for aggressive elimination of negative lag compensation (good if you want to have a more local player community and play more professionally).