Ban federation model

Bans in heliana come from a few places, and it helps to know which does what. There are bans you issue yourself, bans you import from an outside source, an automatic signal about bans in other communities, and exceptions that let a specific player through. This page is the map.

Bans you issue

A ban you hand out is a record of its own: a reason, a duration (a fixed length or permanent), a scope (all your servers or one), who issued it, and when. You create one by running the Ban player trigger against a player — the trigger carries the duration and scope, and you type the reason at run time. These bans show up in the player’s Lists tab under Bans, and you can lift them there. See Ban a player.

Imported ban lists

A ban list can pull its entries from an outside source instead of being filled by hand. You attach a connector — BattleMetrics, the Community Ban List, or a Remote Ban File — to a Ban list on the Roster page, then sync it in. The imported entries are read-only copies; heliana matches connecting players against them but never writes back to the source. See Sync an external ban source.

Cross-community visibility

heliana also matches a player against ban lists kept by every other heliana community. A match is automatic and read-only — an advisory signal, not enforcement. There’s no opt-in, no sharing step, and no consent: every community’s bans are visible to every other. The match runs across all of a player’s identities (Steam, EOS, BattlEye, Mojang), so it follows the person rather than one ID. See Cross-community ban visibility.

Exceptions

Sometimes a player matches a synced ban list but you want to allow them anyway — a false positive, an old entry from a different community, someone you’ve cleared. An exception lets that player past matching ban-list entries, either across your whole organization or on one server. It doesn’t delete anything from the source; it’s a local override. See Manage exceptions.

Putting it together

For a player trying to join one of your servers, the picture is:

• Do you have your own active ban on them? That’s your call, made directly.
• Do any of your synced ban lists match them — unless an exception clears them?
• Separately, are they banned in other heliana communities? That’s shown to you as context, but it’s yours to act on or ignore.

Each of these is independent. Your own bans and your synced lists decide who’s blocked on your servers; cross-community visibility is background information; exceptions are your local override on the imported side.