Minecraft anticheat guide
FairPlay BadPackets, Criticals, Timer, and Macro Checks
A focused look at FairPlay utility checks that catch repeated slot packets, spoofed criticals, swing timing, macro damage patterns, and invalid packet behavior.
Small packet abuses add up
Not every cheat presents as a huge reach or obvious speed hack. Repeated held-slot packets, spoofed critical conditions, suspicious swing timing, invalid placement, and macro-like damage patterns can all support larger abuse workflows.
FairPlay includes utility and combat-adjacent checks such as BadPacketsRepeatedSlot, CriticalsSpoof, SwingTimer, MacroDupeDamage, and InvalidPlace.
Why these checks matter
Utility checks improve the evidence model. A combat flag becomes more credible when paired with packet-order anomalies, timer rhythm, invalid placement, or macro patterns. Staff can then make better decisions from combined context.
Tuning advice
Keep these checks visible during rollout. Some servers have custom inventory, combat, or item behavior that can change packet patterns. Use debug values before command punishment, especially on heavily modified servers.
Other check categories
FairPlay also includes checks for Macros, Criticals, Misc, Place, and Timer. FairPlay focuses on combat and related player actions rather than general Fly or Speed detection.
Use the check name and its settings when explaining an alert. Review the evidence before deciding whether to change configuration or apply punishment.
FAQ
Does FairPlay include BadPackets checks?
Yes. FairPlay includes BadPacketsRepeatedSlot and other combat-adjacent utility checks.
Why care about CriticalsSpoof or Timer?
These signals can expose client behavior that supports unfair combat even when reach or aim alone is not enough evidence.