Moderation dashboard
Review the queue
The queue is players who behave like someone you have banned, closest first. Open one, read both sides, and decide.
When matches appear
Claymore compares behavior once a night, at the hour set in Settings. The queue page says when the last check ran. If that check did not finish, the list is from the night before.
Until the first successful check, the page says there is nothing yet. That is expected on day one. The check can only flag a new account against a banned player who already has a record. Let that record build up before you ban them, and look again after a later night.
Overview lists the same closest matches, with a count of how many are still waiting. Start there or open Queue in the sidebar.
How many to review
The slider is Show me the N closest. It remembers your choice on this project, in this browser. The project’s default is 25, and an admin can change that default in Settings. You can still show a different number for yourself, up to 500.
Beside the slider, Claymore suggests a queue size for the team. Early on it says Still learning. After your team has decided on enough matches, it says Tuned to your calls and estimates how many of the shown matches have turned out to be the same person. Use the suggestion, or keep your own number.
The line under the slider is how many players were close enough to flag at all. The slider only changes how many of those you see. It does not change who was flagged.
Read a match
Each row is a player, the banned player they behave like, and how close the match is. Closeness is in words: Possible, Close, or Very close. The bar beside the words marks how far past the project’s line the match sits. Hover it if you want the raw score.
Click the row to open it, or open the flag on its own page. You get:
- The comparison. The banned player on the left, the new account on the right. Look for the same habits.
- When they were online. The last 21 days. A mark on the banned player’s line is when they were banned. One person rarely plays two accounts at the same time.
- The rest of the new account’s history, under the examples.
- Earlier decisions on this pair, if the team has seen them before.
The player’s page has their full history, every time they were flagged, and a list of other accounts that behave like them. That list is a lead. Yellow on its bar means close enough that the queue would flag it.
Decide
An open match has three actions. Each one asks you to confirm, and you can leave a note the team will see.
| Action | What it does |
|---|---|
| Same person: ban | You are saying this account is the banned player on another account. They are banned too. From the next nightly check, new accounts are compared with both. Unban them later from Bans if you change your mind. |
| Not the same person | They stay unbanned. They will not be flagged against that banned player again, unless they start behaving a lot more like them. |
| Decide later | The match leaves the queue for the number of days you set, from 1 to 90. It comes back if they still behave alike. The default is 7 days. |
While the top bar says Bans not live yet, a ban is saved here and the player stays in the game. Turning enforcement on later applies bans that are already on the books. See Settings.
When the list is empty and a check has already run, the team is caught up: nobody new looks like a banned player, or every flag has a decision. Check again after the next night.