Minecraft anticheat guide
Review FairPlay Latency Diagnostics
Use the latency diagnostic command, including its 1–120 second duration range, to investigate combat timing.
Command bounds and permission
LatencyCommand requires fairplay.command.latency and accepts a duration from 1 to 120 seconds. It resolves a named online player and obtains the loaded BacktrackCombatSpikes check before beginning diagnostics.
If the diagnostic check is unavailable on your server, FairPlay reports that it cannot run. Confirm the check is loaded before starting a trace.
/fp latency <player> <seconds 1..120>Interpret latency diagnostics
The command collects a bounded diagnostic sample for a player and check. Use it to investigate latency-related combat alerts; it is not a direct network ping measurement or a verdict about player intent.
Do not expose player names, UUIDs, or raw records in public reports. Redact identifiers and follow staff access and retention policies. Record the collection duration and relevant server settings when comparing samples.
Review diagnostic results
The command validates its arguments before starting diagnostics. Confirm the check is loaded and review the command response when a trace is unavailable.
Follow the installed command help and compare diagnostic samples with staff observations before changing a player’s enforcement settings.
FAQ
What duration range does the command accept?
An inclusive 1 to 120 seconds. Values outside that range fail validation.
Why does the command report diagnostics unavailable?
The handler requires a loaded BacktrackCombatSpikes check instance; when it is absent, the command reports unavailability instead of fabricating a result.