Bukkit

@Crayder

You can add that yourself.

Write in your actions.txt a new line:

consolecommand banHammer x 1 ban [player]

You can choose whatever you want instead of "banHammer" (it's just a name for this action). Instead of the "x" write a number that defines how many times per minute a player has to fail a check to really get banned. And you can (and probably should) replace "ban [player]" with whatever your ban command looks like (different plugins offer different types of ban commands). E.g. maybe your ban command allows to set a ban time and a reason for the ban like "/ban playername 10m Banned for cheating", then you'd use instead

consolecommand banHammer x 1 ban [player] 10m Banned for cheating

Now that you have defined what the action "banhammer" is, you can add it to checks of your choice, by appending it to the list of actions that is already defined there. E.g. if you want people to get banned when spamming a lot instead of getting kicked, edit in your config.txt the line:

chat.spam.actions.50 = spamLog chatCancel spamkick

and set it to

chat.spam.actions.50 = spamLog chatCancel banHammer

You can define and run pretty much any command you want in this way (not only "/ban").

@Katorone

It's always hard to explicitely say what is cheating or not. In general, all checks that are related to movement can be failed due to lag (usually the "morepackets" check), mistakes made by NoCheat (e.g. a good way to fail NoCheats movement check is by bunny-hopping across a frozen lake) or similar.

It also shouldn't be necessary to confront players at all, because NoCheat will by default prevent the cheating or severly reduce its effectiveness. So unless someone manages to fail one and the same check over and over without being able to say what he did, it's probably best to ignore the messages completely.

@worstboy32

Took me long enough to find a way to do that without causing lots of other problems in the process (e.g. directly kicking a player while he drops an item -> bad idea, server crashes :/ - had to work around that kind of problem a lot).

@deleted_7536780

Should be fixed in newest version.

@Crayder

No, it hasn't. I tried once and failed. It's not possible (for me) to do in a reliable way.

NoCheat v2.24:

• Fix MobArena shutdown NullPointerException (again)
• Fix some problems when players lose and then get "nocheat.checks.moving" permission(s)
• Catch unexpected errors when executing commands
• BREAKING CHANGE: consolecommand actions are executed a little bit delayed with a bukkit task instead of instantly for safety reasons
• New check "inventory.drop": Kick people if they drop too many items within a short timeframe (default limit is 100 item(stacks) within 20 seconds)

@XeonG8

Not possible.

@Sleaker

There is no way to keep track of the velocity of a player serverside. "player.getVelocity()" is completely useless, as it will always provide false information. The only time when it does give correct results, is immediatly after "player.setVelocity(...)" is called (and only if you don't use Spout. If you use Spout, even that will be wrong). That's why I have to try to at least estimate (generously ) how fast the player may be moving for the next few seconds. :(

@LordKainzo

Afaik Bukkit doesn't offer any ways to access or modify Packet data. If I could do that, a lot of my problems would vanish instantly. The only way I can think of would be to use the Spout plugin, but they declared that they'll drop support for Bukkit as soon as their own project is up and running (which would leave me with the same problem again).

Also, that wouldn't help me with those "velocity" related mechanisms, because those are broken by design. They violate the server-client principle of the client sending instructions and the server executing them, by reversing it.

Hm, that MobArena thing is really strange. I'll have to find out what it is trying to do while the server shuts down, that causes players to get broken that way during teleports. The "crash" shouldn't have any impact anyway though, it probably just doesn't look too nice.

@wide_load

Well spotted. English isn't my first language. My first language is German, and "direct" is spelled "direkt" in German. That's where the k came from. That doesn't change that it was unintentional and I changed it now. :)

NoCheat 2.23:

• Likely fixed NullPointerException when MobArena plugin shuts down
• Removed fight.selfhit check, as it causes problems all over the place with other plugins and isn't that security relevant anymore
• Don't check BlockBreakEvents that can't come from a player (therefore have to come from a plugin), fixes compatibility with "LumberJack" plugin and probably a few others that I don't even know of
• Reduced maximum movement speed a little bit by removing/nerfing a workaround for bunnyhopping
• Support commandbooks "/rocket" command, precious stones etc. (overall stuff that launches players very high in the air) better than before