Bans list
Search and filter bans, read the detail panel and its evidence, ban an offline player, unban, and what Wipe All actually does.
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 six fields at once, so pasting whatever fragment a player gave you in a ticket is usually enough.
| Search matches | Example |
|---|---|
| Player name | The name the resource reported when the ban was filed |
| Ban id | ban-1759536000000-k3f9d2a |
| Ban reason | Any fragment of it, typed or from a detection |
| Identifiers | license:110000100000001 |
| Hardware ids | Any of the machine fingerprints on the row |
| FiveM tokens | The per-client tokens the ban also carries |
Filter and sort
| Group | Choices | Offered |
|---|---|---|
| Kind | Manual, Detection | Whenever the list holds a ban |
| Issued by | Dashboard, Server console, In-game admin, Resource | Only when the list holds bans from more than one of them, and only the ones it holds |
| Age | Last 24 hours, Last 7 days, Last 30 days, Older than 30 days | Whenever the list holds a ban |
A choice stays in force while it is ticked even when no ban matches it any more: unban the last ban the server console filed while Issued by is set to Server console, and the list goes empty with a notice naming that filter and a Clear filters button, rather than quietly showing everything again.
Sorting offers Date or Name with an ascending or descending toggle, and opens on Date descending, 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 carry no expiry at all, so Permanent is a statement of fact rather than a setting you missed.
The detail panel
Clicking a card opens the full record.
| Field | What it holds |
|---|---|
| Manual tag | Present when an admin issued the ban by hand. No tag means a detection issued it. |
| Ban id, reason, issuer | Plus when it was filed and when the row was last updated. An in-game admin who filed the ban is a link: to their entry on the In-Game Moderators page while they are still on it, and to Lookup once they are not. |
| Proof | When the ban carries a capture. A screenshot renders inline and opens full size in a new tab, and a recording plays in place. A capture already reaped to save storage says so instead of showing a broken frame. |
| Identifiers and HWIDs | Each with a copy button. The IP stays on the server and is never sent to the browser. |
| Detection context | The structured evidence the resource sent with an automatic ban, starting with the config option and the type. This is what tells you whether a detection fired on something your own scripts do. |
When a capture came back empty there is nothing to reap: no file is stored and the ban carries the black screen card as its capture, so the panel shows that card and says the capture came back empty rather than leaving a dead capture to be read as a ban that never had one.
Banning an offline player
Ban Offline covers the case where someone left before you could act. It needs the ban create permission.
Pick the player
The left pane lists everyone who has played on this server, with a count of how many are in history and how many the search left. Search by name, player id, identifier or hardware id, and flip the order between A to Z and Z to A.
Check the identifiers
The panel shows the identifiers and hardware ids that will go on the ban. This is worth reading before you confirm.
Write a reason
A reason is required. Cheating, Hacking, Exploiting, Toxicity, Ban Evading and Griefing are offered as buttons, and you can type anything else instead.
If this server already has an active ban carrying any of those identifiers the request is refused with Already banned, so you never end up with two live rows for one person. A ban you lifted earlier does not block it: re-banning somebody you previously unbanned works from this page, which is the whole reason the check looks at active rows rather than every row.
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. It also undoes everything the ban caused elsewhere.
| Action | Unban one ban | Wipe All |
|---|---|---|
| Rows deleted | None, the row is kept | None, every row is kept |
| Trust penalty refunded | Yes, the exact amount deducted | No |
| Automatic global ban revoked | Yes | No |
| Open Raven Mind card resolved | Yes | Yes |
| Permission | Bans List Remove | Bans List Remove |
| Undo | Restore ban, from the activity log row | None, per ban |
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. Either way the rule applies only to this server, and promoting it to the network is a separate step.
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.
Ban ids are written as ban-<timestamp>-<random>, which is the id a player reads off the rejection screen when they open a ticket.