An Arma Reforger player ID is the Bohemia Interactive identity string that every player is assigned through their Bohemia Account, and it is the one value that admin and ban lists actually read. Players can see their own ID in the in-game profile menu, and admins can read other players' IDs from the live server console, the chat command output, or the log files. This guide walks through every way to find one quickly so you can paste it into config.json with confidence.
What an Arma Reforger Player ID Actually Is
Arma Reforger uses a Bohemia Interactive identity ID, sometimes called the Reforger Identity or colloquially the SID, to identify every player. It is tied to the player's Bohemia Account, not to Steam or Xbox directly, which is why the same player has the same ID on PC and console. It is a hexadecimal string, and it is what the server stores in admin and ban lists.
- The Bohemia identity ID is what every server-side admin or ban check uses
- It is not a Steam ID or an Xbox gamertag; do not paste either of those into config.json
- The same player keeps the same identity ID across servers
- Older Arma admins sometimes call this value the SID; in Reforger it is the Bohemia identity ID under the hood
How a Player Finds Their Own ID In-Game
Most of the time you are not the one looking up the ID. You ask each new admin or banned player to read theirs from the main menu. This is the fastest path because it does not need a connected server.
- Launch Arma Reforger
- From the main menu, open the Profile section
- Locate the Bohemia Account identity field on the profile page
- Copy the full string exactly, with no spaces
- Send it to the admin who will paste it into config.json
- Ask players to send the ID in a copy-paste-friendly channel like Discord, not a screenshot
- IDs are case sensitive; preserve capitalisation exactly
Pulling a Player's ID from the Server Console
If a player is already on the server, you do not need to ask. As an admin you can list every connected player and their identity ID straight from the chat console. This is the cleanest way to grab the ID of someone you just had to kick or are about to ban.
- Open the in-game chat with the chat key
- Run #login with your admin password
- Run #players to print the connected list
- Copy the identity ID from the row of the player you care about
#login changeme#players- Run #players right before a ban so you know you are catching the right person
- If you cannot remember the slot number for #kick, the same list shows it next to the ID
Reading IDs from the LPV5 Live Console
On Loafhosts the LPV5 panel inside LoafHub at hub.loafhosts.com gives you a live console with full server output, so you can pull player IDs without joining the game. This is useful when the server is full or when you are admin-ing from a phone.
- Open hub.loafhosts.com and select your Arma Reforger server
- Open the Console tab to see live output
- Use the command box to run #players, or watch the join log for new player IDs
- Copy the ID directly from the console line
- The LPV5 console captures every line, so you can search back through history for an old player's ID
- Scheduled restarts keep the console output clean and easy to scan
Finding IDs in the Server Log Files
Every join and disconnect is written to the server logs along with the player's identity ID, so even after a restart you can recover an ID you forgot to copy. Reforger writes logs into the profile folder under a timestamped subfolder each session.
- Open the LPV5 file manager
- Navigate to the profile folder, then into logs
- Open the most recent timestamped session folder
- Open console.log and search for the player's name to find the line with their identity ID
- Use the file manager search to jump straight to a player name across logs
- Log session folders are created on each restart, so older incidents are in older folders
- console.log is the right log for join, leave, kick, and ban events
What You Use a Player ID For
Once you have a verified identity ID, you paste it into the relevant array in config.json. The admins array under the game block grants admin rights to that player, and the playerBanList entry blocks them from rejoining. Both fields live in the same config.json file.
"admins": ["abcdef1234567890"]"playerBanList": [ { "identityId": "abcdef1234567890", "name": "Griefer", "reason": "Team killing" } ]- Triple-check the ID before adding it to admins; you are granting kick and ban power to whoever owns that account