To add an admin to an Arma Reforger server, paste their Bohemia identity ID into the admins array inside the game block of config.json, then restart the server so it picks up the change. From that point the player can run #login and use admin commands like #kick and #ban directly from in-game chat. This guide covers both the LPV5 panel method and the manual config edit, plus the security practices that keep your admin team from becoming an attack surface.
Two Ways to Become an Admin in Reforger
Arma Reforger has two admin paths and you usually want both. The first is the admins array in config.json, which is a static list of trusted identity IDs that always have admin rights. The second is the admin password, set in passwordAdmin, which any player can use with #login to gain admin rights for that session. The admin password is a fallback; the admins array is the production setup.
Tip: Use the admins array for your real staff
Tip: Keep the admin password as a one-time fallback in case a staff member’s ID is wrong
Tip: Listed admins still typically run #login to flag themselves as active admins in chat
Note: Both methods are controlled by the same config.json file; there is no separate admin file
Collecting Your Admins’ Identity IDs
Before you edit anything, gather every admin’s identity ID. Each entry may be either a Bohemia (BI Account) identity ID or a 17-digit SteamID64 (for example “76561198xxxxxxxxx”). Each admin can read their Bohemia identity ID from the main menu Profile screen in Arma Reforger. Get them all in one pass so you only have to edit config.json once.
- Ask each admin to launch Arma Reforger and open Profile from the main menu
- Have them copy the Bohemia identity ID and send it back to you
- Drop every ID in a Discord channel or shared note in copy-paste form
- Double-check none of them contain stray spaces or quotation marks
Warning: Never accept screenshots; typos on long IDs are very easy to miss when transcribing
Adding Admins on the LPV5 Panel
On LoafHosts the LPV5 Config Editor inside LoafHub covers core settings (server name, passwords, scenario, max players, network tuning) but does NOT edit the admins array. Mods and admins are managed on their own pages and are not overwritten by the Config Editor. To add admins, use the LPV5 file manager to edit config.json directly (next section).
The Config Editor is still useful here for one related field: game.passwordAdmin is editable as the Admin Password field, so you can set or rotate the admin-password fallback without touching raw JSON.
- Open hub.loafhosts.com and select your Arma Reforger server
- Open the Config Editor to set or rotate the Admin Password (passwordAdmin)
- Save the config
- Restart the server so the change takes effect
- To edit the admins array itself, use the file manager (see the next section)
Tip: The Config Editor applies server-side validation that rejects out-of-range values, but it does not manage the admins array; add admins through the file manager instead
Adding Admins by Editing config.json Directly
If you prefer raw JSON, the LPV5 file manager lets you open config.json in place. The field you want is the admins array under the game block.
| Command | Description | Example |
|---|---|---|
game.admins | Array of Bohemia identity IDs granted admin rights on boot | "admins": ["abcdef1234567890", "0011223344556677"] |
game.passwordAdmin | Admin password used with the in-game #login command | "passwordAdmin": "long-random-secret" |
- Open the LPV5 file manager and locate config.json
- Open it for editing
- Find the game block and the admins array
- Add each identity ID as a quoted string, separated by commas
- Make sure there is no trailing comma after the last entry
- Save the file and restart the server
Warning: config.json must be valid JSON; a single missing comma or quote stops the server from starting
Using Admin Commands In-Game
Once a player is in the admins array, they can authenticate from in-game chat and use the admin commands. The chat console is opened with the chat key and admin commands are prefixed with #.
| Command | Description | Example |
|---|---|---|
#login <adminPassword> | Authenticate as admin in chat using the passwordAdmin value | #login changeme |
#logout | End the current admin session | |
#players | List connected players with their in-session player IDs, UIDs, and names | |
#kick <playerId> [reason] | Kick a player off the server | #kick 5 AFK in main |
#ban create <playerId> <seconds> [reason] | Ban a player by in-session player ID; 0 seconds is permanent | #ban create 5 3600 spam (1-hour ban) |
#ban remove <identityId> | Lift a ban by the player’s identity ID; there is no #unban verb | #ban remove 0x0123456789abcdef |
Tip: Run #players first so you know the exact in-session player ID before kicking or banning
Tip: If a command does not respond, run #login again; admin status only lasts for the current connection
Removing an Admin
Removing an admin is the same flow in reverse. Delete their entry from the admins array, save config.json, and restart. There is no in-game command that revokes an admin who is listed in the array; the source of truth is the config file.
- Open the Config Editor or the file manager
- Find the admins array under the game block
- Delete the identity ID line for the admin you are removing
- Save and restart the server
- Rotate passwordAdmin if the removed admin knew it
Warning: If the removed admin knew the admin password, change passwordAdmin immediately or they can still #login
Admin Security Best Practices
Admin rights mean the power to kick, ban, and disrupt a session, so treat the admin list like a key list. A few habits keep the system safe.
Tip: Use a long, random passwordAdmin and only share it with people you have vetted
Tip: Rotate passwordAdmin any time a staff member leaves
Tip: Keep the admins array small and review it monthly
Tip: Use LoafHub sub-users to give staff panel access instead of sharing your account
Tip: Log major admin actions in a Discord channel so your team has a paper trail
Warning: Do not paste your admin password in screenshots, public chats, or unredacted log uploads
Frequently Asked Questions
What field do I put admins in for Arma Reforger?
Add their Bohemia identity IDs to the admins array inside the game block of config.json. Each ID is a quoted string and the array can hold as many as you need. Restart the server after editing to load the new list.
Do admins need to use the admin password if they are in the admins array?
Players in the admins array have admin rights automatically, but they typically still run #login from chat to flag themselves as an active admin and unlock admin commands for that session. The admin password is the fallback path for users not in the array.
What is the in-game command to log in as admin?
Open chat and type #login followed by your admin password, for example #login mySecret. If your identity ID is in the admins array or your password matches passwordAdmin, you gain admin status for that session.
How do I remove an admin from my Reforger server?
Delete their identity ID from the admins array in config.json, save the file, and restart the server. If they also knew the admin password, change passwordAdmin right away so they cannot reauthenticate that way.
Can I add admins from inside the game?
No. The admins array is read from config.json on server boot, so adding or removing admins always means editing the config and restarting. You can grant ad-hoc admin to any logged-in player using the admin password, but for persistent admin status, edit the array.
How many admins can an Arma Reforger server have?
There is no practical limit set by the engine; the admins array accepts as many identity IDs as you list. For security, most groups keep the list small and add only the people who actively need admin powers.