Minecraft anticheat guide
Packet Order Checks for Scaffold and FastBreak
How packet order helps detect impossible block placement, digging restarts, and burst abuse.
Chronology is the evidence, not the trick
Packet-order checks read the sequence of client messages as a timeline: for scaffold, placement, swing, interact, rotation, and slot packets in order; for FastBreak, digging start, cancel, and finish interleaved with slot changes and movement. Legal play produces timelines consistent with the client's claimed actions; automation produces timelines that contradict them.
This page describes that chronology conceptually for server owners. It publishes no evasion guidance and no check-specific thresholds.
Two conceptual timelines reviewers should know
A scaffold timeline asks whether each placed block had a preceding swing and interaction in a plausible order with consistent rotation and slot state. A FastBreak timeline asks whether each break followed a legal digging progression for its block and tool context, without impossible restarts or overlapping sequences.
Both reduce to the same review question: does the message order tell a physically possible story? Staff need the recorded order, not just the verdict.
Non-evasion staging for sequence checks
Stage sequence checks with consenting builders and miners covering the server's blocks, tools, and latency range. Keep checks alert-only until legitimate sequence variation is mapped, especially around lag, high ping, and rapid but legal play.
For appeals, preserve the contradicting order itself with timing context. Sequence evidence is reviewable without disclosing internals.
FAQ
Do packet-order checks replace timing thresholds?
No. Order and timing corroborate each other: order shows whether the story is possible, timing shows whether a human could have told it.
Why no thresholds or bypass details here?
Because publishing evasion-relevant specifics would help cheat developers. Thresholds belong to staged server measurement, not public pages.