Bukkit

NoCheat v2.24b:

• our CommandSender is now a ConsoleCommandSender, because some plugins insist on differentiating between those two things
• should fix plugins ignoring "consolecommand" actions

At least for "BanHammer" this should work well.

@The_Wizard

Found it. Oh my god, what a stupid little problem. I'm updating NoCheat now accordingly. It's literally a single word that I got wrong (I used CommandSender instead of ConsoleCommandSender as an implemented Interface).

@The_Wizard

Thanks, I'll try to find out how BanHammer processes commands and why it may fail to execute them when coming from NoCheat.

@The_Wizard

I have no idea why they wouldn't work. They work fine for me. Can you send me the "consolecommand ..." line that you use, where you use it and to which plugin the command belongs?

@XeonG8

Not at the moment. You can follow a related feature request here: http://dev.bukkit.org/server-mods/nocheat/tickets/23-nocheat-regions/

@boblefisk

NoCheat is pretty much at its limits when it comes to stop people from moving in illegal ways. If the current version of NoCheat doesn't block it, future version will most likely also not block it. Unless the author of the mod has builtin a deactivation command, like the author of Zombe's flymod did for his mod.

@redted44

That's too easily avoidable by hacked clients. E.g. if they start all their commands with ".", all they need is to create a command ".." that does nothing but send a normal chat message starting with a "." and their problem is solved.

That is not even considering clients can just as easily replace their special character with anything else (?, #, +, -, ...) or not use chat commands at all (and instead hotkeys, clickable buttons, ...)

NoCheat 2.24a:

• reverted changed behaviour of consolecommands. Back to the insecure, DO IT RIGHT NOW! behaviour.
• will e.g. cause a NullPointerException when players get kicked for dropping too many items, but that's not "lethal" (simply ignore it).
• should fix jumping on and off redstone repeaters

You'll get a NullPointerException now when a player gets kicked for dropping items. Ignore it, it is not dangerous.

@The_Wizard

Hm, seems that the server won't execute consolecommand stuff until all player packets have been processed. I didn't know that, probably only happens if there is latency. Seems like I'll have to revert that last change I made, that was supposed to make consolecommands less insecure to use.

@MonsterTKE

Ah, that explains it. Build CB 1619 fixes this disconnect spam type.

@The_Wizard

The missing "reach" logs may be because Bukkit/Minecraft itself prevents interactions with blocks/entities that are too far away. In these cases NoCheat won't even get noticed about the players attempt to reach further than allowed, therefore can't log it.

Speed block placing, I may look into that. the only method I can think of would be to go for something that works like the spam check, e.g. limiting blocks placed in a specific time interval.

Spamkick, does it not work at all, or what happens in that case? It may have to do with a change I made for 2.24 to get customcommands to work safer.

@xeNiums

What The_Wizard said. This is possible, because Zombe's mod actively reads the first message that comes from the server when the player logs in (usually some kind of "message of the day") and if that message contains a certain word, the mod deactivates itself. The disadvantage of that is that you can't change it once a player is on the server, meaning if he was allowed to use it when joining, he'll be allowed until he leaves the server, and vice versa.

@Villermen

Please tell me how it works out for you. I hadn't much ways to test it, so I'm desperate for feedback.

@MonsterTKE

What version of CB are you using? CB is fixing those issues normally, but they (and I) ran out of ideas about how players can cause this (and therefore ways to fix it). If you find any log messages in server.log (maybe error messages, whatever) related to these "player left the server" spams, I'd be happy to see them.