Bukkit

@Gnintendo

Thanks for telling me that. I didn't notice it when testing. I've fixed it now.

NoCheat v 3.1.1:

• fixed teleports

http://dev.bukkit.org/server-mods/nocheat/pages/changelog-and-downloads/

A detailed explaination of the changes can be found here

Ok, here we go. NoCheat 3.1.0:

• Prevent exploitation of the missing cooperation of the moving.runfly and moving.morepackets checks
• Support MonsterEffect.JUMP, at least rudimentary (Boost potions etc.)
• moving.morepackets check should now no longer be crippled by low TPS
• moving.morepackets check will now stop hacking players faster than before
• Fix detection of water, should fix problems when jumping close to or out of water
• added moving.nofall "aggressive" mode to detect and prevent additional forms of "nofall" hacks
• the aggressive mode for the nofall check is toggleable in the config file

@asofold

It's per client tick or "move" packet which is normally the same, because the client sends a move packet once per tick, and limits itself to 20 ticks per second. So limit times 20 is the distance per second.

Got a new version ready. Just doing some cleaning up and stuff to get everything working. You'll like this version, it has a lot of nice new features. :)

@LordKainzo

I'll replace the checks that depend on server lag and add support for "BOOST".

@ShakyTom

That video will help me a lot in finding out why that happens. Thanks.

@PublicPerv

No, never.

@XeonG8

Works for me. Maybe people try to fly up too fast? The "limited" flying that people are allowed to do when having "nocheat.checks.moving.flying" permission is limited to 1 block upward movement per step (You can change that limit in the config).

@Zombiemold

I'm not sure how the game even decides how far the string is pulled on bows. So I can't promise anything on that. Also, I've currently other things to work on for NoCheat.

@LordKainzo

I didn't know that the jump height increasing potions were actually implemented, as afaik they can't be brewed.

As long as the effect is recorded serverside (like with the swiftness potions) it shouldn't be a problem for me to support that potion effect.

@HighlifeTTU

You can't prevent getting false positives for that from time to time, simply because the targeted player moves while the "attack" is transmitted from the attacker to the server. If the target moved out of range in that time, the server will only see someone attacking something that's out of reach.

So you probably want to make your "ban" only execute if a player keeps attacking somebody who is out of range. To do that do the following for the "reach" check actions option:

actions: log:freach:2:5:if cancel vl>10 log:freach:0:5:if cancel cmd:ban:0:1

That would mean that, as before, attacks over too big distances get logged and blocked, but in addition when a player gets to a "violation level" of 10 or more (for this check, the violation level represents the summed up "attack distance minus allowed attack distance"), he'll get banned.

That should help differentiate between the players that randomly, due to lag, attack players beyond the set maximum distance and those that constantly try to attack enemies beyond that distance.

The "violation level" gets reduced by 20% for every attack that didn't go beyond the set maximum distance, so it should only get to 10 if players keep trying to attack other players (or monsters) that are too far away.

PS: "ban" should obviously be replaced by whatever you used to define your ban command.