Ban schema
This page describes what a ban is made of and how it behaves, regardless of where it came from. For the mechanics of issuing one, see Ban a player; for connecting an external source, see Sync an external ban source; for the automatic cross-community signal, see Cross-community ban visibility.
Fields of a ban
Section titled “Fields of a ban”| Field | Description |
|---|---|
| Reason | Free-text explanation, shown wherever the ban appears |
| Duration | Permanent, or an expiry date/time. An expired ban stops enforcing on its own — you don’t need to revoke it. |
| Scope | One server, or every server in your organization |
| Category | A classification label — one of Cheating, Teamkilling, Toxicity, Ban evasion, Griefing, or Other |
| Status | Active, Expired, or Revoked |
A ban targets a player, not a single identity — it’s enforced against every identity (Steam, EOS, BattlEye, Mojang) linked to that player, not just whichever one triggered it.
Manual vs. imported
Section titled “Manual vs. imported”A ban gets into heliana one of two ways:
- Manual — an admin issues it directly (through the Ban player trigger), or a trigger issues it automatically in response to an event or a schedule.
- Imported — it comes in from a connected external ban source (BattleMetrics, Community Ban List, or a Remote Ban File) synced into a ban roster group, on a schedule or via “Sync now.”
Either way, the ban shows up in the same place: the Lists tab on the player’s profile.
Author. A ban you issue yourself is recorded under your name. A ban created by an automated trigger, or pulled in from an external source, is recorded as a system entry with no operator attached.
Revoking
Section titled “Revoking”Revoking a ban lifts enforcement immediately and marks it Revoked. A revoked ban drops out of cross-community visibility entirely — only active and expired bans are shown there.
Cross-community ban visibility
Section titled “Cross-community ban visibility”A player’s profile automatically surfaces matching active or expired bans from other heliana communities — this is read-only and automatic. There’s no sharing step, no consent request, and no opt-in: any community using heliana can see any other community’s active or expired bans on a matching player, as an advisory signal. Revoked bans are never shown this way. It’s informational only — it never bans a player on your servers by itself.
Exceptions
Section titled “Exceptions”An exception excludes one player from ban enforcement without touching the ban record itself — useful when you want to let someone play despite a matching ban (yours or an imported one). Set on the player’s Lists tab, an exception applies either:
- Org-wide — across every server in your organization, or
- On one server — the player is let through on that server only; the ban still enforces everywhere else
Every exception needs a reason, so there’s a record of why the player was let through.