FairPlay Reach, Hitbox, and Occlusion False Positive Control

Reach is geometry plus timing

Reach is not just a raw distance number. A serious check needs eye position, target hitbox, rotation state, packet timing, possible latency uncertainty, and block occlusion. A single hard distance threshold can be too blunt for real servers.

FairPlay's hitbox, reach, cone, and occlusion coverage is meant to give combat-focused servers stronger proof around whether an attack was plausible.

Occlusion matters

Attacks through blocks, suspicious line-of-sight, and block-covered targets need separate handling from open-air reach. Block occlusion checks help staff distinguish long hits from hits that should not have had a clean path at all.

Tuning advice

Use debug variables before punishment. Account for knockback, teleport, server corrections, high ping, target interpolation, and custom combat plugins. Configure mitigation first, then add automatic punishment only after enough clean production evidence.

Hitbox authority and cancellation are different stages

Hitbox checks and violation responses are separate parts of combat review. A cancelled action alone does not show which geometry check triggered; review the alert and mitigation details together.

Packet and client-view state can affect the context available to a hitbox check. Review alert details and stale-state indicators before making a staff decision.