[dataviruset]

Originally Posted by bobbobagan Some users are reporting being kicked with the reason as "Fireflys." when I am using the latest release. Any ideas?

Check the md5 sum or something similar, because I had the same problem when I had the latest version as I thought (the same version number, but not the same file).

And, err... There's a new version again...

[afhof]

/dev/null, Could I make a request? I have noticed that if an griefer tries an exploit and it doesn't work, they trend to try another. Would it be possible to simply temp IPban anyone your plugin catches?

[deadlyruler]

In my error log im getting a ton of spammed commands.
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__eb
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__pyevent
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_cexec
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_cexec
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ep
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__pyevent
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_cexec
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ep
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__de
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__sb
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_fire
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__fire
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__eb
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip
L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__pyevent

I also noticed my server is having lag spikes and I think they are spamming these commands, anyone know how to fix this?

[devicenull]

Originally Posted by deadlyruler In my error log im getting a ton of spammed commands. L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__eb L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__pyevent L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_cexec L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_cexec L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ep L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__pyevent L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_cexec L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ep L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__de L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__sb L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es_fire L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__fire L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__eb L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__ip L 03/29/2010 - 159:42: [rcon_lock.smx] <server> executes: es__pyevent I also noticed my server is having lag spikes and I think they are spamming these commands, anyone know how to fix this?

That's because you are running eventscripts, and an older version of the plugin.

[afhof]

Originally Posted by afhof /dev/null, Could I make a request? I have noticed that if an griefer tries an exploit and it doesn't work, they trend to try another. Would it be possible to simply temp IPban anyone your plugin catches?

devicenull, does this seem possible?

[WebNoob]

Is anyone still getting the respawn issue with the new version? I'd like to upgrade from my current older version if possible.

[DontWannaName]

Try the legacy version?

[lindo81]

how to desable the log which is creating the plugin ?

[devicenull]

Originally Posted by lindo81 how to desable the log which is creating the plugin ?

Maybe read the first post in the thread?

[[X]BetaAlpha]

devicenull,

Would it be possible to have an authorised list of plugins instead of the blacklist route where any plugins outside this list are disabled/deleted? (as potentially sinister plugins can always be renamed or changed at anytime or worse some could actually be the same name as another valid plugin). Or alternatively a blacklist "file" lookup where plugins are entered. May end up with a large blacklist of plugins (not to mention it's more of a management burden on your part.)

-XBetaAlpha