Identity platforms
A player can be identified by more than one game account system at once — for example both a Steam ID and an EOS ID. Platform names which of those systems a given ID belongs to. You’ll see it in two places:
- On a player’s linked identities
- On an entry imported from an external ban source
Values
Section titled “Values”| Value | Full name | Description |
|---|---|---|
steam |
Steam | Steam 64-bit ID (SteamID64). |
eos |
Epic Online Services | EOS ID — the identifier that defines a Squad player. |
battleye-guid |
BattlEye | BattlEye GUID. Seen on some external ban sources. |
mojang |
Mojang / Microsoft | Microsoft/Mojang account identifier, for games that use it. |
Matching
Section titled “Matching”Matching is platform-blind: a BattlEye GUID or a Mojang ID matches exactly the way a Steam or EOS ID does. It is not, however, live.
Both ban enforcement and cross-community visibility work off a ban’s coverage — the identity it was issued against, plus the identities the servers of the issuing organization had already linked to that player at that moment. Coverage is written once, when the ban is issued, and is never recalculated afterwards. A match is the overlap between the identities a player presents now and that stored set: one identity in common is a match, whatever platform it sits on. An imported ban is filled differently but frozen the same way: its coverage is exactly the set of identities carried by the source’s own entry, with nothing added from heliana’s observations.
An identity linked to the player after the ban was issued is therefore not covered by it. That is deliberate: if coverage tracked a player’s live identities, a single observation would extend an already-issued punishment to a new account of that person without anyone deciding it.
See How bans are structured for how a ban itself is structured.