GameGrid
DayZ Steam64, Player ID and BattlEye GUID: Which ID Goes Where - visual guide

DayZ Steam64, Player ID and BattlEye GUID: Which ID Goes Where

DayZ uses three different player IDs, and its default name for everybody is "Survivor". Learn how to tell a Steam64 ID, a DayZ player ID and a BattlEye GUID apart, where the panel shows each, and which file or command needs which.

The Three IDs at a Glance

IDLooks likeWhere DayZ uses it
Steam64 ID17 digits, starting 7656119priority.txt
DayZ player ID44 characters of letters, digits, - and _, ending in =The id= in admin logs; the Whitelist (whitelist.txt) and Banned Players (ban.txt) lists
BattlEye GUID32 characters, digits and a to fRCon players output, addBan, battleye/bans.txt

All three belong to the same Steam account. The player ID and the GUID are both calculated from the Steam64 ID, so a Steam64 ID can be turned into either of the others. The other direction is not possible.

Pasting the wrong kind of ID is the number one reason a whitelist, ban or priority entry "does nothing". Check the length before saving, and test a new entry with one player before relying on it.

Why Everybody Is Called "Survivor"

On a fresh DayZ server almost every player is called Survivor, and several of them at once. That is not a fault in your server or in the panel: "Survivor" is the name DayZ itself gives a profile that has never been renamed, and the game reports that name to us exactly as it holds it. There is no better name on a dedicated server to read instead.

DayZ knows this too. Give it a second player under the same name and it calls them Survivor (2) on its own.

So GameGrid puts a short code beside the name everywhere a player appears โ€” the survivor table, the map labels, the killfeed, the leaderboard and a survivor profile:

Survivor ยท a1b2c3d4
  • The code is the same for one player across every one of those pages on that server, and the same for every member of your staff who looks, so you can talk about "a1b2c3d4" and mean one person.
  • It is specific to that server. The same player on your second server has a different code.
  • It is not a DayZ ID, a Steam64 ID or a BattlEye GUID, and it does not go into whitelist.txt, ban.txt, priority.txt or an RCon command. For those, use the real identifiers below.

Killfeed and event lines read plainly and add the codes only when two players in one line share a name โ€” which on DayZ is the case that actually needs them.

If the server mod has not resolved a player's identity yet, usually because they are still connecting, the panel shows the start of their DayZ ID in its place and says so, rather than showing a row with no name at all.

Copying an ID from the Panel

You rarely need to calculate an ID by hand. The panel hands you the exact string:

WhereWhat you get
DayZ Tools โ†’ Survivors, Actions on a playerDayZ ID and SteamID64, each with a Copy button
A survivor profile (click any name)DayZ ID, SteamID64 and BattlEye GUID, each with a Copy button

Each one says what it is for: the DayZ ID is what whitelist.txt and ban.txt take, the SteamID64 is what priority.txt takes, and the BattlEye GUID is what battleye/bans.txt takes. The GUID is computed from the SteamID64 rather than read from the game.

Only staff who can act see them

Identifiers are shown only to someone with the Manage permission on that server, because they are what a ban, a whitelist entry or a priority line is written with. A view-only member of your staff still sees the map, the board and a profile, and is told why the identifiers are not there.

The leaderboard, the killfeed and the events list carry no identifiers for anybody, whatever their permission โ€” the name and the short code only.

If a player is still connecting, the mod may not have an ID for them yet. Open them again a moment later.

Finding a Steam64 ID

  • From the player: in Steam, open their profile. If the address ends in a long number (/profiles/7656119...), that number is the Steam64 ID.
  • Custom profile address: paste the profile link into a lookup site such as steamid.io, which shows the steamID64.

The Steam64 ID is the most useful one to collect when a player applies to your community, because the other two can be calculated from it.

Finding a DayZ Player ID

DayZ writes each connection to the admin log (.ADM files in profiles/, opened from the Files tab) with the player ID. A connection line looks like this:

12:04:31 | Player "Survivor" is connected (id=Aa0bBc1CdD2eEf3FgG4hH5iIj6JkK7lLm8MnN9oOp0Q=)

Search the newest log for the player's name and copy everything between id= and the closing bracket.

You can also calculate it from a Steam64 ID: it is the SHA-256 hash of the Steam64 number, encoded as URL-safe Base64. Community tools for DayZ server owners do this conversion.

Names in logs are not unique and players can change them, so confirm with the player before whitelisting or banning by a name you found in a log. On DayZ this bites harder than on most games, because the default name is the same for everybody โ€” see Why Everybody Is Called "Survivor" above.

For a player who is online right now, the quickest route is the panel: open them on DayZ Tools โ†’ Survivors and copy the DayZ ID.

Finding a BattlEye GUID

  • Player online: run players in the Console tab. The GUID is the 32-character code on the player's line.
  • Player offline: convert their Steam64 ID. The GUID is an MD5 hash of "BE" plus the Steam64 ID, and BattlEye GUID converters are widely available.

Use the GUID for addBan when banning a player who is not online. See Banning Players and BattlEye Bans.

Which ID for Which Job

JobUse
Ban someone onlineTheir number from players, with ban
Ban someone offlineBattlEye GUID with addBan
Give priority queueSteam64 ID in Login Queue Priority (priority.txt)
Whitelist a playerDayZ player ID in Whitelist (whitelist.txt)
DayZ's own ban listDayZ player ID in Banned Players (ban.txt)
Look someone up in the admin logSearch for their player ID

Privacy

IDs are how you keep track of players, but treat them with care:

  • GameGrid masks player IP addresses in RCon replies shown in the Console, so you work with numbers and GUIDs, not addresses.
  • Keep lists of IDs with names and notes in private staff channels, not public ones.
  • Logs use hashed IDs rather than Steam64 IDs so that a leaked log does not point straight at a Steam profile. Only ask players for their Steam64 ID when you need it.