Arma Reforger Admin Commands: What Each Role Can Run

Arma Reforger admin commands depend on who is issuing them. The official command list separates logged-in admins, voted admins, regular players, native RCON admins and RCON monitors; a command available in one context may be rejected in another. This guide uses Bohemia’s Reforger server management reference, not command lists for Arma 3.

The short version: use #players to identify people in the current session, #kick for a temporary removal, and #ban only on a dedicated server. #restart restarts the active scenario while keeping clients connected; #shutdown closes the server and disconnects them. Read the permission table before pasting a command into chat or an RCON client.

Which Arma Reforger admin commands can each role run?#

These are the roles in Bohemia’s documented permission matrix. “Logged admin” means an in-game admin authenticated with the admin password; RCON roles come from the server’s native RCON configuration. A monitor can inspect supported information but cannot issue the state-changing server commands in this table.

The table summarizes the official matrix; server configuration, game version and whether you are using chat or native RCON still matter. Bohemia’s server configuration reference documents the JSON settings and the admin identity fields. Native Reforger RCON is configured separately from BattlEye RCon, so check which service your client connects to before choosing syntax.

How do you open chat and log in as an admin?#

On PC, Bohemia documents C in the lobby and Return in-game to open chat. Type #login followed by the admin password if your account is not already recognized through the server configuration. The published reference does not give an Xbox or PlayStation button sequence, so use the current in-game control mapping on those platforms instead of relying on a shortcut copied from a video.

#login your-admin-password

Only send the password to the game server’s chat input when you intend to authenticate. Do not paste it into public chat, screenshots, a support post or an RCON client you have not verified. If the server lists your identity as an admin or you own the server, the documented flow may allow login without the password argument.

The exact role matters after login. #roles tells you the in-game role available to the session, and the matrix above shows which operations require a logged admin specifically. A normal player can see #players, for example, but that does not grant permission to kick someone.

If you run your community through a managed panel, Game Hosting’s current Arma Reforger plans include a server console with Reforger command suggestions and an admin list in the server settings. The panel also exposes current player and moderation controls. Those controls are a convenience for server owners; the game’s own permission rules and command behavior still apply.

Can Xbox and PlayStation admins use the same commands?#

Bohemia’s published permission matrix describes in-game roles and RCON roles; it does not give a different command list for Xbox or PlayStation. That means the documented command syntax is the useful reference once a command reaches the game’s chat input. The documentation names PC chat controls only, though, so it does not establish which controller buttons open that input on Xbox or PS5. Check the current control mapping in the client instead of trying an unverified button combination during a live session.

Native RCON is a separate option for a server operator, not a console shortcut. It can issue the commands allowed by its configured role without opening in-game chat. A console player’s ability to join a cross-platform server also does not make that player an admin automatically; the server still needs the appropriate identity and permissions. If a console player cannot run a command, first confirm their role and the input method before changing server configuration.

How do you check player IDs without confusing them with IdentityIds?#

Run #players to see the players currently connected and their session playerId values. The playerId is local to that session; it is useful for a command such as #kick <playerId>, but it is not the persistent Bohemia IdentityId used to recognize an account across sessions.

The #id command prints your own local player ID. It does not look up another player’s persistent identity. This distinction matters because a session ID can change after someone disconnects and rejoins, while a ban or server admin list may need a persistent identity. Do not save a number from #players as if it were a permanent account ID.

Which commands remove a player or end a session?#

Use #kick when you need to remove a connected player but leave open the possibility that they return. Its documented form takes the target’s online session ID:

#kick <playerId>

For bans, Bohemia documents #ban on dedicated servers. It can use an online playerId, a persistent identityId, or a player name where supported by the current game version. The official reference says a playerId target must be online; an identityId can identify an offline player. Ban duration is in seconds, and 0 means permanent. Because bans affect future access, verify the target identity and reason before applying one.

#ban create <playerId-or-identityId-or-playerName> <durationInSeconds> <reason>
#ban list <page>
#ban remove <identityId>

The optional reason is useful for keeping a moderation record, but it does not change the target identifier or duration rules. #ban list shows a page of ban entries with a BanID, player UID and duration; the in-game list returns 10 entries per page and RCON returns 25. If you omit the page number, the first page is shown. A listed BanID is not the same argument as the persistent identity required by #ban remove, so read the command’s expected parameter before copying a value from a list.

The official docs mark player-name support as available from version 1.2.0. When you are unsure which identifier the server accepted, use the matching account identity rather than guessing from a display name. This guide keeps the full moderation workflow out of scope; confirm exact syntax in Bohemia’s server management reference and avoid running a permanent ban as a syntax test.

Keep moderation actions separate from server lifecycle commands. #restart restarts the scenario currently running and keeps clients connected. #shutdown turns off the server and disconnects players. If you intend to change a scenario or restore a world, first confirm a recoverable backup and the restore path with whoever operates the server; a restart command is not a backup or recovery step.

What is the difference between chat commands and native RCON?#

In-game commands use the # command syntax and the in-game permission roles. Native Reforger RCON uses the server’s rcon configuration block and gives a connection either admin or monitor permission. A monitor is read-only for the documented command set. RCON has its own @logout command, which closes the authenticated RCON session; it is not an in-game chat command.

@logout

The server’s #login password flow is not a substitute for configuring native RCON credentials, and BattlEye RCon is a separate service. Check the official server configuration guide and server management guide for the exact option names and access model. Do not assume an Arma 3 RCon client or command list speaks the same protocol.

Which familiar commands are missing from Bohemia’s Reforger list?#

Bohemia’s published Reforger server command list does not include say, #lock, #unlock, #mission or #reassign. Those often appear in Arma 3 command references, which is why a search for Reforger admin help can lead to instructions for the wrong game. This does not rule out separate mod or third-party tooling; verify those commands against the documentation for the exact tool installed on your server.

Also avoid treating a recent compatibility fix as a universal guarantee. The 1.8.0.13 release notes say Bohemia fixed a crash involving vanilla scripted commands on modded servers through RCON. That note confirms one fix; it does not promise every mod, command and RCON client combination will work.

What should you check when a command fails?#

First identify where you entered it: game chat, native Reforger RCON or BattlEye RCon. Then check the spelling, the command’s required role, whether the target is online, and whether the operation is restricted to a dedicated server. For an RCON monitor, retrying a state-changing command will not grant admin permission; the server owner must configure the right role.

If you are still choosing a managed server after sorting out the admin workflow, our Arma Reforger hosting guide compares the questions to ask about panel controls, platform support and recovery. For a server you already run, keep Bohemia’s command and configuration references nearby and test changes with the other admins before using them during a live session.

When a command fails, save the exact error and identify the context before changing anything. A role error points to permissions; an unknown-command response may mean an Arma 3 command or a missing mod; a missing target may mean the player is offline or the wrong identifier was used. For a lifecycle action, ask whether you intended to restart the scenario or stop the server. That small check prevents an admin from solving the wrong problem while everyone is connected.