Bukkit

@unv_annihilator

You can disable the check, i will make it more configurable what to use it for.

It combines several inputs, weighted, to allow canceling actions if different kinds of actions or violations combine. Things that add in are attacking, inventory manipulation, sneaking, sprinting, attacking on the verge of the allowed distance etc. You can safely disable it at the moment, it is meant supplementary but not yet fully developed.

It helps a little against force fields, but future updates will improve on those anyway and also allow to disable it for inventories individually.

@lazertester

Donations went and still go to NeatMonster, unfortunately he is too busy in real life to continue right now, so i will take charge. Just i don't have the Manager role yet.

We are having a jenkins roughly working, it will be linked soon.

@andrewkm

Not really, it dpends on the permissions plugin, though - is it an option to add the nocheatplus.mods permission t see if that works?

@Freeezd

thx .9

@watdidyusaey

Of course rpg plugins get blocked usually, it is the job of NoCheatPlus, not because it is rpg plugins, but because those skills usually would mean cheating if just regarding the players actions. You might make a ticket for CompatNoCheatPlus for your plugin and describe what plugin it is and which skills fail and which checks alert, then i might do something about it.
(Just as an example: mcMMo creates 3 Block break events per giga drill breaker use on a block, one of the events is a "fake" or custom one. Not sure they changed that with dev builds recently. So in addition to the fast breaking speed (insta...) they also create three times the events that normally would happen. cncp provides compatibility with that though.)

Hidden flags ? All settings will be documented, but it might happen with a little delay for some things. Maybe you want to reach something certain, then you can ask directly.

Concerning potions and effects please make a ticket for NCP and describe which effects it is and probably which checks alert for those. That might speed up things.

@LordKainzo

Actually 2500 - 10000 is not so much for fastbreak, because currently it adds the overtime in milliseconds. So getting 5000 at once means you have mined blocks like 5 seconds faster than allowed given the monitored time frame (like 2 minutes), for vls it adds up and decreases slowly. We might try to adjust vls later by applying some factor, but one can't compare other checks vls too much anyway.

intervalsurvival should be <= 100, especially if you have lag issues - it is percentage of the allowed block breaking time, but in terms of "lower allows them to break the blocks faster". So with 110 it would be no wonder if people accumulate vl for breaking obsidian for sure :)

I think you can delete the buffer and interval settings, they are prehistoric remainders.

Actually if you have lag issues, it is certainly heroic to try to make fastbreak work (if you depend on rough breaking durations for economy, ignore this), but you might consider relying on the frequency check and disable fastbreak, becasue fastbreak just tries to enforce the per block breaking speeds, roughly. On the other hand it is very valuable for us to see if you get it to work...

@Dandacion Could be anything from imbalanced check (outdated version, or just too strict) to laggy clients or to hack clients not being turned off.

Important are details like version of NCP used or if any other information is known (i guess you don'T know what they have been trying).

If you know more , please add to this ticket: http://dev.bukkit.org/server-mods/nocheatplus/tickets/208-fastbreak-issues-3-7-1-beta-b/

If you are using mods with new block types employed it is inevitable that they alert with present versions.

@TNTUP

You are not running default configuration or an outdated version, what CraftBukkit version are you on ?

@TNTUP

There never is no reason, what is it ? Please update your config, some settings seem to be wrong, and which beta exactly are you using (post exact verison please)?

@LordKainzo

You can try to increase the contention amount (accumulated overtime) and/OR adjust how strongly older overtiem counts in:

a)

checks:
  # ...
  blockbreak:
    # ...
    fastbreak:
      active: true
      delay: 90
      intervalsurvival: 100
      actions: cancel vl>500 log:fastbreak:3:5:cif cancel
      # Hidden section for accumulation settings:
      buckets:
        # Normal value is 2000, i.e. allowing 2 seconds of overtime to be accumulated,
        #   before triggering violations.
        contention: 4000
      # Hidden debug flag: if set to true and give nthe permission
      #  nocheatplus.admin.debug, it will give you info about breaking times,
      #  which might help to check consistency. Should use the beta for it.
      debug: false

b)
In addition or even alternatively you could add an entry to the buckets section: "factor: 0.9" for instance - this setting defaults to 0.99 and allows to specify how strongly older overtime counts in. Overtime is accumulated for two minutes, with 0.9 entries that are 1.5 minutes old wil lcount in only 10% of their value, that could help with lag a good bit. With the default of 0.99 entries with age of 1.5 minutes would count in with 80% still.