FastBreak Coverage Map: Which Break Check Answers What

Short answer: what the FastBreak map covers

Per FairPlay engineering notes, FastBreak coverage is a set of checks, and each one answers one question about block breaking. Most read the start and finish dig packets with their timing and target data. One reads the server-confirmed break event for look direction. The checks keep state per player and reset it on teleport or quit. A match means one question failed, so read the check name before the player name.

Coverage by question

Use this table to turn a check name into the question it asks. The action column shows what the notes say the check does when it fires.

Why one-tick mining is not an automatic violation

A start and a finish in the same server tick is a legal packet sequence, per the notes. The sequence check does not flag it for sharing a tick. The timing check still reads the block material and the dig session. It excludes instant-break blocks at or below its ignore threshold. An ordinary block must meet its calculated expected time plus allowances.

So the same-tick pattern is not automatically legal for every block, and it is not suspicious by packet ordering alone. Judge it by the block and the timing evidence.

Why burst checks do not use one break per pong

The notes reject one break per pong and one block per flying packet as models. The pong burst check sets its allowance from elapsed server ticks plus skipped markers, up to a maximum allowance. A delayed client that skips markers gets a larger allowance, not a flag for a fixed quota.

Clean intervals decay the buffer, so one busy interval does not carry forward. The multi-break check follows the same epoch idea for flying packets.

How to read a break alert

• Identify the group from the table. Timing, burst, geometry, look, and sequence each need different evidence.
• For timing and burst alerts, check the player's ping history for the same minute. The notes allow for latency, so a spike in that window weakens the case.
• For tool-related timing, check whether the held item changed. Per the notes, a dig session keeps the tool it had at start. An unresolved tool fails open rather than flagging.
• For geometry alerts, remember that missing or unknown collision data is recorded as unknown and never flagged. An alert from these checks means the geometry was available.
• For look alerts, check whether the player's head moved visibly during the window. The notes say visible head movement resets the static series.
• Compare the pattern across breaks and sessions before you decide. One block rarely tells the whole story.

What is still unverified

Per the notes, Minecraft runtime verification is unexecuted and remains the server operator's job. The external overlap table matches check names across public anticheats. The notes say a name match is not semantic parity or runtime proof.

Read the map as a statement of code coverage. Before you rely on alert volume, test legitimate mining on a staging server at several tool and ping levels. Compare the defaults in the configuration reference with your own generated files, since an older install may keep older values.