[ADMN/SEC] AntiCheat v1.5.8 - Protect your server from hackers & cheaters [1.5.2-R2.0]

Errr... That doesn't sound right at all.. what version are you using?

This issue is on our radar, we're looking into it

AntiCheat v1.3 is now online.

AntiCheat v1.3 is a bugfix and new feature build.

• This build does not require immediate action.
• AntiCheat v1.3 is 5.3 kB larger than the previous major version (1.2) with a total size of 77.4 kB.
• AntiCheat v1.3's changes span across dev builds #143-#171.

CHANGELOG:

Fixes:

• Fixed teleportation causing y-axis false-positives
• Fixed TnT breakage causing fastbreak false-positives
• Fixed Giga Drill (mcMMO) causing fastbreak false-positives
• Fixed water, ladder, minecart, and vine related ascension problems
• Fixed noswing false-positives when breaking large amounts of blocks in creative
• Fixed spam bugs that were preventing command spamming from getting recognized

Additions:

• Multilingual capability through addition of lang.yml
• Build number added to dev builds
• Added ascension check to stop players from rising into the air

Modifications:

• Builds on the newest Craftbukkit/Bukkit Recommended Build (1.2.5-R4.0)
• Plugins that modify player move data are now ignored to avoid conflicts
• Console warnings are now logged as INFO and not as SEVERE
• File logs are now stored in /log/anticheat.log

Your issue should be fixed in this build, in the future please use the issue tracker.

Care to elaborate? AntiCheat version? Bukkit version? How they are flying? (up/down or across the map)?

All you have to do is replace your existing craftbukkit.jar with the newest one from dl.bukkit.org. AntiCheat 1.3+ contains an ascension check that fixes exactly what you described.

It's the giant green button.. you aren't downloading R1.0, it's R4.0... http://dl.bukkit.org/latest-rb/craftbukkit.jar

I have just the thing for you -> http://dev.bukkit.org/server-mods/anticheat/pages/q-a/

AntiCheat v1.3.2 is now online.

- Minor release build -

• AntiCheat v1.3.2 is a bugfix and new feature build

CHANGELOG:
Additions:

• Added jump potion support
• Added a debug feature for easy bug-reporting
• Added '&world' variable to command-events (via kjhf)
• Added silent mode to configuration
• Added garbage cleanup when players quit

Fixes:

• Fixed permissions issues (see Modifications below)
• Repeated messages are forgotten after a time, decreasing spam issues.
• The mcMMO dependency has been updated - if you use mcMMO you MUST be using the LATEST build. http://ci.mcmmo.org/job/mcMMO/lastSuccessfulBuild/
• Running into vines is now not considered flying
• AntiCheat now handles failures of connecting to the update service gracefully
• Fixed an issue where players would be teleported up after being falsely identified as flying

Modifications:

• Thanks to mbaxter, all permissions/sub-permissions are now handled with the plugin.yml (and some awesome cleanup and formatting, thanks!)
• All CHECK permissions have been moved to anticheat.check.xxx. For instance, anticheat.fly has become anticheat.check.fly. The permissions page has been updated to reflect these changes.
• Chatting has been switched to the NORMAL level to allow chat suite plugins to work with AntiCheat
• Repeated messages are forgotten after a time, decreasing spam issues.
• Craftbukkit removed as a dependency; we don't need it anymore.
• Coal removed from xray stats due to large amount of false-positives

It's hard to determine, but it usually does not because the NoCheat bypass is built from NoCheat, and not a single line of code from them exists in AntiCheat. It's possible that two checks may work the same and that a NC bypass could potentially also bypass AC's logic, but usually you have to look at the sourcecode for the plugin to determine how to bypass it, and ours are totally different.

Have you tried using them? We already block speed hacks.

Sorry, http://dev.bukkit.org/server-mods/anticheat/files/9-anti-cheat-v1-3-3/ (you could always go to BukkitDev)

Make sure you're using v1.3.3 and then anyone with anticheat.alert, anticheat.mod, or anticheat.admin should get the warning, nobody else.

Type /anticheat debug in-game and give me the pastebin link it gives you, then, (this is important) give a user who is getting the messages (and shouldn't be) access to ONLY anticheat.report, and tell them to issue the same command, and then give that link to me as well.