Players and bans

Find a player

Open Players, or use the search in the top bar. Search by username, display name, or a Roblox or Discord user ID. A user ID has to be the whole number. A username can be the start of the name. Two characters is the minimum.

Results show the platform, the display name, whether they are banned or active, and Claymore’s own ID for them. Open the row for the player page. If nobody matches, try the start of the username. After a Roblox test, wait about a minute and search the username you used in the game.

The player page

The page is that person’s record in this project.

• Who they are. Platform user ID, Claymore ID, and the names they have used.
• Activity. First seen, last seen, recent play time, and whether tonight’s check can compare them. A player without enough of a record yet is not compared. A banned player with too thin a record before the ban cannot be used to find alts.
• Times they were flagged, with the decision on each one. Open a night to reread that match.
• Players who behave like them. The closest behavior on every platform the project receives, or only the same platform, or only the others. Treat the list as a lead. A yellow bar is close enough that the queue would flag it.
• Their history in this project.

The small fingerprint beside the name is drawn from their behavior. The same drawing shows up next to a match, so you can see two accounts side by side. It is a picture of the comparison, not a separate verdict.

Ban from the player page

Ban this player bans them directly, which is different from banning a look-alike out of the queue. You give a reason the team will see. They become the original account of a new ban group. Later queue bans that point at them join that group as alts.

If they are already banned, the page says when, by whom, the reason, and whether they are the original account or a look-alike. See their ban group opens Bans filtered to that group.

The Bans page

Bans lists everyone the team has banned. Each row says whether they are the Original account or an Alt, whether the ban came From the queue or they were Banned directly, the reason, and who banned them.

Filter the list with the two switches:

• Banned now, Unbanned, or All.
• Any way, Banned directly, or From the queue.

Search matches a username, a player ID, or the reason.

Unban asks for a reason. They can play again, and they leave their ban group. The rest of the group stays banned. If they were banned as a look-alike, Claymore treats the unban as “not the same person” and will not flag them for this again unless they start behaving a lot more alike.

While Bans not live yet is in the top bar, unbanning and banning only change the dashboard. Once an admin applies bans in the game, a ban here is what the game enforces. See Settings.

Delete a player’s data

An admin can delete a player from their page. This is for a deletion request from the player or their parent. It removes their record and any flags that quote them. The audit log records that you did it, without their name.

If they are banned, the ban stays, so the same account is still banned if they come back. Type delete to confirm. This cannot be undone.

Player data is also removed on its own after the project’s retention window. A banned player’s record stays while the ban is active, because new accounts are compared with it. The default is 90 days. An admin changes it in Settings.