Bukkit

@Pr07o7yp3

Oh some reasons.

We got held up with [short version: see b) and the last paragraph below the line!]...
a) A "safeguard" was introduced in the middle of 1.4.5, leading to a considerable amount of overhead with implementation+testing+bug fixing, for almost no gain so far, though some developers might (have) use(d) this opportunity to go somewhere else. We also get told that there might be more than 0 Bukkit staff people telling other people that NCP is causing some issue in question, while it is rather to be expected to be caused by inventory manipulation plugins or CB itself. Peculiar enough, word reaches us by hearsay that at the same time other plugins are advertised by the same / similar people.

b) There are other things to patch / work on.

c) It would most likely need a slightly heavier addition/recode, which will also mean applying new technique, being instable for some amount of time. While we have to care for "bugs" which are related to Essentials or MultiVerse changing their spawn locations (their natively stored ones!), this will rather be postponed until we have an overall stable base. It might be easier to fix than the speed on ladders, which have the problem that players often dive into ladders with a high initial speed, thus we will need some model accounting for the "entry speed" for a medium and possibly even friction.

d) I have tried to keep my fingers off the basic conception of the moving/flying checks, though i adapted and fixed and re-structured parts of those and also added things, i still have a full recode in mind for those, to be able to go with more precision where precision is possible.

e) Do you know a plugin that does it better? Currently we allow like 30% speed up, some others at least recently allowed like 60% as far as i know. Not sure about SafeGuard.

The problem with very precise speed judgement is that you have to account for the medium the player is in (on-ground, air, water, web... ground+jump-in-air?, ground+jump-in-water?...), potentially also have to account for the "entry speed", cope with CraftBukkit not putting through all events (better for performance but, judging the number of packets gets imprecise and also the moment of the player touching the ground sometimes gets lost), account for varying speeds due to sneaking+sprinting+jumping+normal. The modeling has to play well with the necessary workarounds (specialties of CB/MC, incorrect positions sent, missing touch-ground, strangely shaped moves with sprint+jump), or even make them superfluous.

If we do one thing wrong with this, hack clients will update to put a short moment of sneaking or sprinting in between now and then and the check will be spoiled. So if i take a go on this, i want the modeling to be something that actually pays off in relation to the time needed to implement it.

@MyPictures

Pretty optimistic judgement :) - let's say the checks we have are for a good part well in place, and we don't expect too many surprises on quite a few of those.

There are ways to gain advantages, some still hurt (depending on the server type/situation), but most critical things are somewhat covered.

@Luzitano

You need a plugin like Orebfuscator against xray.

@jaimecamara

Force field can not be 100% blocked. But it is limited in effect by NCP.

@Luzitano

It is not (yet) blocked, if the cheater keeps to distance and event-sequence constraints.

@harl

@Apoc22932

A ticket would make sense if you really find an issue. I can't make out if there is one, or if you are just wondering if NCP does anything at all, because nothing happens.

First thing to make sure is to have matching versions of Craftukkit/Spigot and NCP. Also check the startup log if it enabled at all, or if any other exceptions with NoCheatPlus occur.

If it is on a live server with a couple of players, you can also check the nocheatplus.log file in the plugins/NoCheatPlus folder, there will most likely be some entries for the slightly higher violations, though only if someone went beyond some limits, be it cheating or false positives (some checks currently must throw false positives, like the passable check, which checks against noclip stuff - unfortiunately Minecraft lets players move before they have received and rendered the chunk they stand on, so there are small passable violations to be expected with logins and teleporting and the like).

What often happens is that people test a hack client, but still have op or the '*' or other check-bypass permissions, thus they can't generate violations.

The other thing is for servers using very few permissions for admins/techs, you might be missing the nocheatplus.admin.notify permission, which is necessary to receive in-game alerts.

So far. We need better overview pages :) .