Public, anonymised ban list across all servers on the platform.
/bans is a public list of every ban issued through z-dev. Goal: community transparency + deterrence for repeat offenders.
| Field | Example |
|---|---|
| Identifier prefix | license:a3f9k2… (only leading characters) |
| Category | cheating |
| Public reason | "Aimbot detected" (optional — admin decides) |
| Created date | 2026-04-23 |
The full identifier, internal ban notes, IP addresses and hardware information are not part of the public list. Those fields are only visible to authorised admins of the owning project.
Five standard categories admins pick from when banning:
| Category | Meaning | Colour |
|---|---|---|
| cheating | Cheats, hacks, aimbots | Red |
| griefing | Intentional disruption of RP/events | Orange |
| racism | Discriminatory slurs | Purple |
| exploiting | Exploiting bugs | Yellow |
| other | Anything else | Grey |
A filter above the table restricts by category (/bans?category=cheating).
Every identifier is truncated on write so the public list only shows a short prefix. The full identifier never leaves the secured admin environment.
Anonymisation doesn't prevent a player from recognising themselves in the list. It prevents third parties from reconstructing the full identifier or linking a ban to real accounts — an important distinction for GDPR compliance.
Staff with the right permission manage bans in the panel under /admin/bans. Fill in:
/bans. Keep it factual and impersonal.Every ban creates an audit log entry (BAN_CREATE, BAN_REVOKE). Audit entries cannot be deleted.
The public ban list is deliberately not linked from the marketing header — it's not meant as a marketing tool. Visitors find it via search (⌘K → "bans") or direct link. Per tenant the list can be enabled in your own public menu.