How anti-cheat works — and what happens when someone gets caught

How the system identifies suspicious behavior

Azeroth Legacy's anti-cheat operates on multiple layers:

Automatic detection in real time: the system monitors metrics such as movement speed, hit rate, reaction time, loot patterns and behaviors that go beyond the physical limits of the game. A character moving faster than the mount's maximum speed, for example, is automatically flagged.

Pattern Analysis: Repetitive and impossible behaviors (such as attacking without animation, collecting resources with inhuman precision, or logging in/out in a bot pattern) are identified by sequence analysis.

Community Reports: Players can report suspicions. Reports validated by multiple independent players have greater weight in screening.

Case analysis and validation flow

Being flagged by the system does not result in automatic punishment. The process is:

1. Automatic flag — system detects anomalous behavior
2. Manual screening — team reviews character logs
3. Context Check — server bugs can cause false positives (e.g. extreme lag resulting in incorrect speed)
4. Decision — if confirmed, the punishment is applied; if false positive, flag is discarded
5. Notification — player is informed of the decision

Types of punishment and criteria applied

Punishments vary by severity and recidivism:

• Formal warning — first mild occurrence, no history
• Temporary suspension — infraction confirmed, duration proportional to severity
• Permanent ban — use of third-party software (hacks, bots), confirmed speed hacks or serious recurrence
• Item rollback — in cases of economy exploit or item duplication

Infractions that affect other players directly (speed hack in PvP, raid mechanic bypass) have more severe punishment than solo infractions.

Appeal and review rights

Every punished player has the right to contest via ban appeal. The process guarantees:

• Review by a different member of the team that applied the punishment
• Deadline for sending evidence in favor of the objection
• Formal response justifying the final decision

Full details in the ban appeal post.

Tips to avoid behavioral false positives

• Report extreme lag when it occurs — lag can simulate behaviors that the anti-cheat flags
• Do not use unauthorized software — even non-standard addons can generate alerts
• Avoid macros that simulate inhuman inputs — sequences that are impossible to execute manually are suspect
• Document bugs that affect your character — if something strange happens to your speed or position, file a ticket before the anti-cheat catches you