View Full Version : YeGods High Ping Remover v1.0.1.10
YeGods High Ping Remover - v1.0.1.10
About the plugin:
Allow admins to keep the server free from bad connections & set maximum allowed ping/choke/loss :)
Supported Languages:
English
German - Thanks to sessus (http://forums.alliedmods.net/member.php?u=16668)
Polish - Thanks to 300FraYda (http://forums.alliedmods.net/member.php?u=31946)
French - Thanks to flubber (http://forums.alliedmods.net/member.php?u=31687)
Dutch - Thanks to justeagle (http://forums.alliedmods.net/member.php?u=33440)
Server Console Vars:
// Enable the high ping remover plugin
yghpr_enable "1"
// Maximum allowed ping on the server.
// 0 to disable.
yghpr_maxping "100.0"
// Maximum ping points before a client gets kicked, this is updated once a second.
// 60 points will mean the client gets kicked in 60 seconds.
yghpr_maxpingpoints "60"
// Allow admins immunity from getting kicked for a high ping.
yghpr_adminsimmune "1"
// Warn the user for the last 10 connection breaks every second until kicked
yghpr_connectionbreakwarn "1"
// Maximum kick counts a client can get before getting banned.
// 0 to disable
yghpr_maxkickcounts "3"
// How long to ban a client for hitting the kick count limit.
yghpr_kickcountlimitbantime "60"
// How often to clear the kickcounts array.
// 1 = a minute
yghpr_kickcountcleartime "60"
// Extra immunity flag to stop clients getting checked for a high ping
// Flag types (Using the same ones found in the sourcemod admins.inc)
//
// Reservation = 0
// Generic = 1
// Kick = 2
// Ban = 3
// Unban = 4
// Slay = 5
// Changemap = 6
// Convars = 7
// Config = 8
// Chat = 9
// Vote = 10
// Password = 11
// RCON = 12
// Cheats = 13
// Root = 14
// Custom1 = 15
// Custom2 = 16
// Custom3 = 17
// Custom4 = 18
// Custom5 = 19
// Custom6 = 20
//
// Default is set to "1" Generic
yghpr_extraimmunityflag "1"
Installation:
yghpr.smx -> addons\sourcemod\plugins
yghpr.phrases.txt -> addons\sourcemod\translations
plugin.yghpr.cfg -> cfg\sourcemod
yghpr.sp -> addons\sourcemod\scripting
Version History:
1.0.1.10
- Really small optimization
1.0.1.9
- Removed the slight change i made to the ping calculation - Need to do some debugging first & get the calculations right (Added it as a last minute thing which was a bad idea)
- Added a new cvar "yghpr_extraimmunityflag" for a custom immunity flag
1.0.1.8
- Made a slight change to the Ping calculation thanks to urus
- Disabled the Choke/Loss options for the time being (causing too many problems with TF2)
- Added a Polish translation - Thanks to 300FraYda (http://forums.alliedmods.net/member.php?u=31946)
- Added a French translation - Thanks to flubber (http://forums.alliedmods.net/member.php?u=31687)
- Added a Dutch translation - Thanks to justeagle (http://forums.alliedmods.net/member.php?u=33440)
1.0.1.7
- Made a small change that will hopefully fix the choke bug with TF2
1.0.1.6
- Fixed another translation bug :(
1.0.1.5
- All translation bugs fixed
- Hopefully fixed the TF2 config bug
- Added a german translation - thanks to sessus (http://forums.alliedmods.net/member.php?u=16668)
1.0.1.4
- Fixed a bug with the translations - Thanks to bailopan
1.0.1.3
- Plugin now supports translations
1.0.1.2
- Added a few more client connected checks
- Fixed a bug with the loss option
- Few typos fixed in the config file - copy & pasted ;)
1.0.1.1
- Fixed the cVar limits for max ping/choke/loss
1.0.1.0b
- All convars changed to yghpr_### & changed the config name to pluging.yghpr.cfg
- Added new loss & choke options
- Kick counts are now recorded & clients can be banned after they hit a specified number - 0 to disable this option
- Kick counts array can be cleared after a specificed time with - yghpr_kickcountcleartime
- Ping/Choke/Loss options can now be disabled by an admin
1.0.0.4
- Spectators are now skipped
- Added a warning message for the last 10 seconds of a ping violation before getting kicked/banned
1.0.0.3
- Added an option to ban a client aswell as kicking
- Changed the versioning system requested by xYx
1.0.2
- Fixed the config folder error
- Moved the plugin out of beta
1.0.1 BETA
-Option to protect admins from getting kicked for having a high ping
v1.0.0 BETA
-Initial release
Have fun dubbeh :)
Nice job! :)
Maybe add something that if the whole server (everybody) gets a high ping (or if more then xx % has high ping) then dont kick anyone?
thank tcviper :)
i'll have an done by v1.0.2, that seemed to happen quite alot with the client crash bug when someone switched team
just about to upload a quick little update to allow the option to give admins immunity
and thanks for approving the plugin ferret
nice, been waiting for a high ping kicker!
good to see a YeGods dude on the forums.
Better than ED forums hey :p
You wouldn't happen to fancy making a auto team balancer would you? :)
Heres my idea (original I know)
http://forums.alliedmods.net/showthread.php?t=57817
cheers
janbanan
07-15-2007, 15:01
This is very useful, thank you.:up:
How does the admin immunity work? For instance, if i have a regular that i want to except from high-ping kick, but dont want to make him admin, can i give him like 'a' flag or something?
nice, been waiting for a high ping kicker!
good to see a YeGods dude on the forums.
Better than ED forums hey :p
You wouldn't happen to fancy making a auto team balancer would you? :)
Heres my idea (original I know)
http://forums.alliedmods.net/showthread.php?t=57817
cheers
ill have a look into it, bit busy with coding up a match server admin plugin with a lot of ideas based on edap for eventscripts :wink:
This is very useful, thank you.:up:
How does the admin immunity work? For instance, if i have a regular that i want to except from high-ping kick, but dont want to make him admin, can i give him like 'a' flag or something?
all the regular needs is the generic admin flag in sourcemod to be immune from getting kicked :)
ill have a look into it, bit busy with coding up a match server admin plugin with a lot of ideas based on edap for eventscripts :wink:
That would be really handy as well, especially if you can implement all the functionality of EDAP into ur sourcemod plugin.
After you have done this though, I feel making that auto balance would make you a yeGOD!!! :)
On a serious note. I might have found a bug.
I set my server with these settings:
// enable the high ping remover plugin
yg_hpr_enable "1"
// maximum allowed ping on the server
yg_hpr_maxping "150.0"
// Maximum ping points before a cliet gets kicked this is updated once a second
// 60 points will mean the client gets kicked in 60 seconds
// with a continous high ping above the max ping limit
yg_hpr_maxpingpoints "60"
// Allow admins immunity from getting kicked for a high ping. 0= off 1=on
yg_hpr_adminsimmune "1"
I tested these settings and with me having a ping of 300 it did infact kick me. However the console kick message has you exceeded the maxping of 100.00000
Is this a typo, or is maxping cvar not working? (giben that i later my maxping to 150)
just fixed that bug, had the config in the wrong folder :oops: ill upload the new version now
Also noticed that the VERSION_PRINT thingy is labelled hpk 1.0.2 could it be pre-fixed with sm_hpk 1.0.2
I just noticed it prints its version number different from my other sm plugins in hlsw.
Doesnt really matter tho either way, its just nice to see all the sourcemod plugins together in HLSW.
can u make cvar or smth so it will automatically ban player for some time when they reconnect the server after 3 or more kicks?
yeah only problem is it will put a bit more overhead on the server with a seperate thread recording ids & cleaining up the list
atm its only one loop & quite low on server overhead but ill get around to it soon, pretty much why ive not go around to adding the skip percentage option yet ;)
just about to up a quick update that allows u to ban users aswell as kicking them
Brainstorm
08-11-2007, 21:03
Just a heads-up: this plugin wasn't working for me with a fairly recent version (1269) of Sourcemod. I updated to r1310 today, seems to work fine now.
Dubbeh, again, you rock :p
Should add, if not already done, a warning message to client like :
[WARNING] : Hight Ping count 1/X before kick !
[WARNING] : Hight Ping count 2/X before kick !
[WARNING] : Hight Ping count 3/X before kick !
...
Only problem with something like that is the amount of chat spam the user would get
eg. checks the ping every second, the user would have that message spammed every second to the chat section for x ping breaks
I'll have a look into it & see what i can come up with
could print the message on the first ping break, then when they hit half max ping breaks
mmmmmh... If the message is displayed on the last 10 hight ping counts counts, spaming the client for 10 sec is no big deal I assume... (like in ESK High ping kicked, but I prefer your plugin since it's on sourcemod :P)
spelworm
08-12-2007, 20:26
maybe just put a message when ur ping goes over XXX like: "Warning : Do something to ur ping or u will get kicked" then u could also repeat is after 10 seconds or so if he is still in the server
Requests filled in the latest version & skipped observers in the ping checking routine :)
spelworm
08-16-2007, 02:41
Requests filled in the latest version & skipped observers in the ping checking routine :)
like is specs they dont get kicked if high ping ? if yes please make it so u can enable it or disable
Yeah, specs will get skipped in the ping checking routine - I'll add a switchable convar in the next release & let the user enable/disable the option
andye836
08-30-2007, 17:52
just downloaded this but noticed on your installations instructions it says
Installation:
yg_hpr.smx -> addons\sourcemod\plugins
yg_hpr.sp -> addons\sourcemod\scripting
plugin.yg_hpr.cfg -> cfg\sourcemod
but i cant find the yg_hpr.sp file
nvm figured it out
lamdacore
08-31-2007, 02:58
the yg_hpr.sp file is in the first post in the link: "Get Source"
Edit: gnah, didnt' see yor edit sentence >_<
Kaschenko
09-22-2007, 04:34
Can make cvars please yg_hpr_loss, yg_hpr_choke?
It very much would help from lags.
In advance thanks.
Good idea, i'll get them added in the next version. A few changes coming with the next release - recording kick counts & after so many kick counts banning a client - changing all the console vars to yghpr_* - adding a max loss/choke option & max loss/choke points before kicking the client. Hopefully have them all added by this weekend edit.. new lines seem to be broken with the forum
Not forgotten about this ;). Pretty much got all the features added, just need to beta test them now
Had to restructure quite a bit of the code for the updates
Dubbeh:
Are you going to be porting this over to TF2 as soon as sourcemod is live on Tf 2?
We are in desperate need of a ping kicker on TF 2, its certainly the first plugin I'll be adding :)
If you do this, I'll send you some free cake.
Once sourcemod supports the orangebox update this plugin will work fine :)
Find out a bit more about it here (http://forums.alliedmods.net/showthread.php?t=61651)
This should be good to release in beta very soon, just in the process of adding the new cvars to the config & preparing the changelog
Got v1.0.1.0b out ;)
Changelog:
1.0.1.0b
- All convars changed to yghpr_### & changed the config name to pluging.yghpr.cfg
- Added new loss & choke options
- Kick counts are now recorded & clients can be banned after they hit a specified number - 0 to disable this option
- Kick counts array can be cleared after a specificed time with - yghpr_kickcountcleartime
- Ping/Choke/Loss options can now be disabled by an admin
17:09:29 yghpr_maxchoke
17:09:29 "yghpr_maxchoke" = "1.000000" ( def. "15.0" ) min. 1.000000 max. 1000.000000
- Set the maximum choke allowed on the server
Can't disable the choke and stuff like that with 0 :(
mongwong
10-14-2007, 18:44
yeah had the same problem with choke kick set at 0, even changed the choke to a ridiculous figure but still kicked peeps.. so had to remove plug all together for the time being. :(
Think I've fixed this in 1.0.1.1 - Fixed the limits on the minimum cVar input (had it set to 1.0 instead of 0.0)
Can everyone test this version & see if the bugs fixed, Thanks :)
Tekniqal
10-19-2007, 03:30
OK with SM 1616
YGHPG 1.0.1.1
L 10/18/2007 - 19:53:22: SourceMod error session started
L 10/18/2007 - 19:53:22: Info (map "de_dust2") (file "errors_20071018.log")
L 10/18/2007 - 19:53:22: [SM] Native "GetClientAvgLoss" reported: Client 13 is not in game
L 10/18/2007 - 19:53:22: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/18/2007 - 19:53:22: [SM] [0] Line 324, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20845.attach::RunLossChecks()
L 10/18/2007 - 19:53:22: [SM] [1] Line 259, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20845.attach::PingCheckThread()
Thanks for the bug report - this is fixed in v1.0.1.2
Added a few more client connected checks to hopefully avoid this bug & fixed a bug with the loss option
Not tested but this should work fine with TF2 :)
Please, add other languages support.
yghpr.phrases.txt -> cfg\translations
Request filled in v1.0.1.3
Translations now supported :)
I have seen a couple of players getting away with a high ping, by periodicly changing their nick. Can anyone confirm this?
That shouldn't be possible unless the client index changes, one possible way to get away with it is by reconnecting to the server
I think I have a bug I have the .cfg in cfg/sourcemod but I have ping to 175 or they get kicked but its kicking people with 100 ping. I also have the loss/choke disabled but it seems to be kicking them.Please take a look at this. THanks btw this is both for tf2 and css
The .cfg seems to be working fine for CSS but not for TF2.
Sounds like the math is slightly off in TF2 or the config is in the wrong place.
100.0 is the defaulted value set by plugin if it cant find the plugin.yghpr.cfg . If it cant find the config, then it will create a new one with the default values. Can you double check it hasn't automatically created a config in "cfg/sourcemod". Havn't got TF2 to test it atm, but i should be able to put up a test server & get some debug messages to find a possible cause :)
It has not made its own. I dont think the paths are right for TF2. For your plugin or the values are off. As it works fine on my CSS servers.
Tekniqal
10-20-2007, 23:58
sm 1616
yghpg 1.0.1.3
L 10/20/2007 - 17:16:00: [SM] Plugin encountered error 22: Maximum number of parameters reached
L 10/20/2007 - 17:16:00: [SM] Native "PrintToChat" reported: Translation string formatted incorrectly - missing at least 1 parameters
L 10/20/2007 - 17:16:00: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/20/2007 - 17:16:00: [SM] [0] Line 298, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::RunLatencyChecks()
L 10/20/2007 - 17:16:00: [SM] [1] Line 251, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::PingCheckThread()
L 10/20/2007 - 17:16:12: [SM] Plugin encountered error 4: Invalid parameter or parameter type
L 10/20/2007 - 17:16:12: [SM] Native "PrintToChat" reported: Translation failed: invalid client index -1
L 10/20/2007 - 17:16:12: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/20/2007 - 17:16:12: [SM] [0] Line 298, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::RunLatencyChecks()
L 10/20/2007 - 17:16:12: [SM] [1] Line 251, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::PingCheckThread()
L 10/20/2007 - 17:16:14: [SM] Plugin encountered error 4: Invalid parameter or parameter type
L 10/20/2007 - 17:16:14: [SM] Native "PrintToChat" reported: Translation failed: invalid client index -2
L 10/20/2007 - 17:16:14: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/20/2007 - 17:16:14: [SM] [0] Line 298, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::RunLatencyChecks()
L 10/20/2007 - 17:16:14: [SM] [1] Line 251, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::PingCheckThread()
L 10/20/2007 - 17:16:15: [SM] Plugin encountered error 4: Invalid parameter or parameter type
L 10/20/2007 - 17:16:15: [SM] Native "PrintToChat" reported: Translation failed: invalid client index -3
L 10/20/2007 - 17:16:15: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/20/2007 - 17:16:15: [SM] [0] Line 298, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::RunLatencyChecks()
L 10/20/2007 - 17:16:15: [SM] [1] Line 251, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::PingCheckThread()
and a HELL of a lot of that ^
I get 0 errors so any chance of you fixing my problem?
aakerlind
10-22-2007, 06:23
this plugin seems to be working with tf2
Yeah, it is working with tf2!
Its not working with TF2. It obv doesn't read the .cfg. So stop thinking it is.
FlyingMongoose
10-23-2007, 06:58
make sure your config file is in the right directory. I've had a few people with that problem. (this is also why I requested SourceMod's AutoExecCfg native to force the cfg/sourcemod directory, so no matter what you'd have to start your config roots from there)
It is trust me. I don't mess up the where to put the .CFG for this plugin.
3lektr° *Luc)-('s*
10-23-2007, 12:45
Hi;
May i ask some questions.
1. Is ist possible to add a kick with reason option?
That the player get kicked from the server knows that there ping was too high.
2. Can you please update your plugin.
It works perfectly on my Css server but it doesn't work on my Tf2 server.
yours Jan
In my error log i found something like this
Plugin encountered error 22: Maximum number of parameters reached
L 10/23/2007 - 19:57:29: [SM] Native "PrintToChat" reported: Translation string formatted incorrectly - missing at least 1 parameters
L 10/23/2007 - 19:57:29: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/23/2007 - 19:57:29: [SM] [0] Line 298, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::RunLatencyChecks()
L 10/23/2007 - 19:57:29: [SM] [1] Line 251, /home/groups/alliedmodders/forums/files/2/9/2/1/8/20965.attach::PingCheckThread()
I directory translations i have yghpr.phrases.txt
Any hint ?
I must say that this plugin don't working.
Hi;
May i ask some questions.
1. Is ist possible to add a kick with reason option?
That the player get kicked from the server knows that there ping was too high.
2. Can you please update your plugin.
It works perfectly on my Css server but it doesn't work on my Tf2 server.
yours Jan
1. Yeah, all kick messages will say if the players ping/choke/loss was too high & warn them about the max setting
2. Lots have people have been talking about this bug - not sure if its to do with having the config in the wrong folder, but a definate work around is to put the cvar settings into the server.cfg
@wiciu I'll have a look into that & find the possible cause, might have overlooked something
BAILOPAN
10-24-2007, 13:47
You are misusing "%T" -- it requires an extra parameter containing the client index (directly following the phrase, but before the parameters).
If the function is a targeting function (i.e. like PrintToChat), then it's simpler to just use %t instead, Core will automatically know the client properly.
This is necessary, of course, because clients can have different languages. For more information, see here (http://wiki.alliedmods.net/Translations_%28SourceMod_Scripting%29#Usage_ in_a_Plugin).
Thanks bail, thought i might have overlooked something
This is fixed in v1.0.1.4
imported_Anth0ny
10-25-2007, 09:09
nice work!
=)
Added the German translation.
It's still not reading the .cfg I have 150 in the .cfg but kicks for 100 as thats defualt. Do I need to have it at 150.0 not 150 ?
I actually had the same thing, none of th CFG's were being read in the {mod}/cfg/soourcemod folder.
I just put most of the cvars in the server.cfg
I ended up disabling this plugin for now because of previous errors mentioned already and because users keep on getting kicked because of choke, loss, etc errors.
For TF2 does anyone have any recommended settings for choke, loss, etc.
For the most part, I really just want to kick anyone who has a ping of 180 or higher. But if it would benefit the server to limit the other stuff then I'd like to do that.
lamdacore
10-26-2007, 02:29
if the choke think is not disabled on setting it to zero, then i would set it to 1000 (max) that should no player reach and even if some player reached it, there is defenetly something wrong with that clients connection.
The cfg thing. You can easily write in your server.cfg
exec sourcemod/plugin.yghpr.cfg
that would force to execute the cfg file. im doing that too because the automatically execute does not work, it seems.
EDIT:
in the translation fixed version I think this code in KickClientWithReason()
Format (szBuffer, sizeof (szBuffer), "%T", "Ping Too High", client, g_fMaxPing);
KickClient (client, szBuffer);
}
else if (g_iMaxChokePoints <= g_iChokePoints[client])
{
Format (szBuffer, sizeof (szBuffer), "%T", "Choke Too High", client, g_fMaxChoke);
KickClient (client, szBuffer);
}
else if (g_iMaxLossPoints <= g_iLossPoints[client])
{
Format (szBuffer, sizeof (szBuffer), "%T", "Loss Too High", client, g_fMaxLoss);
KickClient (client, szBuffer);
}
should also be changed to this code:
Format (szBuffer, sizeof (szBuffer), "%t", "Ping Too High", client, g_fMaxPing);
KickClient (client, szBuffer);
}
else if (g_iMaxChokePoints <= g_iChokePoints[client])
{
Format (szBuffer, sizeof (szBuffer), "%t", "Choke Too High", client, g_fMaxChoke);
KickClient (client, szBuffer);
}
else if (g_iMaxLossPoints <= g_iLossPoints[client])
{
Format (szBuffer, sizeof (szBuffer), "%t", "Loss Too High", client, g_fMaxLoss);
KickClient (client, szBuffer);
}
at least i got this error messages yesterday from this part wit the upper case %T letter:
L 10/25/2007 - 19:24:35: [SM] Displaying call stack trace for plugin "yghpr.smx":
L 10/25/2007 - 19:24:35: [SM] [0] Line 422, yghpr.sp::KickClientWithReason()
L 10/25/2007 - 19:24:35: [SM] [1] Line 343, yghpr.sp::RunLossChecks()
L 10/25/2007 - 19:24:35: [SM] [2] Line 263, yghpr.sp::PingCheckThread()
Thanks for the translation sissus
Thanks for the info lamdacore
hopefully all bugs fixed now in 1.0.1.5
Still doesnt read the .cfg
Found a strange bug with the config file problem
Had to change the map after server load for it to create the config file
Think it could be a possible bug in SourceMod
As of version 1.0.1.5 I get the following error message
L 10/28/2007 - 04:21:24: [SM] Plugin encountered error 4: Invalid parameter or parameter type
L 10/28/2007 - 04:21:24: [SM] Native "PrintToChat" reported: Language phrase "High Ping" not found
L 10/28/2007 - 04:21:24: [SM] Debug mode is not enabled for "yghpr.smx"
L 10/28/2007 - 04:21:24: [SM] To enable debug mode, edit plugin_settings.cfg, or type: sm plugins debug 23 on
Thanks for the bug report - fixed this in v1.0.1.6
This plugin config fixed yet?
Hmm on my test server seems that config plugin.yghpr.cfg is executed.
lamdacore
11-02-2007, 04:09
maybe the config file only will not be executed on linux systems?
wiciu: what os is your test server?
@lamdacore
OS -> Fedora core 7
kernel -> 2.6.22.4-65.fc7
but ... one word about plugin.yghpr.cfg. It's executed after first map change !. When I start my server; plugin.yghpr.cfg is not working.
lamdacore
11-02-2007, 09:07
but ... one word about plugin.yghpr.cfg. It's executed after first map change !. When I start my server; plugin.yghpr.cfg is not working.
ah ok thats the point then .. seems to be a bug in sourcemod
Hi YeGods,
I set yghpr_maxchoke "0" in our config because we were having a lot of users being kicked and they were regular users. We are running TF2 when I set the choke to 0 it seems to have disabled the plugin because I can see frame skipping users and we have maxping set to 200 and there are people in the server with like 250 ping.
I'm going to set maxchoke to like 20 and see if by re-enabling it the rest of the plugin works but maybe you can check to make sure that if one feature is disabled it doesn't disable everything?
Thanks for the plugins!
Seems to be some fairly major problems with the TF2 as far as choke is concerned. For now we have removed this plugin and are using the Country Filter plugin.
Indeed we have the same problem on our servers, a lot of people get kicked at the same time or they time out for some strange reason.
Any idea on this dubbeh?
imported_Anth0ny
11-15-2007, 13:02
i have it too... =(
Think i might have an idea of how this bug is happening but i need to get the code from backup over the network & run some tests
Hopefully have it fixed within the next couple of days, got a couple of cup matches, one tonight & one tomorrow. I'll try to get an a update out by wednesday :)
gl dubbeh, can't wait for the new version.
the admin immunity should also apply for choke and loss
Tenacious
11-27-2007, 06:05
The plugin makes TF2 game server crash sometime :/
Can everyone test this small update & see if the problem still occurs with TF2
If it still happens I'll have it fixed 100% in the next update, I promise ;)
Thanks
@PrefeX Admin immunity applies for everything
Hi dubbeh getting A LOT of complaints about high choke messages.
Can you explain is the yghpr_maxchoke the maximum amount of choke someone can get during the yghpr_maxchokepoints period or is it averaged out and if it's above the yghpr_maxchoke for the yghpr_maxchokepoints the user is kicked???
Michael_Jim
12-05-2007, 11:36
Hi,
i've set yghpr_maxchoke "0" and yghpr_maxloss "0", but people with too high choke and loss get kicked?!?
My cfg is in cfg/sourcemod.
I'm running a TF2 Server and the plugin won't crash the server :)
Michael_Jim
Bloodlvst
12-05-2007, 11:49
Hi dubbeh getting A LOT of complaints about high choke messages.
Can you explain is the yghpr_maxchoke the maximum amount of choke someone can get during the yghpr_maxchokepoints period or is it averaged out and if it's above the yghpr_maxchoke for the yghpr_maxchokepoints the user is kicked???
Rothgar, I'm not sure of the problem, but if the messages are bothering you, I have edited this plugin to use on my server so that the loss and choke functions don't exist and it only keeps track of the ping itself. PM me if you want more.
Hi,
i've set yghpr_maxchoke "0" and yghpr_maxloss "0", but people with too high choke and loss get kicked?!?
My cfg is in cfg/sourcemod.
I'm running a TF2 Server and the plugin won't crash the server :)
Michael_Jim
Michael_Jim, I think setting it to 0 means that you can't have ANY choke or loss. Set it to something stupidly high that you know people never get and you should be okay. Or I can send you the edited version I offered Rothgar.
TFN|Nick
12-05-2007, 12:58
I had to remove this because of the choke... I had it set at 25 choke in the config and people with 10 choke where still getting kicked :? It maybe an actual bug with the plugin, but i'm not sure. Could i have a copy of the ping tracker Bloodlvst??
TFN | Nick
Bloodlvst
12-05-2007, 13:02
I had to remove this because of the choke... I had it set at 25 choke in the config and people with 10 choke where still getting kicked :? It maybe an actual bug with the plugin, but i'm not sure. Could i have a copy of the ping tracker Bloodlvst??
TFN | Nick
You mean the version of YeGods that I edited? Sure, just shoot me a PM with either an email adress or your AIM, Live Messenger, or whatever method you prefer and I'll send it over when I get home.
A ping kick immunity config file would be a great addition to this as some people you don't want as admins but would like them immune to the ping kicker.
Bloodlvst, i would like very much to test your version of the plug in, i send you a pm with my messenger adress.
Bloodlvst
12-16-2007, 18:04
Sorry I've been late on this guys... I'll be posting the source here shortly and PM-ing you all the package.
(Had to format and was only able to recover parts of folders I forgot to backup, including my SM scripts, D'oh!)
justeagle
12-22-2007, 19:13
Here's a Dutch translation:
{1} seconds remaining before getting kicked for a high ping violation
{1} seconden voordat je gekicked wordt wegens een te hoge ping
{1} seconds remaining before getting kicked for a high choke violation
{1} seconden voordat je gekicked wordt wegens een te hoge choke
{1} seconds remaining before getting kicked for a high loss violation
{1} seconden voordat je gekicked wordt wegens een te hoge loss
Sorry, You've hit {1} connection violations and have been banned for {2} minutes
Sorry. Je hebt {1} overtredingen uitstaan en bent gebanned voor {2} minuten
Sorry your ping is too high. Max ping is {1}
Sorry, je ping is te hoog. De maximum ping is {1}
Sorry your choke is too high. Max choke is {1}
Sorry, je choke is te hoog. De maximum choke is {1}
Sorry your loss is too high. Max loss is {1}
Sorry, je loss is te hoog. De maximum loss is {1}
I'm about to test this plugin on my server (in English) but I figured you'd like this.
And here is the french one ;)
{1} seconds remaining before getting kicked for a high ping violation
{1} secondes restantes avant d'ętre kicker pour ping trop élevé
{1} seconds remaining before getting kicked for a high choke violation
{1} secondes restantes avant d'ętre kicker pour choke trop élevé
{1} seconds remaining before getting kicked for a high loss violation
{1} secondes restantes avant d'ętre kicker pour loss trop élevé
Sorry, You've hit {1} connection violations and have been banned for {2} minutes
Désolé vous avez {1} violation des regles de connexion et avez été banni pour {2} minutes
Sorry your ping is too high. Max ping is {1}
Désolé votre ping est trop élevé, ping maximum autorisé : {1}
Sorry your choke is too high. Max choke is {1}
Désolé votre choke est trop élevé, choke maximum autorisé : {1}
Sorry your loss is too high. Max loss is {1}
Désolé votre loss est trop élevé, loss maximum autorisé : {1}
Chaos Llama
12-30-2007, 16:49
Settings dont appear to be read from the config file in the latest version (1.0.1.7)
For instance, i had max ping set to 200, choke and loss disabled and admins immune - yet as an admin i got kicked for having 30 choke.
I edited the cvars in the plugin, hopefully that will fix it.
DontWannaName
01-14-2008, 23:18
It didnt fix it for me. People are getting kicked with the high choke when I have choke disabled. I dont know if any of the other configs are being read though.
ottobohn
01-15-2008, 15:49
I have the same kicking for choke 30 issue. I say put choke at 500 or something that'll never get you kicked. I'm going to play round with the cvars and post the ones that work for us. I had it disabled.
otto
When I first ran this plugin I had the same issue with the config not being executed. After editing the config file I executed it on the console.
exec sourcemod/plugin.yghpr.cfg
After doing that I added this command to my server.cfg to make sure it ran my settings everytime server changed map.
ottobohn
01-15-2008, 19:57
I've attached a version that only kicks due to ping, not choke or player loss. Just eliminate the cvars for loss/choke from your server.cfg and u'll be fine. Just worry about setting the ping kick.
Otto
n00bsalad.net
DontWannaName
01-15-2008, 20:25
Thanks, I will try it out today. I made the old cfg exec in server.cfg but I never was ingame to test if it worked but who needs the choke settings, makes it too advanced as choke differs.
300FraYda
01-28-2008, 14:44
Here is polish translation for this plugin.
"High Ping Violation"
{
"#format" "{1:d}"
"en" "{1} seconds remaining before getting kicked for a high ping violation"
"de" "{1} Sekunden verbleiben bis ein Kick wegen zu hochem Ping erfolgt."
"pl" "{1} Pozostało sekund zanim zostaniesz usunięty za zbyt wysoki ping"
}
"High Choke Violation"
{
"#format" "{1:d}"
"en" "{1} seconds remaining before getting kicked for a high choke violation"
"de" "{1} Sekunden verbleiben bis ein Kick wegen zu hochem Choke erfolgt."
"pl" "{1} Pozostało sekund zanim zostaniesz usunięty za wysoki choke"
}
"High Loss Violation"
{
"#format" "{1:d}"
"en" "{1} seconds remaining before getting kicked for a high loss violation"
"de" "{1} Sekunden verbleiben bis ein Kick wegen zu hochem Paketverlust erfolgt."
"pl" "{1} Pozostało sekund zanim zostaniesz usunięty za wysoki loss"
}
"Hit Connection Violations"
{
"#format" "{1:d},{2:d}"
"en" "Sorry, You've hit {1} connection violations and have been banned for {2} minutes"
"de" "Sorry, Du hast {1} Verbindungsverstöße erreicht und wirst für {2} Minuten gebannt."
"pl" "Wybacz, Masz {1} złych połaczen i zostaniesz zbanowany na {2} minut"
}
"Ping Too High"
{
"#format" "{1:f}"
"en" "Sorry your ping is too high. Max ping is {1}"
"de" "Sorry dein Ping ist zu hoch. Max Ping ist {1}"
"pl" "Wybacz, masz za wysoki PING. Maksymalny ping to {1}
}
"Choke Too High"
{
"#format" "{1:f}"
"en" "Sorry your choke is too high. Max choke is {1}"
"de" "Sorry dein Choke ist zu hoch. Max Ping ist {1}"
"pl" "Wybacz masz za wysoki choke. Maksymalny choke to {1}"
}
"Loss Too High"
{
"#format" "{1:f}"
"en" "Sorry your loss is too high. Max loss is {1}"
"de" "Sorry dein Paketverlust ist zu hoch. Max Paketverlust ist {1}"
"pl" "Wybacz Twój loss jest za wysoki. Maksymalny loss to {1}"
}
}
Do I need to paste in my server.cfg
exec sourcemod/plugin.yghpr.cfg
?
I've attached a version that only kicks due to ping, not choke or player loss. Just eliminate the cvars for loss/choke from your server.cfg and u'll be fine. Just worry about setting the ping kick.
Otto
n00bsalad.net
Hi Otto,
I spotted your post while coming back to check this plugin out again and having a ping only check was exactly what we were after, so TY!
Matt
ottobohn
02-01-2008, 12:29
Do I need to paste in my server.cfg
exec sourcemod/plugin.yghpr.cfg
?
I dont put anything in the server.cfg except the cvars in plugin.yghpr.cfg. I just take it a step farther. You can just edit the values in plugin.yghpr.cfg and be fine. I like to set the cvars in server.cfg that are in plugin.yghpr.cfg, so I know 100% that my server will have those values.
Otto
I find what plugin wrong detect players ping.
For example "yghpr_maxping" = "80.0", but players with ping 100 stay on server without problems.
It because this line in plugin:
fClientLatency = GetClientLatency (client, NetFlow_Outgoing) * 500.0;
calculated ping 80 as ~ 50 and only players with ping ~ 120 and more real kicked from server for ping violation (0.160000 * 500.0 = 82 > 80 ).
500.0 it`s good value for ping 10-15, but for ping 80 this must be ~ 780.0 and for ping 120 ~ 820.0
The-Killer
02-26-2008, 01:40
good thought but even when i said max choke to 50 people were still getting kicked for it and i dont see how anyone could have a choke that high and not notice them lag, maybe make a version that does ping only?
DontWannaName
02-26-2008, 01:55
Already done and works perfecty. Should replace the plugin on the first page as its bugged. Go to page 10 for the plugin.
http://forums.alliedmods.net/showthread.php?t=57944&page=10
Sorry I've not been here for ages
I'll be releasing an update for this soon. Think the best way to go about it is to disable the Choke/Loss options, till i get to what was causing all the problems
Tekniqal
03-02-2008, 22:19
Thanks man
Cant wait for an update...
DontWannaName
03-03-2008, 17:14
For some reason it wont let me see page 12 but can you add immunity using the reserved slot flag so my donators can be immune to it too.
Dubbeh the new version gives problems,
people get kicked while having a ping of 60 while i set it to 200 in the config file:
// Maximum allowed ping on the server.
// 0 to disable.
yghpr_maxping "200.0"
Extreme_One
03-04-2008, 05:34
For some reason it wont let me see page 12 but can you add immunity using the reserved slot flag so my donators can be immune to it too.
You can just give your donators the 'b' flag :)
Don't worry about it, added a new convar to use a custom admin flag ;)
@Viper rolled back the slight calculation change i made to the ping check, should stop that problem happening.
This is the only plugin i have that will not read from the cfg unless i put exec sourcemod/plugin.yghpr.cfg in the server.cfg.
DontWannaName
03-04-2008, 23:26
Ya thats why I have the exec command in my cfg, can you fix this Dubbeh?
This plugin is using up a lot of resources on our server.
This plugin is using up a lot of resources on our server.
Did you try up-grating your server from a Celeron to something like an Opteron?
Did you try up-grating your server from a Celeron to something like an Opteron?
You mean upgrading from our Dual Xeon 3.06GHz server with HTT and 4GB RAM to something bigger...
Can't see how this plugin would choke a dedi running on that spec :o
Just wondering, have you got the yghpr_maxkickcounts cVar set greater than 0? That can use up quite a bit of memory over an amount of time, if the clear timer is set quite high & the server is constantly full
The config problem I'm not sure why it happens, everything seems to be setup right
Well one of the problems i think is that srcds.exe never seems to go above 25% CPU, like a limitation or something, however looking at the processors, none of them are peaked.
I was using:
yghpr_enable "1"
yghpr_maxping "280.0"
yghpr_maxpingpoints "60"
//yghpr_maxchoke "10.0"
//yghpr_maxchokepoints "60"
//yghpr_maxloss "5.0"
//yghpr_maxlosspoints "60"
yghpr_adminsimmune "0"
yghpr_connectionbreakwarn "1"
yghpr_maxkickcounts "3"
yghpr_kickcountlimitbantime "20"
yghpr_kickcountcleartime "60"
yghpr_extraimmunityflag "1"
You mean upgrading from our Dual Xeon 3.06GHz server with HTT and 4GB RAM to something bigger...
Yes, that is exactly what I meant. If you have a single Dual Xeon and you are running more than, say 3 instances of cstrike, then you a likely to run into problems.
Also: Using a Windows server permanently is never a good idea.
This plugin just stops working sometimes and it doesn't work again until the server has been restarted.
I have seen people in the server with about 500ms latency and I have verified this with a "status" command and yet I have the high ping kicker set to 280 and nothing happens.
DontWannaName
03-30-2008, 16:53
Its half dead :D
The plugin does not work whith SM 1.0.0 :evil:
Update pls, we really need a working ping kicker for sourcemod
DJ Tsunami
05-01-2008, 12:15
sirmoe: use High Ping Kicker (http://forums.alliedmods.net/showthread.php?t=70417). Liam will release a Linux and Orange Box version soon.
DontWannaName
05-01-2008, 16:05
This should be moved to unapproved since its almost dead and theres a new one from Liam
Stinkyfax
05-25-2008, 06:53
nice one, using it from now.
when will loss and choke be supported? when (would really like to see these, choke and loss kicker)?
Hi there,
I just made some grammatical correction for the French translation ... See the attached file.
(If you're interested of course)
Cya!
This plugin is the only one which is workin on my servers. The other plugin called High Ping Kicker doesn't work at all.
I would like the developer YeGods to keep supporting this plugin. Please, we need you.
The High Ping Kicker from Liam is working perfectly on our TF2 servers.
The High Ping Kicker from Liam is working perfectly on our TF2 servers.
That is the problem. I don't know what is happening. I tried to put Max Ping 10 and it didn't kick anyone. 4 miutes have passed and the player with 990 ping wasn't kicked.
So I went to this plugin here which is the only one working. I am running a DOD:S server with the 1.1 2440 branch.
That is the problem. I don't know what is happening. I tried to put Max Ping 10 and it didn't kick anyone. 4 miutes have passed and the player with 990 ping wasn't kicked.
So I went to this plugin here which is the only one working. I am running a DOD:S server with the 1.1 2440 branch.
I am running the same snapshots on a DODS Server with Liams Ping Kicker & it works fine for me.
You should change the version number from 1.0.10 to 1.1.
You should change the version number from 1.0.10 to 1.1.
????????
There is a new version of YeGods plugin?
That is the problem. I don't know what is happening. I tried to put Max Ping 10 and it didn't kick anyone. 4 miutes have passed and the player with 990 ping wasn't kicked.
So I went to this plugin here which is the only one working. I am running a DOD:S server with the 1.1 2440 branch.
I've had the same problem. I'll be going back to this one tomorrow morning.
laorui304
11-20-2008, 01:29
I've had the same problem. I'll be going back to this one tomorrow morning.
I have the same problem
If some one know how to solve it please tell us
Thx
The-Tournament
11-21-2008, 19:10
I found that if i "quit" the server then when it restarted the plugin didnt work I had to use HLSW to change the map straight away and it worked fine until the server restarted then I had to do it again.
might be a fix for this
laorui304
11-26-2008, 03:40
I found that if i "quit" the server then when it restarted the plugin didnt work I had to use HLSW to change the map straight away and it worked fine until the server restarted then I had to do it again.
might be a fix for this
My trouble is another situation,for example,when a guy enter into my serve with 400 ping ,he cant be kicked even he played hours of time,it seems the Remover doesnt work.But when i downloading sth,my ping can up to 400,and without few seconds i will get kicked.I really dont know how to solve .Here is the config i set
//
// YeGods High Ping Remover
//
// Coded by dubbeh
//
// Enable the high ping remover plugin
yghpr_enable "1"
// Maximum allowed ping on the server.
// 0 to disable.
yghpr_maxping "300.0"
// Maximum ping points before a client gets kicked, this is updated once a second.
// 60 points will mean the client gets kicked in 60 seconds.
yghpr_maxpingpoints "15"
// Maximum allowed choke on the server
// 0 to disable
yghpr_maxchoke "25.0"
// Maximum ping points before a client gets kicked this is updated once a second.
// 60 points will mean the client gets kicked in 60 seconds
yghpr_maxchokepoints "30"
// Maximum allowed loss on the server
// 0 to disable
yghpr_maxloss "15.0"
// Maximum loss points before a client gets kicked this is updated once a second.
// 60 points will mean the client gets kicked in 60 seconds.
yghpr_maxlosspoints "30"
// Allow admins immunity from getting kicked for a high ping.
yghpr_adminsimmune "1"
// Warn the user for the last 10 connection breaks every second until kicked
yghpr_connectionbreakwarn "1"
// Maximum kick counts a client can get before getting banned.
// 0 to disable
yghpr_maxkickcounts "5"
// How long to ban a client for hitting the kick count limit.
yghpr_kickcountlimitbantime "60"
// How often to clear the kickcounts array.
// 1 = a minute
yghpr_kickcountcleartime "60"
// Extra immunity flag to stop clients getting checked for a high ping
// Flag types (Using the same ones found in the sourcemod admins.inc)
//
// Reservation = 0
// Generic = 1
// Kick = 2
// Ban = 3
// Unban = 4
// Slay = 5
// Changemap = 6
// Convars = 7
// Config = 8
// Chat = 9
// Vote = 10
// Password = 11
// RCON = 12
// Cheats = 13
// Root = 14
// Custom1 = 15
// Custom2 = 16
// Custom3 = 17
// Custom4 = 18
// Custom5 = 19
// Custom6 = 20
//
// Default is set to "1" Generic
yghpr_extraimmunityflag "1"
DontWannaName
11-26-2008, 04:20
Thats cause this plugin is old and doesn't calculate the players ping properly unlike Liams new version in another topic which does.
laorui304
11-27-2008, 00:06
Thats cause this plugin is old and doesn't calculate the players ping properly unlike Liams new version in another topic which does.
http://i76.servimg.com/u/f76/12/86/53/47/210.jpg
Here is the screenshot of my plugins and version.YeGods High Ping Remover v1.0.1.10 is the newest version.Really dont know how to make the Remover work.
DontWannaName
11-27-2008, 02:56
http://forums.alliedmods.net/showthread.php?p=701420
Lebson506th
11-27-2008, 08:06
His point is that this plugin does not work, which is why its in the "Unapproved" section.
The one he linked DOES work, so use that.
laorui304
11-27-2008, 10:45
http://forums.alliedmods.net/showthread.php?p=701420
Thx and i will have a try
noPASARAN
06-07-2009, 13:39
Russian version (http://aces-gs.ru/musor/yghpr.phrases_RU.rar)
HAS UPDATED!!!
Russia fail delete /
ďĺđĺçŕëĺéňĺ ďîćŕéëóńňŕ .
noPASARAN
05-31-2011, 04:52
"Phrases"
{
"High Ping Violation"
{
"#format" "{1:d}"
"en" "{1} seconds remaining before getting kicked for a high ping violation"
"de" "{1} Sekunden verbleiben bis ein Kick wegen zu hochem Ping erfolgt."
"pl" "{1} Pozostało sekund zanim zostaniesz usunięty za zbyt wysoki ping"
"nl" "{1} seconden voordat je gekicked wordt wegens een te hoge ping"
"fr" "{1} secondes restantes avant d'ętre kicker pour ping trop élevé"
"ru" "{1} секунд остается, прежде чем кикнут за то, что привышен Ping"
}
"High Choke Violation"
{
"#format" "{1:d}"
"en" "{1} seconds remaining before getting kicked for a high choke violation"
"de" "{1} Sekunden verbleiben bis ein Kick wegen zu hochem Choke erfolgt."
"pl" "{1} Pozostało sekund zanim zostaniesz usunięty za wysoki choke"
"nl" "{1} seconden voordat je gekicked wordt wegens een te hoge choke"
"fr" "{1} secondes restantes avant d'ętre kicker pour choke trop élevé"
"ru" "{1} секунд остается, прежде чем кикнут за то, что привышен Choke"
}
"High Loss Violation"
{
"#format" "{1:d}"
"en" "{1} seconds remaining before getting kicked for a high loss violation"
"de" "{1} Sekunden verbleiben bis ein Kick wegen zu hochem Paketverlust erfolgt."
"pl" "{1} Pozostało sekund zanim zostaniesz usunięty za wysoki loss"
"nl" "{1} seconden voordat je gekicked wordt wegens een te hoge loss"
"fr" "{1} secondes restantes avant d'ętre kicker pour loss trop élevé"
"ru" "{1} секунд остается, прежде чем Вас кикнут за то, что привышен Loss"
}
"Hit Connection Violations"
{
"#format" "{1:d},{2:d}"
"en" "Sorry, You've hit {1} connection violations and have been banned for {2} minutes"
"de" "Sorry, Du hast {1} Verbindungsverstöße erreicht und wirst für {2} Minuten gebannt."
"pl" "Wybacz, Masz {1} złych połaczen i zostaniesz zbanowany na {2} minut"
"nl" "Sorry. Je hebt {1} overtredingen uitstaan en bent gebanned voor {2} minuten"
"fr" "Désolé vous avez {1} violation des regles de connexion et avez été banni pour {2} minutes"
"ru" "Извините, Вы достигли {1} нарушения связи и забанены на {2} минуты."
}
"Ping Too High"
{
"#format" "{1:f}"
"en" "Sorry your ping is too high. Max ping is {1}"
"de" "Sorry dein Ping ist zu hoch. Max Ping ist {1}"
"pl" "Wybacz, masz za wysoki PING. Maksymalny ping to {1}"
"nl" "Sorry, je ping is te hoog. De maximum ping is {1}"
"fr" "Désolé votre ping est trop élevé, ping maximum autorisé : {1}"
"ru" "Извените но Ваш ping слишком высок. Максимальный ping {1}"
}
"Choke Too High"
{
"#format" "{1:f}"
"en" "Sorry your choke is too high. Max choke is {1}"
"de" "Sorry dein Choke ist zu hoch. Max Ping ist {1}"
"pl" "Wybacz masz za wysoki choke. Maksymalny choke to {1}"
"nl" "Sorry, je choke is te hoog. De maximum choke is {1}"
"fr" "Désolé votre choke est trop élevé, choke maximum autorisé : {1}"
"ru" "Извените но Ваш choke слишком высок. Максимальный choke {1}"
}
"Loss Too High"
{
"#format" "{1:f}"
"en" "Sorry your loss is too high. Max loss is {1}"
"de" "Sorry dein Paketverlust ist zu hoch. Max Paketverlust ist {1}"
"pl" "Wybacz Twój loss jest za wysoki. Maksymalny loss to {1}"
"nl" "Sorry, je loss is te hoog. De maximum loss is {1}"
"fr" "Désolé votre loss est trop élevé, loss maximum autorisé : {1}"
"ru" "Извените но Ваш loss слишком высок. Максимальный loss {1}"
}
}
vBulletin® v3.8.7, Copyright ©2000-2024, vBulletin Solutions, Inc.