Bukkit

@UnitedFactions

kNoHax 0.5 only counts how often a player attacks another player within a certain timeframe, something that already "mxAntiPvPCheats" did in the time when it still worked (broken now). And that was easily bypassed by hacked clients by reducing the number of attacks per second to whatever the plugin expected to be "normal".

NoCheat checks not only checks for that, but in addition for attack distance (was the target really in range during the attack?), direction (did the attacker actually look at the target?) and if the player actually moved his arm when attacking.

@cvxx7q

Yes, no new features. Only fixing stuff that breaks because of Minecraft updates and similar.

@UnitedFactions

PS: I just saw that the kNoHax developer removed the line that said "we recommend using this in combination with NoCheat", so forget what I said. It seems it is no longer possible to use both.

I'll follow the progress of kNoHax and see where it goes, but atm. it's just too early to say if it really is effective in what it does or not. NoCheat has now taken over 1 year of constant attacks from hack client developers who started to specifically design their hacks to not get detected by NoCheat, yet I'm still here and stronger than ever.

Once servers start to remove NoCheat in favour of kNoHax and therefore client developers start to adapt their clients to kNoHax's detection algorithms to prevent detection for e.g. flying, we'll see how good it holds up.

PPS: kNoHax has one design flaw that they can't even fix. Griefers have started to use "alt" accounts regularly, almost none of them use their real accounts for griefing. Therefore banning isn't really a threat to them and they'll just grief the server and players for as long as they can, until an admin finally bans them. Then they come back with another "alt" account and start again. That's essentially why I don't think that detection alone is a viable way to secure a server.

These are my thoughts about kNoHax in a nutshell.

@cvxx7q

I feel good. Only one thing left on my to-be-patched list that I want to do before taking a break from NoCheat development (maintainance only for a while).

@raoulster

I recommend orebfuscator + orescrambler. That combo is unbeatable and prevents all variations of X-Ray hacks by not only preventing the players from knowing where ores are, but also changing their location slightly to prevent players from making a copy of the map (with the world seed value that you see when pressing F3) and finding the ore locations that way.

@UnitedFactions

It does not do the same thing as NoCheat, as the developer points out on his page. NoCheat works on making the game fair by preventing cheating when it happens, his plugin focuses on detecting it. Two very seperate goals. NoCheat already handles the attack range issue in the latest versions btw by limiting it to 4.25 blocks (the server allows 6 blocks).

There will never be a integration of knohax or parts of it into NoCheat, because the basic ideas are different, the execution different and last but not least, his plugin is closed source, therefore I can't use any of his work in NoCheat (opensource MIT license), even if I wanted to.

According to his page you can use both at the same time anyway, so I'd suggest just doing that.

@acetech09

Just use e.g. "nocheat.checks" without the ".*" All permissions are defined the way that parent permissions include all the child permissions. E.g. "nocheat.checks" includes "nocheat.checks.moving", "nocheat.checks.moving.morepackets", ... automatically.

Using a ".*" at the end is not necessary and may even break this behaviour (depending on the used Permissions plugin). So for NoCheats permissions, simply avoid using the ".*" and everything should work fine.

NoCheat 3.3.0:

• added an additional safeguard to interworld teleports
• log messages from "chat.spam" are now cleaned of color codes of players
• spellchecked and fixed a lot of errors in the Instructions.txt file
• fixed bug in instantbow/instanteat checks that prevented them from working correctly
• added check "fight.godmode" which should prevent players from exploiting a design flaw that makes them invulnerable to attacks
• added "hidden" options to set walking/sprinting/swimming/sneaking speed limits. These don't show up in the automatically generated config, because almost nobody should need to change these. But you can add these options yourself to plugin.yml. See "Instructions.txt" for details.

Longer explaination here: http://forums.bukkit.org/threads/sec-nocheat-v3-3-0-detect-and-fight-the-exploitation-of-various-flaws-bugs-in-mc-cb-1-1-r3.4523/page-76#post-960308

@CoolOppo

I found out why the instantbow check wouldn't work. It'll be definitely fixed in the next version, which I'll finish within a few hours.

@PublicPerv

Everything looks ok there. What exactly doesn't work? If it is flying, then check if you have deactivated "towny"s anti cheat functionality (or given appropriate permissions, I don't really know how "towny" handles this stuff in detail).