Minecraft anticheat guide
Anti-KillAura Protection for Minecraft PvP Servers
How FairPlay approaches KillAura-style abuse through swing, rotation, target, rhythm, and no-swing context.
KillAura signals staff should understand
KillAura-style abuse rarely appears as one packet. Reviewers should look at attacks without swings, attacks without matching rotation, multi-target switching, unnaturally steady combat rhythm, and hits that ignore line-of-sight context.
No single signal settles a case. Strength comes from several weak signals agreeing in the same fight, combined with latency and knockback context that rules out benign explanations.
Evidence staff should collect before acting
For each suspect fight, preserve the check names and VL history, the measured debug values, the player's latency around the fight, and any nearby teleports, velocity changes, or inventory activity. Note whether the flags came from built-in checks or an external hook.
Redact player identifiers before sharing notes beyond the moderation team, and keep the raw evidence in an access-controlled location rather than in chat threads.
Legitimate controls that prevent false cases
High latency, custom knockback, lag-induced teleport corrections, and crowded multi-target fights can all mimic aura signals. Keep aura-adjacent checks in observation on unusual profiles, require human review before punishment, and re-test after knockback or combat plugin changes.
Document which checks are enforcement-eligible and which are observation-only for the server's exact setup, and review that split whenever the environment changes.
FAQ
Is one no-swing flag enough to punish?
No. Treat isolated signals as investigation leads, require corroborating signals plus timing context, and keep human review in the loop.
What most often mimics KillAura on legitimate players?
Latency spikes, teleport corrections, custom knockback behavior, and chaotic multi-target fights. Rule these out before escalating.