What CheaterWatch is

1. A member submits a report: a match code or a recording, a link to the profile, the moment in the recording and a description of what raised questions.
2. An administrator opens the review, and reviewers study the material independently over the next 24 hours.
3. If a majority of reviewers, with a quorum of 2 votes, sees signs of cheating, the case is published.
4. Any member can open the case, copy the prepared text and send a report in Steam.
5. The platform checks the profile against the Steam Web API daily and records a confirmed ban automatically.

A report sent straight from the game carries no explanation and no recording: the recipient sees only that a report was filed. Here the order is reversed — several independent reviewers examine the material first, and the report comes with a timestamp and an analysis. Manual review filters out submissions made out of frustration after a loss and keeps the ones worth looking at.

A single report changes almost nothing: it disappears into the general flow, and no one reviews it separately. Weight appears when many people report the same account independently, each with a reason of their own, because they have seen the recording and know what to look for. The community turns one player's observation into dozens of well-founded reports, and the chance that the account gets reviewed rises accordingly.

We do not replace Valve's decision and cannot promise a ban. A published case only means that several people examined the evidence independently and found the report justified. Each participant submits one report from their own account: reporting from several profiles harms both the case and the participant.