Bukkit

@imaxorz

That is the flying checks by CraftBukkit. If you stand in mid air you get pulled down.

NeatMonster made attempts to do something about it, but i am not sure if the nomovedtooquickly option is really safe to use, some people were experiencing problems with it.

There might be client side fly mods that allow better compatibility, but i am not into it right now.

CraftBukkit version might matter if it is about the creative flying qursiton (teleports, world changes: CB 2357 fixes, supposedly).

@andrewkm

It will be subject to revision, though there are many servers that rely on a pretty rigid chat handling and probably have to due to the amount of online players, so we will have to provide some default configuration that allows reasonable protection against real spam attacks out of the box.

Still first you have to check your version, if you had a version with globalchat active, the latest builds changed some things and you might have to regenerate parts of the configuration (its enough to delete the paramters like level etc. no need to remove command lists.).

Then you need to find out / know which check actually forces them into captcha, currently there is nopwnage and globalchat. Knowing which prevents what can help to know what part of the configuration to adapt.

I will try to add a "quick page" about configuration of developement features, which are not well covered by the other documentation, yet. That will cover Flying and speed, chat. i will link it from here and from the configuration page soon.

@lbb601

It should be: nocheatplus.checks.chat.globalchat

The parent nodes are not yet set up so one has to give it explicitely, most likely (indev...).

@VergilPrime

Uncanceling has been fixed quite some time ago.

And maybe you can describe your problem more precisely - what does "gives me my ....." mean?

I assume you are using an old version of NoCheatPlus, best update to the latest, to be found at: http://www.nocheatplus.org:8080/job/NoCheatPlus/

Build 63 addresses some issues, some might get reverted due to concept changes, but some might be lasting improvements:

• NoPwnage speed checks have been adjusted to work.
• NoPwnage exclusion list and globalchat commands both work as prefixes now, allowing spaces etc. - so you can exclude or count as chat commands only starting with "/chat advertise" for instance, so other "/chat" commands would not be matched. Since build 64 you can add spaces at the end of entries (- "/chat "), so that an entry like "/chat " would not match things like "/chatmonger".
• Add possibility to allow speeding (horizontally). Permission is nocheatplus.checks.moving.survivalfly.speeding , however you need to add a config setting by hand into the survivalfly section, like speedingspeed: 200
  100 would be 100% of normal speed, thus 200 is two times the normal speed. It applies to the normally allowed speed including ice etc., but it only works for walking and sprinting by default.
• Checking for updates is configurable now.
• Some minor fixes.
• Attempted to fix the step hack detection.

Other changes in the recent builds:

• Add to chat prodcessing: "globalchat"
  • Medium term violation tracking.
  • Attempts to count in several annoyances, such as upper case, some kinds of trash.
  • List of commands to count as chat.
  • Clearly experimental features can be disabled with the engine section (Global word use cooldown + letter order repetition, something). Expect "changes".
• Adjusted nopwnage to work almost fully on actions (needs adding a kick command, or let the config section regenerate).
• Extra VL and actions for the captcha processing.
• Added commands for convenience of actions definition.
• Various small bug fixes.

(See for commit list: http://www.nocheatplus.org:8080/job/NoCheatPlus/changes)

@MasterGabeMOD

I don't know.

Somebody (NeatMonster?) wanted to adjust the roles, i think. I will have to ask him...

@dotapurex1

That may be your judgement, how about disabling the captcha, setting active to false for the captcha section in the configuration (checks -> nopwnage -> captcha -> active: false)?

I also favour a review of how to configure it and what the default settings should be (for instance banning etc, for chat), but currently it is set to active by default. How the captcha looks like in chat might also be subject to change, for instance sending a multi line "image" of the captcha instead of an easy to parse message.

@icheesy

The captcha bypass permission is mostly useless, because without captcha the normal nopwnage checks and possibly actions are run. Only difference to disabling captcha alltogetehr is that you can disable it for a player. Usually the nopwnage actions are more severe than captcha, like kicking or banning so it might not really pay to disable them for some players only.

(Edit: probably not that much useless for they can be used with globalchat too.)

You can disable captcha in the configuration, the permission is:
nocheatplus.checks.chat.nopwnage.captcha

For speeding you can currently not distinguish flying and speeding for individual players (maybe worth a ticket) - you can add values for flyingspeed, walkingspeed, sprintingspeed, blockingspeed, sneakingspeed in the survivalfly section of the configuration. 100 is the normal value.

What do you want to allow speeding for actually?

Just to allow people to wlak faster, or also to swim faster, run faster while blocking / sneaking etc. ?

@GuildMasterLelo

1. Over the beta build i would recommend the developement build CB 2357, because it fixes some issues, also related to creative flying with teleports or world changes.

2. As MasterGabeMod said, YOu should use the latest developement version.

@chrishillz

I am not sure what the problem is, actually - are there any kick commands issued for spam violations ?

There could be some cross plugin issue, because NCP is using the asynchronous chat events, on violations NCP will let them be synchronized into the main thread by a custom event (i.e. waits for the man thread processing that). So it could happen that plugins receive the asynchronous chat event after NCP at a moment after NCP has already run the actions, whatever commands are defined in there.

The latest developement versions rely on the actions for banning + kicking only, so if you are using an outdated configuration file, the kick entry might simply be missing.

Not sure if any of your other chat protection plugins (if i understand right, you have some) should perform kicking and fail.