Bans list

The Bans List holds the bans currently in force on one server. A ban that was lifted leaves the list immediately but keeps its row, so the audit trail survives and the Total Bans counter on the server home keeps counting it.

Finding a ban

The search box matches the player name, the ban id, any identifier, any hardware id, and the ban reason, so pasting whatever fragment a player gave you in a ticket is usually enough. Sorting offers name A to Z, name Z to A, oldest first and newest first. Newest first is the default, which is what you want when someone was just banned and is already complaining.

Each card shows the ban id, the player name, the reason, who issued it, the date, and Permanent. Dashboard bans have no expiry, so Permanent is a statement of fact rather than a setting you missed.

The detail panel

Clicking a card opens the full record:

• A Manual tag when an admin issued the ban by hand. No tag means a detection issued it.
• The ban id, the reason, who issued it, when, and when the row was last updated.
• Proof, when the ban carries a capture. A screenshot renders inline and opens full size in a new tab. A recording plays in place. If the capture was already reaped to save storage the panel says so instead of showing a broken frame. When the game handed back an empty frame there is nothing to reap: the anticheat stores no file at all and the ban carries the black screen card as its capture, so the panel shows that card and says the frame came back empty rather than leaving a dead capture to be read as a ban that never had one.
• Identifiers and HWIDs, each with a copy button. These are what the ban actually matches on when the player tries to reconnect.
• The detection context the resource sent with the ban, when there is any. This is the raw evidence behind an automatic ban, and it is what tells you whether a detection fired on something your own scripts do.

Banning an offline player

Ban Offline covers the case where someone left before you could act. It needs the ban create permission.

If this server already has a ban row carrying any of those identifiers the request is refused with Already banned, so you never end up with two rows for one person. That check looks at every ban row, including one you lifted earlier, so re-banning someone you previously unbanned is refused here. Ban them from the Players List while they are connected instead.

Unbanning

Unban needs the ban remove permission. It is a soft action: the row stays, gains the time, the actor and the reason, and stops being enforced. Any trust penalty the ban applied to the player is refunded by exactly the amount that was deducted, so a ban followed by an unban leaves the score where it started.

When the ban carries detection context you get a second button that unbans and records a Raven Mind rule at the same time, so the detection stops firing on whatever caused it. Choosing to just unban with no rule is always offered as well, and it changes nothing about your configuration.

What a ban does not cover

This list is yours alone. Bans that Raven staff issue across the whole network are a separate list with a separate switch, described on Global bans. Unbanning someone here does not lift a global ban, and a player blocked by a global ban never appears on this list.

Every action on this page writes a row you can find later under Activity log, and an unban row there offers Restore ban if you changed your mind. Bans issued while the license is expired are refused outright, with a renewal message, because a ban list you cannot enforce is worse than none.

Ban ids are written as ban-<timestamp>-<random>, which is the id a player reads off the rejection screen when they open a ticket.