Controlled publishing
A new record starts as a draft and appears in the public listing only after publication.
CZ/SK SCUM community
A banlist built for order, not noise
The public banlist gives players and admins a clear overview of published sanctions across the SCUM.SK environment.
Records are separated from sensitive identifiers, move through a workflow and publish only data intended for public view. Details and internal data stay available only to authorized people.
Why it exists
Not a blacklist for show. An operational tool for fair moderation.
The banlist helps verify sanction context quickly without exposing private player identifiers publicly.
Each record has a public part, an internal part and an audit workflow. That keeps community-facing information separate from sensitive admin work.
A record is more than a table row
A ban moves through draft, review, publication and possible correction or appeal. Admins see more; the public sees only the approved output.
Permission-based access
Only an account with the ADMIN_BANLIST role can add bans.
Visible record origin
The account that created the record is stored; anonymous visitors see only a placeholder.
Data protection
Public data should be public. Private data should not leave the backend.
SteamIDs, internal notes and non-public evidence are not sent to regular visitors.
The system uses separated read models. When a visitor does not have access, the backend does not return real sensitive data and the frontend renders only a replacement state.
Dashboard
Open the public banlist
Go to the filtered dashboard of published records. Search works across nickname, SteamID, Discord nickname, server and sanction type.