[EKS]

This plugin kick players that have to high a ping, or too low a cl_updaterate/rate setting. It also has a
option to adds X amount to the max ping when the clock is goes over 24.
The plugin can also automaticly update client settings ( Showing a menu to the client ) or just update his setinfo field ( this will cause the settings lost once he closes HL1)

Forum Thread: http://forums.alliedmods.net/showthread.php?t=7341

Credits:
Ops in #AMXmod @ Quakenet for alot of help ( + AssKicR & CheesyPeteza )

Install:
Install the plugin like any other
Put these into your amxx.cfg with the correct vaules
amx_maxping 125
amx_minrate 10000
amx_minupdaterate 40
amx_maxping_add 50

Changelog:

1.1.4 - Added: Define UseSetInfo so you can change if you want to use client_cmd() instead of setinfo 1.1.3 - Fixed: Fixed typo - Added: cvar showing version 1.1.2 - Fixed: Typo in log_amx() - Added: #define To disable cl_updaterate on the client. - Added: Automaticly changeing client settings without chaning the cvar ( Just changeing the setinfo field instead ) - Added: Also checks the clients Rate setting ( cvar: amx_minrate ) - Added: amx_minupdaterate The lowest accetable client updaterate

[Alle]

Why accept higher ping when clock is over 24 ?

[EKS]

Originally Posted by Alle Why accept higher ping when clock is over 24 ?

becuse then most of your regulars might be going to bed, so accepting higher ping players is better then a emty server.

[ericb]

I have no problems compiling a plugin and adding it to the system... but what i do not understand is the values that we are suppose to put in the amxx.cfg file? those are the values that the plugin is going to use ?? or do we edit the values in the sma file only?


do we change these??

#define TaskTime 15.0
#define HowManyChecks 10
#define ExtraPing 150


do we change these??? if the cfg file already has the values?

register_cvar("amx_maxping","125")
register_cvar("amx_minrate","40")
register_cvar("amx_maxping_add","50")

and the maxplayers? do we change these values??????

[EKS]

Just change the cvars.

The #define are for advaced users.

Update

Changelog: 1.1.0 - Added: Shows a menu to ppl with to low a cl_updaterate settings

[Opacus]

Server segfaults when running that plugin

Fedora Core 2

AMXX 1.0
Metamod 1.17.3

[EKS]

hmm, thats weird. It works flawlessly on my test server.( Windows offcourse)

It also work on linux boxes running a unkown distro Im guessing its a bug most likely in amxx, find me on irc if you wanna bother tracking it down.

[Opacus]

I'll just try it on a previous release of AMXX, stability has been virtually non-existent after we upgraded to 1.0...
Servers segfault 5-6 times pr. day, and VERY often during menu-access. That's why I thought it was Your plugins, because I experienced a few times people lowering the updaterate ingame, and within 10 seconds, I would have "Connection Problem" in the upper right corner of my screen.
Conclusion being that I was a bit quick saying it's Your plugin - I too rather think it's AMXX.

[EKS]

I dident think it was this plugin either, as its painfully simple. But trying to trace down exacly what makes the server crash makes it alot simpler to fix

[EKS]

Update:

1.1.1 - Fixed: Task not being removed when player left.

pffft, why do all my plugins have a 1.1.1 version Anyways this could have crashed the server, if some of the natives dont check if the user is connected. ( Most natives check this, or make a generate a runetime error.)