Inactive [CHAT/ADMN] StopTalkingAutoBan [Reloaded!] Alpha1 - Intelligent Anti-Spam System [1.4.5-R0.2]

Currently I'm using the player.hasPermission(); but 2.0 will have a "double take" permission system.

This is such a nice plugin but for spam its garbage! Words per minute? That allows a user to spam a lot before they get banned. I HIGHLY suggest making it words per second. I have mine set at 4 words per second.

Can you only count chat that isn't cancelled? My players are getting banned for typing short (Factions plugin) commands in quick succession, even though I set numOfMessages to 6 (I'm not even sure if it's reading the value correctly... people seem to be kicked/banned after 2+ messages in quick succession).

Oh, do continue to use player.hasperm! I hate it when people continue to do Permissions double ups. The system is there not to be ignored, therefore it should remain a standard. I'm using it.

Where the hell did you get words per minute? It uses seconds to track spam. Please get your facts straight. Thx.

I agree completely.


Ill be releasing v1.2.7 in like 3 hours, once I get home from school. v2.0 is coming along nicely. STAB logic has been pretty much completely re-written, and will be finishing up its new plugin system(yes you heard me correctly. STAB2.0 will be able to have it's own extensions)

EDIT: Also forgot to mention, most features made it into 1.2.7... I also changed my algorithm for detecting/ticking commands and implemented a whitelist for commands that you wish to not be tracked by STAB. I also rewrote the way Bukkit handles commands. If a player starts spamming commands, STAB will warn the user and block the commands from being handled by the server any further.

not sure if this has been mentioned but 1.26 seems to block private messaging in essentials via /msg

me and my admin has been doing some testing with this plugin. it doesnt block command spam =/

my server was gwettting spamed till this LOVE IT!

Right, I need some help w/ this. I'm CB #1550 and this does work but whenever I reload, the server crashes. I'd use it, but I change plugins alot, so please help me out here

Is it my plugin that is making your server crash?

v1.2.6 only blocks certain commands. v1.2.7 will implement full command monitoring, with a whitelist to enable quick repetition of that command

Yes, It's your plugin. I removed it, and there were no crashes when I reloaded.

Post or PM me your server.log file so I can determine what the issue is.

cant wait for the update =)

Finals tomorrow - next tuesday. After that, expect big things.

So, /msg and /tell can be unlocked?

Little tip: Quit all threads onDisable. If you don't do that it will have a NullPointer to the PermissionsManager (Don't know what you're using that for anyway, why not player.getPermission("whatever")
It's saying PEX isn't enabled.
That's because the plugin was enabled, before the reload. After the reload, it has to re-enable, but it will have another instance, causing your threads to get a null, causing crazy log spam and DC for everyone.

I advice you do
1. Quit all threads onDisable()
2. Start new threads for every player onEnable()
3. Check if variables aren't null before using them.

Yep!

1.) This is already been done, sorry to burst your bubble.
2.)Once again, this is already done.
3.) The null errors are due to when I originally started creating this plugin. (I was still trying to get used to the way the plugin system works for Bukkit at the time.) I used PEX as the permission system and I never got around to removing/redoing the original code to handle this better. v1.2.7 has a lot of this fixed, and will be testing over the week on a 100 slot server. If issues come up, they will be fixed BEFORE 1.2.7 is pushed out.

Thanks for the help!

How exactly? I cannot find how to D:

You have to wait for STAB v1.2.7

Okay, thanks a lot.
Waiting for 1.2.7 then, tell me when it's out.

I love this! Its my most recommended for your server to stop spam!

I think ALL servers should use this plugin! Good Job!!! +1

I have this annoying issue that the plugin reset the config file every time the server isn't properly shut down (I think at least). This results in innocent people getting banned again because of the low 2 message limit. :/

Found this bug today while working on 1.2.7. And it has(or at least should) be fixed.

STAB2.0 will use a new style of config anyways. And will be much more user friendly.
I will also be creating a small program to generate a config for you

v1.2.7 is done. Letting it run all night, and if no errors show up, I will release it first thing in the morning!

v1.2.7 OUT!

Please make sure to read the changelog.

How do you set a timeout when people logout? So that when they logout they have to wait 5 seconds to log back in, I haerd this is possible with STAB. Also when you get kicked? Please tell me
Also how do I setup ANTISPAM for logging in and out 1000x (spam)

Does this version help against spammers with hacked clients that send 1000 sentences in 3 seconds?

Is it possible to turn off the entire command spam feature off, or at least make it a lot less sensitive?

Currently no. But there will be soon.....