What is this?
This is a Choke / Ping | Latency / Loss kicker.
Alright... um.... What makes this different then Liam's or Msleeper's Ping kicker plugin.
Well, the major downfall to using their takes on this is they deal with static data. Regardless of what the rest of the servers latency is, clients are kicked if they break the static limit. If the server is being attacked, if the server is having network issues. Everyone will be kicked. This is just stupid. What this does is it gets the lowest Ping/Choke/Loss value in the server, and creates a limit based on that.
Cool! But I want my admins to be immune to this!
Of course. By default anyone with the Reservation flag is immune.
What can I configure about this?
Quite a few things actually, here's a list.
nt_enabled - Is the plugin enabled?
nt_minplayercount - How many players have to be in game until this is started.
nt_checkrate - How often the plugin checks client values.
nt_kickvocalize - Should kicks be vocalized to the server or not.
nt_warningvocalize - Should the client be warned that he is going to be kicked unless if something drastically changes with his connection.
nt_logenabled - Should I be logging kicks?
nt_logformatext - Log Filename Time Format.
nt_logformatint - Log Internal Time Format.
nt_choke_enable - Should the Choke Checker be enabled?
nt_choke_addition - What should the limit be based on the lowest choke value?
nt_choke_threashold - How many consecutive checks the client has to fail before he's kicked from the server (Choke).
nt_latency_enable - Should the Latency Checker be enabled?
nt_latency_addition - What should the limit be based on the lowest latency value?
nt_lat_threashold - How many consecutive checks the client has to fail before he's kicked from the server (Latency).
nt_liammethod - Should we use Liam's method to get a more accurate latency time?
nt_loss_enable - Should the Loss Checker be enabled?
nt_loss_addition - What should the limit be based on the lowest loss value?
nt_loss_threashold - How many consecutive checks the client has to fail before he's kicked from the server (Loss).
Alright, thanks for those CVars. I'll manually configure them!
Sounds like a plan. Remember this plugin reads values from cfg/sourcemod/networktools.cfg and you should NOT place them elsewhere. Also remember you do not need to edit them (The Suggested values I personally think are best).
Are there any commands? How can I be certain that this is working?
Yup! There sure are.
nt_display on its own will give you some information about the entered convars. If it's active and what not. nt_display with a target (ie nt_display Kyle12) will display information about the client (Current Value | Broken Limit/Max limit before kick). This will also tell you if the plugin is actively monitoring the client.
nt_toggle will toggle immunity on specific clients (Should they be kicked for breaking the limits).
What does this act as a replacement for?
This acts as a replacement for the following:
High Ping Kicker - Lite Edition
Very Basic High Ping Kicker (Updated 7/15/10)
RateTables (for the Linux Kernel).
Credits:
Liam - Using his alternative method for getting client latency.
Psychonic - Answering generic questions in IRC.
Secondary Protocol - Being an awesome tester.