How Detection Escalation Works
VL is tracked separately for each player and check. Reaching a buffer does not immediately mean the player is kicked: it allows that sample to add the configured
violation, and the accumulated VL must then reach kick-vl.
Units Used by Checks
Global Settings Affecting Checks
Speed Configuration
The Speed check also scales its limit for Speed potion effects and custom Bukkit walk speed. Increasing a maximum or
leniency makes the check more permissive.
Fly, Glide, Step, HighJump, and FastClimb Configuration
InventoryMove Configuration
Reach Configuration
Combat Timing and Target Configuration
AimPattern Configuration
AimPattern and BehaviorAnomaly default to kick-vl: 0 because they are statistical supporting checks. They should normally remain alert-only unless validated against substantial real-player data.
Timer and Packet Rate Configuration
PacketMoveSim Configuration
Packet Validation Configuration
InvalidPitch has no threshold option because its valid range is fixed by the Minecraft protocol. Its
buffer, violation, and kick-vl still control escalation.
WaterWalk, NoFall, and GroundSpoof Configuration
Block Placement Configuration
AirPlace uses block-neighbor support validation and therefore has no distance/timing threshold. Its sensitivity is controlled with
buffer, violation, and kick-vl.
FastBreak and FastConsume Configuration
Behavior Profiler Configuration
Behavior Profiler Weights
Each profiler signal adds its configured
weight when its threshold condition is met. The resulting weights are summed and compared with behavior-profiler.alert-score. Lower thresholds, larger weights, or a lower alert score make behavior alerts more sensitive.
Safe Tuning Procedure:
- Keep statistical checks such as
aim-pattern,scaffold-suspicion, andbehavior-anomalyatkick-vl: 0while collecting production data. - Change one threshold at a time and record the old value.
- Test normal gameplay under high ping, low TPS, potion effects, knockback, liquids, ice, slime, honey, Elytra, vehicles, teleports, and custom server mechanics.
- Raise
bufferfirst when a check is correct but occasionally noisy. Raise the physical threshold only when legitimate movement consistently exceeds it. - Do not solve false positives by increasing
violationIncreasing it makes punishment faster. Reduceviolation, increasebuffer, increase the relevant maximum/leniency, or increasekick-vlinstead. - Review the detailed flag hover information and Behavior CSV before enabling automatic punishment for a better check.