Fair Play
Strike-Command is a competitive game. This page is the running record of how we keep it honest.
Think we got it wrong about you? Open a ticket and we'll look into it. We don't name players here.
Open a ticket →
The last 30 days
- 0Warnedlast 30 days
- 0Correctedlast 30 days
- 0Resetlast 30 days
- 0Restrictedlast 30 days
- 0Bannedlast 30 days
- 0Bansall-time
The numbers
Week by week
Actions taken against cheating, counted straight from the server. ISO weeks run Monday to Sunday, UTC.
Last 8 weeks
by action30-day mix
share of all actions- Warned–
- Corrected–
- Reset–
- Restricted–
- Banned–
How it works
Four steps. Every one logged.
Every save that reaches our servers is checked, and a save holding what the game couldn't have produced is put back to its last honest state. When cheating is confirmed, this is the usual path. Each step only comes if the cheating carries on, and some cases go straight to review.
-
01
Warning
A confirmed case gets a warning message in the game.
-
02
Final warning
If it happens again: a final warning.
-
03
24 h restriction
Next time: 24 hours off the leaderboards and out of online activities such as the World Boss, ranked, SHOWDOWN and events, with a countdown in the app and a letter explaining why. The save itself is never touched.
-
04
Review
If it still carries on, the account is reviewed by our team, and a review can end in a reset or a ban.
Warned counts accounts sent a warning message (first or final) after a review. Restricted counts 24-hour restrictions from the leaderboards and online activities (the save is never touched). Corrected counts saves put back to their last honest state; Reset and Banned are outcomes of a review. If a check ever misfires, we put it right and say so: open a ticket.
The record
By week
ISO weeks, Monday to Sunday UTC. The current week is still filling.
| Week | Warned | Corrected | Reset | Restricted | Banned |
|---|---|---|---|---|---|
| Loading… | |||||