KillAura Rotation and Swing Checks Explained

What do the KillAura checks observe?

KillAura checks look for attacks that do not match how a player aims, swings and moves. FairPlay names five KillAura checks: no rotation, no swing, multi-target, combat rhythm and attack-to-move timing. A separate critical-hit spoof check covers attacks that claim a falling hit when the player's movement does not support one. Each check asks a different question about the same fight.

A single check rarely decides a case. The useful signal is several checks agreeing across a fight, read against the player's usual combat.

Keep in mind that combat rulesets change what a normal fight looks like. Attack cooldowns, knockback and sweep rules all shift the timing and the target lists, so a fight that is odd on one ruleset can be routine on another.

Which cheat behavior do these checks target?

Aura modules attack without turning toward the target, attack without playing the swing animation, switch between several targets very quickly, or time attacks to a fixed rhythm. The critical spoof check targets clients that claim a falling hit without falling.

Each target behavior leaves a different trace. A module that never turns leaves a view that stays put while hits land. A module that never swings leaves hits with no arm animation. A module that spreads hits across targets leaves a target list that changes faster than a person can manage.

What legitimate combat can resemble these patterns?

Plenty of normal fights produce these shapes. A target that is already directly ahead needs no turn, so a no-rotation alert on a close fight deserves a second look. Sweep and cleave attacks hit several entities at once, which can look like multi-target behavior.

• Attacking a target that is directly in front, where no turn is needed.
• Sweep or cleave attacks that hit several entities in one action.
• Players who attack once while moving to a new spot, which can look like attack-to-move timing.
• Fast players with a steady rhythm during a long fight.
• Lag that delivers a swing after the attack, so the two look out of order.
• Critical hits from ordinary jumping and falling during PvP.

How should staff read KillAura alerts?

Match each alert to the question it asks, then pull the evidence that answers it. The table gives the first question and the most common legit cause for each check in this family.

What is the review procedure?

Review each fight, not each hit. A reviewer should see the whole fight before judging any single attack.

Note the number of players present and the map, since a fight in a crowded area gives legitimate sweep attacks more targets.

• Confirm the alert came from a real fight, not a lobby, respawn or mob area.
• Check the ping and the combat settings the fight used.
• Compare the fight with the player's other fights on the same weapon and map.
• If your policy allows it, ask the player to describe their combo and setup.
• Record the decision, the checks involved and the evidence you ruled out.

What should you tune only in staging?

Combat checks interact with knockback plugins, custom combat rules and the attack cooldown your server uses. Test on the same combat settings your players use, and include PvE and mob areas if players fight there. Keep the family alert-only until reviewers agree on how legit combos read on your server.

Read the per-check reference before changing anything. Do not copy values from another server, because the same numbers can mean different things under a different combat ruleset.

Test on a copy of the ruleset your players actually use, and include at least one fight with a second player who moves quickly, so you can see how the checks respond to ordinary chases.

What have we not verified?

We have not measured how often these checks fire on each combat ruleset, how they respond to each combo, or how they compare with other combat anticheats. This article describes the public check names and the behavior each one is named to observe. It does not claim that any single check catches every aura module.