Adding Admin Access and Using Commands on Your Arma 3 Server
Before skipping down to the command list below, follow these steps to give your players access to run commands on your Arma 3 missions!
Adding Admin Access
Create a server.cfg
The server.cfg, one of Arma 3’s main configuration files, is needed to add admin access. We recommend checking out our article Creating a "server.cfg" file for your Arma 3 Server for more information on creating the file.
Add an Admin Password
On an empty line in your server.cfg add the following passwordAdmin setting. Remember to edit the password to something secure and safe.
passwordAdmin = "xyzxyz";
Making Permanent Admins
Permanent admins have the benefit of not needing to enter the password each time they login as an admin. However the players Steam ID must be added in order to do so. To locate your Steam ID, we recommend reading How to quickly find Steam ID numbers to acquire you and your admin's SteamID64 number. After doing so add the following to your server.cfg on its own line. Each additional SteamID64 will need to be separated by a comma.
admins[] = {"76561198157725231", "76561199011986503"};
Using Commands
Once you have connected to your server you can login as an admin by opening your Chat console. By default this is set to the / key. Type and enter #login if you have added yourself as a Permanent Admin, or #login xyzxyz with the password set earlier. You can now use admin commands on your server!
List of Commands
Each command begins with a #.
| Command | Example | Description |
|---|---|---|
| #login | #login password | Log in as the admin. Without password only possible if you are listed as an admin[] in server.cfg |
| #logout | Admin log out. | |
| #mission filename difficulty | #mission myDM.intro Veteran | Select mission with known name and set the difficulty. Difficulty parameter is optional and if not set, current difficulty is kept. |
| #missions | Ends the current mission to open the mission selection menu. | |
| #restart | Restart mission. | |
| #reassign | Start over and reassign roles. | |
| #shutdown | Shuts down the server immediately. | |
| #restartserver | Shuts down and restarts the server immediately. | |
| #shutdownaftermission | Shuts down the server after mission ends. | |
| #restartserveraftermission | Shuts down and restarts the server after mission ends | |
| #init | Reload server config file loaded by -config option. | |
| #exec ban <name/ID/Player#> | Allows you to ban a player. Their ID will be added to the ban.txt | |
| #kick <name/ID/Player#> | Allows you to kick a player. | |
| #monitor (interval in sec) | #monitor 1 | Shows performance information of the server. Interval 0 means to stop monitoring. |
| #monitords (interval in sec) | #monitords 1 | Shows performance information in the dedicated server console. Interval 0 means to stop monitoring. |
| #debug off | #debug off | Disables debugging. |
| #debug (interval in sec) | #debug 30 | Default interval is 10 seconds. |
| #debug (command) (param) | The available commands are checkFile, userSent, userInfo, userQueue, totalSent, and JIPQueue. Each command can be disabled by the use of the off parameter. Each command differs a bit; some output to screen, some to log file etc. | |
| #lock | Locks the server, prevents new clients from joining. | |
| #unlock | Unlocks the server, allows new clients to join. | |
| #exec <server side command> | Execute administration scripting command. |
