Bukkit

@fogest

Fighting, placing blocks, inventory manipulations are counted in, in general (throwing potions too, hitting at long range, altered in the latest dev builds to mainly impact fighting).

What were the players doing?

Both combined.improbable and combined.yawrate aim at bots/fighting-hacks mostly, if you disable them, you will still be "protected" better than with classic NoCheat but force-fields will be much more powerful. (also see below).

@SmashboxGaming

Not sure how you come to post about us believing anything... we are well aware of problems that people have with the improbable check. You could in fact alter the settings of the improbable check, the defaults are probably too "peaceful", though it does not seem that all servers have the same problems with it.

But mostly the balance of the inputs for this check is not good, the whole concept is under review. On our jenkins the latest builds contain some fixes and also reduce the impact of improbable on some things like block placing (using them as input with lower weight, but not blocking them). The improbable check might well get changed/removed for other concepts (event sequence analysis, timed automata, long term settings for fight.speed, mickey mouse). Before going into that, i will certainly adapt the checks influenced by lag to use information that we have from our own lag-measurement methods. That will rule out some problems with moderate lag spikes.

@Waterdust2000

The managelisteners option would let NCP only register one listener per event type with Bukkit. The main point about that was the "future purpose" of being able to register new checks / compatibility listeners, that receive events exactly before or after a certain NCP checks listener, having reliability for wrapping the event processing of NCP. With the latest MC/CB versions we had the impression that some checks listeners were not registering properly or receiving events from Bukkit, also there was no notable performance gain, so we decided to disable the feature until we have time to run the necessary debugging or if it should be really necessary to have it.

It is likely to become a hidden setting until i have time to run more tests and review the code for it.

@MyPictures

Why do we always write these long texts at the same point of time :) - i'll post it anyway :p

@MyPictures

I hardly ever see above 5 to 7 on join, going through the logs there might be some higher levels also probably with world changes (portals), rarely above 20. With 50 you should be in the hard-to-get without bugs/cheating area.

@MyPictures

Passable does occasionally alert when players join :) - could be more depending on the connections, which might be unpleasant with bigger servers. To spare the low vl messages just let actions log at higher levels and cancel for lower.

@craftovski

You can also alter the actions for passable to alert only for higher violation levels (see configuration link, something like "cancel vl>10 cancel log:..."). Not sure i will make a delay for passable alerts.

@Recolance

I don't know how good the "native" flying checks are, i think in the past those were not really working out that well. Speed check?

@XeonG8

Speed hacks still somewhat work (not an arbitrary speed gain).

Permissions are always bypass permissions, they can only be used to bypass checks, not to activate. The config flags simply turn off the check.

To explicitly allow speeding you can give the speeding bypass permission and also set the desired speed modifier (needs to be added by hand, rough guide: http://dev.bukkit.org/server-mods/nocheatplus/pages/development/pinboard/#w-survivalfly)

@Recolance

350 - I know nothing about your setup - can you add info about versions of NCP / CB and rough average tps, "ncp lag" output would also be interesting? <- If you make a ticket please add such. I assume that the problem is violations handling and lag spikes or lower tps. You should turn off logging for lower VLs (assume you have already, but you can check what it actually logs, at least confine logging to either file or console). At the cost of allowing a little more cheats you might have to turn off vertical-accounting (survivalfly), because it might generate more violations with delays/lag.

@Techtony96

Don't disable the checks, you will be nuked to hell. You can disable all hooks not needed with cncp (mcMMO needs mcMMO-hook + insta-break-hook), i will give it an overhaul with time or even integrate parts into NCP, do you have certain info about "more harm"?

@TheOros

Thanks.

@yaitsbilly

Tekkit is on 1.2.5 ? There was a backport version on GitHub but GitHub is shutting those that down, also our jenkins is causing us trouble, so we are a bit stuck here. I might give it a go to make the main-line of NCP compatible with 1.3 and 1.2.5.

@LordKainzo

Some things happened in the last few days, we are still not fully informed about the causes.

@Jleeevinnn

We are not wizards. Nodus is complying with our specifications for most - which bypasses are you having in mind (might have a look at tickets though)?

@Slipswhitley

You can disable ingame chat alerts with setting logging.ingamechat to false. You should also disable logging to console (to focus on either file or console, or disable all logging).