Arma 3 keeps its server settings in server.cfg in the root of your server files. It is plain text and every line ends with a semicolon.
1. Open the file
- Stop the server in the Game Panel.
- Open the Files tab and click
server.cfg.
2. The settings you will change
| Setting | What it does |
|---|---|
hostname | The name in the server browser. |
password | Password to join. Remove the value for an open server. |
passwordAdmin | Password for the admin login. Never the same as the join password. |
maxPlayers | Player slots. |
motd[] | Lines of text shown to players as they join. |
admins[] | Steam64 IDs allowed to log in as admin without the password. |
verifySignatures | 2 enforces signed mods. Leave it at 2 on a public server. |
persistent | 1 keeps the mission running when the last player leaves. |
kickDuplicate | 1 stops two clients with the same ID connecting. |
Text values are in quotation marks, numbers are not:
hostname = "Night Ops";
maxPlayers = 40;
password = "joinme";
3. Starting a mission automatically
The class Missions block at the end of the file tells the server what to load instead of sitting in the mission select lobby:
class Missions
{
class Mission1
{
template = "MyMission.Altis";
difficulty = "Regular";
};
};
The template name is the mission file name in mpmissions without the .pbo extension. Upload mission files to mpmissions in the Files tab.
4. Save and restart
- Save the file.
- Start the server and check the console for the hostname.
5. If the server will not start after an edit
- A missing semicolon at the end of a line stops the whole file being read.
- Unmatched braces in the
class Missionsblock do the same. - Read the first lines of the console after a start. The parser reports the line it failed on.
Keep a copy of a working server.cfg before a large edit so you can put it back.





