Elytra Aim and Hit Sync Checks Explained

What do the Elytra aim and hit checks observe?

This group focuses on aim and on the hit, not on the glide itself. FairPlay names checks for aim lock, centre-mass lock, hit sync, no-look hit and rotation consistency. They ask whether the view tracks a target the way a human head and mouse do, whether hits land when the aim and the hit timing agree, and whether a hit can happen without a matching view on the target.

Because the checks read the view and the hit together, the order and timing of those two events matter as much as either value on its own.

Which cheat behavior is the target?

Aim assistance during gliding fights tends to hold the view on a target's centre, or to land hits with the crosshair elsewhere. Some tools also turn the view in a repeated way after each hit. The checks in this group compare the steadiness of the view, the spot on the target that receives hits, and the timing of the hit relative to the view.

The aim checks do not decide whether a player is strong. A very good player can keep a clean aim line, so the evidence needed is a pattern that holds across different fights and situations.

Context matters for aim too. Duels, team fights and long chases produce different views, so a fair review compares a fight with fights of the same type and records that type in the case notes.

What legitimate aim can look like?

Strong PvP players often keep the crosshair on the chest or centre during a chase, and that looks steady to a check. Players who hit as they pass by may have the view already on target for a brief moment, which can look like a no-look hit when packets arrive in a different order.

• Players who keep the crosshair on the centre of the body during a long pursuit.
• Players who strike as they pass, with the view on target for a short moment before the hit.
• Low mouse sensitivity, which makes small view changes look very steady.
• Hits delayed by a firework that finishes just after the swing.
• Lag that delivers the view update and the hit in different packets.

How should staff read these alerts?

Each alert in this group asks a different question about the same fight. Use the table to pick the first question for the alert in front of you, then pull the matching evidence before you decide.

What is the safe procedure for a hit sync alert?

Hit sync alerts are sensitive to packet order, so reviewers should check delivery before judging the player. The steps below keep the decision tied to the evidence.

• Confirm the alert happened inside a fight, not in a lobby or during a respawn.
• Compare the ping history for the same window with the alert timing.
• Compare the fight with the player's other fights on the same weapon.
• If your policy allows it, ask the player to describe their setup and sensitivity.
• Record the decision, the evidence reviewed and what you ruled out.

What should you tune only in staging?

Test these checks on the same combat settings your players use, including knockback behavior and any custom combat plugin. Keep the group alert-only until reviewers agree that the alerts read correctly. Change one check at a time, because the view and hit checks share inputs and a change to one can shift the others.

Read the per-check reference before editing, and do not copy settings from another server. A setting that suits a fast duel server may not suit a slower factions map.

What have we not verified?

We have not measured how often these checks fire on live servers, how they respond to each mouse and sensitivity combination, or how they compare with other anticheats. This article describes what each check is named to observe. It does not claim that the checks catch every aim method.