Kicked for flying (or related) too strict.

[Done84]

Hello. Since i updated to a more recent version players keep getting kicked for:
"Kicked for flying (or related)"
Usually by failing survival fly checks for very small values, under a block usually. I am not sure if this is a bug or if i just need to make the check less strict.

Example:
[00:53:47] [Craft Scheduler Thread - 3190/INFO]: [NoCheatPlus] ZuckerGamesYT failed SurvivalFly: tried to move from -693.03, 31.32, 825.30 to -692.98, 31.40, 825.31 over a distance of 0.09 block(s). VL 1067.
[00:53:47] [Craft Scheduler Thread - 3190/INFO]: [NoCheatPlus] ZuckerGamesYT failed SurvivalFly: tried to move from -693.05, 31.11, 825.30 to -692.98, 31.40, 825.31 over a distance of 0.30 block(s). VL 2107.
[00:53:47] [Server thread/INFO]: [PvPManager] ZuckerGamesYT tried to escape combat and got punished!
[00:53:47] [Server thread/INFO]: §cZuckerGamesYT was slain by Axel_Awesome using [§8-§2Member9 Sword§8-]
[00:53:47] [Server thread/INFO]: ZuckerGamesYT left the game.
[00:53:47] [Server thread/WARN]: handleDisconnection() called twice
[00:53:47] [Craft Scheduler Thread - 3190/INFO]: NoCheatPlus Kicked ZuckerGamesYT : Kicked for flying (or related)

I am using build #904 on spigot 1.8.8.

Config: http://pastebin.com/s8Gj1UA6

[asofold]

@Done84 This is not 'spigot' like 'PaperSpigot'? We do prefer to have the output of '/ncp version', also to know if there are special hooks or if ProtocolLib is used :).

The log is somewhat odd, due to a dead player getting kicked for flying? Can't be 100% sure, as there are plugins changing damage, preventing death, teleporting players, etc. (Fail survivalfly -> Tried to escape combat and got punished (how?) -> slain -> kicked for flying ) Are there combat logging plugins in use?

[Done84]

Its regular spigot.

I am using PvPmanager to avoid combat log, I've used it for years along side NCP. After NCP kicks the players for "fly" PvPmanager detects it as combat log (when the player is in fact in pvp). But this also happens without players being in Combat Tag. It also happens with the 'passable check' where players often get stuck into blocks wile mining and time out.

Here are some more log examples: http://pastebin.com/270541D9

It looks like it has a much higher chance of false positives when the player is lagged, but then again, this goes for a lot of NCP checks, also when teleport plugins are involved it also makes it more likely to trigger the kick.

This server is running CraftBukkit version git-Spigot-db6de12-18fbb24 (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT)

INFO Hooks: AllViolations(NCP) 1.0 | mcMMO(cncp) 2.3
INFO packet-listeners: UseEntityAdapter | MovingFlying | OutgoingPosition | KeepAliveAdapter | SoundDistance
INFO defaults: pvpKnockBackVelocity
INFO checks: FastConsume | Gutenberg | AttackFrequency | FlyingFrequency | KeepAliveFrequency
INFO blocks: BlocksMC1_4(base) | BlocksMC1_5 | BlocksMC1_6_1 | BlocksMC1_7_2 | BlocksMC1_8
INFO Features:
INFO MCAccess: 1.8.4-1.8.8 / Spigot-CB-1.8_R3
INFO Plugin: 3.13.5-SNAPSHOT-sMD5NET-b904
INFO #### NoCheatPlus ####
INFO (detected: 1.8.8)
INFO git-Spigot-db6de12-18fbb24 (MC: 1.8.8)
INFO #### Server ####
INFO ---- Version information -

[asofold]

Build 901 is already slightly outdated, though there has been another bigger change towards build 914 (or even 920).

[Done84]

I will update and report back. One question thought, i remember many versions ago i would get a console warning about having to regen my config, now it looks like that feature is gone. How do i know when i should regen it to default then re-edit all my custom commands, messages etc?
Sometimes new stuff is added and if i don't regen it i don't think it shows in the config.

[asofold]

@Done84 NCP will bully server owners with the configuraiton, if we overwrite an existing configuration value, or if we remove values that might be of relevance.

If NCP hasn't complained since, we have not changed the config in such ways, or we forgot to set the 'last change' build. This is very coarse, it doesn't check if you have values set differently than in the default configuration, it just checks the build that you generated your configuration with (configversion section).

To get an estimate if/what we might've changed you could refer to the build-infos page: https://github.com/NoCheatPlus/Docs/wiki/Build-Infos

There we might advertise config changes, e.g. like with build 699: https://github.com/NoCheatPlus/Docs/wiki/Build-Infos#31012-snapshot-smd5net-b699cumulative

[Done84]

I'm now on build 922 and i still have the same issue.
http://prnt.sc/a8tca5

If a player teleports and stands on top of 'half' block like a enderchest,chest,enderframe the trigger goes even wilder.

[asofold]

So they trigger survivalfly standing on an enderchest 'just having teleported there' ?

[Done84]

@asofold Yes. It triggers if they teleport, if they are just standing around on them it triggers but only on occasion, but that's not my concern the real problem are the constant passable false positives for distances such a 0.10 blocks, it happens way to often, im not sure but it might be related to players who suffer from more Lag. Survival fly also trigger a lot.

I recorded 2 mins of me teleporting to each player that gets a positive, maybe it can help.
https://www.youtube.com/watch?v=xAc8Af1TZyg&feature=youtu.be

[asofold]

Passable violations with 0.1 distance (downwards) are bound to happen with Minecraft design-wise. Players just send 'slow falling' moves during rendering and NCP has to prevent the moving.

The non-full blocks / teleporting is still related to the kicking? Perhaps that should be an extra issue, if not.