Identity reference
How provider-scoped IDs connect observations to Users without relying on display names.
The identifiers
| Identifier | Used for | How it is obtained |
|---|---|---|
| Discord User ID | Your signed-in Heir User and Discord interactions | Discord authentication. |
| Mordhau PlayFab ID | Mordhau player observations | The account ID reported by the game; linked through the game-identity flow. |
| SteamID64 | Chivalry: Medieval Warfare identity | Verified Steam sign-in. |
| Team/Roster IDs and handles | Finding the intended Heir entity | Heir links, selectors, and copied IDs. |
These identifiers are not interchangeable. Do not paste a Steam ID into a PlayFab field or infer ownership from the same player name.
Provider scope and names
Identity keys are provider/credential scoped. Game-specific names and sightings can change over time without changing the canonical identity. A rename or clan tag is not a new account, and two identical names are not proof of one person.
PlayFab identifiers belong to the relevant game/title context. Platform Steam identities can be reused where the same Steam account is the required credential.
Previously observed data
Heir can observe an unlinked game identity and associate matching records after the User links it. It does not invent missing matches, merge unrelated IDs by name, or turn old match participation into complete connected-time history.
Organizer tools
/admin identity search name:<name>searches the League's observed names./admin identity unlink user:<user> game:<credential>resolves an incorrect League identity association using its supported options./admin identity panelprovides the supported linking-panel flow.
Read the full identity command reference before changing associations. A mistaken unlink affects identity/eligibility; it is not a way to edit historical combat numbers.
For the player walkthrough, use Link your game identity.