Minecraft anticheat guide
Hit Registration Complaints: Ping, Fairness, and Triage
How to triage a PvP hit-registration complaint by separating ping, server tick lag, and anticheat misfires before you change any check settings.
Why do hits fail for reasons other than cheating?
A hit that did not register can come from several places. Network latency means the client and server disagree about where the player and target are. Server tick lag delays how the server processes the hit. The client's own timing can differ from what the server accepted. An anticheat can also cancel a hit if a check or mitigation acts in that window.
Each cause leaves different evidence. The first job is to find which one is present, because each needs a different fix.
The complaint itself is often a weak guide. A player who says a hit did not register may have seen it land on their screen while the server rejected it, or the reverse. Neither account is wrong about what the player saw. Both can be true, which is why the logs matter more than the description.
Which symptom points to which cause?
Use the symptoms below to choose where to look first. Treat the table as a starting point for the investigation, not a diagnosis.
| Symptom | Check first | Evidence to collect |
|---|---|---|
| Hit looks landed on the client but deals no damage on the server | Latency and desync | Ping for both players at the time of the hit |
| Repeated misses for one player only | That player's connection or client | Ping trend over several fights |
| Misses that cluster after a lag spike | Server tick lag | Tick health for the same window |
| Hit cancelled with an anticheat alert or mitigation entry | Anticheat mitigation and check scope | Alert and mitigation entries for the same window |
What is the triage order for a hit complaint?
Work in order. Each step narrows the cause before the next one, and each step should leave a note. A complaint closed with no notes gives the next admin nothing to work from.
Do not change anticheat sensitivity during the first pass. A setting change can hide the evidence you need.
Record how long each step takes. A complaint that takes an hour in the logs can point to an alert format or log retention problem that is worth fixing separately from the complaint itself.
How should fairness work for high-ping players?
Fairness has two sides. A player with high latency can experience hits differently from a player on a short connection, and that gap is a real complaint. Loosening checks for everyone to help one connection increases the room for cheats, so the fix needs to be narrow.
Prefer changes that target the specific cause in the triage. If the evidence shows a check acting on lag rather than on player input, the review should say so, and the change should be documented with the evidence that supports it.
Fairness also means treating similar complaints the same way. If one player's complaint leads to a change, the next complaint with the same symptom should go through the same triage steps. Keep a short list of the triage outcomes you see. Over time it shows which causes come up most on your server, which tells you where staging time is best spent.
Be clear with the player about what the review can and cannot show. The logs may confirm a latency cause without proving the hit should have landed, and that distinction matters for the player's trust in the outcome.
What we have not verified
This article does not give a ping limit, a tick threshold, or a measured effect of any anticheat on hit registration. We have not tested hit registration across different latency levels on any server.
Reproduce the complaint on your own staging server with the same client and network conditions before you decide the cause.
FAQ
Does a high-ping player always need an exemption?
No. An exemption widens the room for cheats. First confirm that the anticheat acted on the lag, not on the player's input, and then decide on the narrowest change that fixes it.
Can the anticheat cause missed hits?
A mitigation or cancellation feature can stop a hit from applying. Check the log for the same window. If there is no entry, the cause is more likely latency or tick lag.
What should I tell the player while I investigate?
Tell them the time you are looking at, what you will check, and roughly when they can expect an answer. Do not promise a result before the logs are reviewed.
Is one complaint enough to change a setting?
No. Look for the same symptom in other fights and in other players' logs before you change anything.
How often should staff review hit-registration logs?
Review them when a complaint arrives, and also after any server update or network change, because those events shift latency and tick health. Compare the same windows before and after the change so you can see whether the pattern moved.