Arma Reforger is configured with a single JSON file. Everything below sits inside the game block of that file.
1. Open the config
- Stop the server in the Game Panel.
- Open the Files tab and open the server config file. It has a
.jsonextension and contains blocks namedgameandoperating.
Leave the address and port fields alone. They are set to match the ports allocated to your service, and changing them takes the server off the network.
2. The settings you will change
| Key | What it does |
|---|---|
name | The name in the server browser. |
password | Password to join. Empty means open. |
passwordAdmin | Password used with the login command in game. |
admins | A list of identity IDs that get admin without the password. |
maxPlayers | Player slots, up to 64. |
visible | Whether the server is listed in the browser. |
scenarioId | The scenario the server loads. |
crossPlatform | Allows console players to join. |
Keys are case sensitive. passwordadmin is not the same as passwordAdmin and is silently ignored.
3. Choosing a scenario
A scenario ID is a GUID in braces followed by a path that ends in .conf, for example:
"scenarioId": "{ECC61978EDCC2B5A}Missions/23_Campaign.conf"
- The braces and the GUID are part of the value. Removing them breaks it.
- A scenario that comes from a mod only works if that mod is also listed in the
modsarray. - A wrong scenario ID gives you a server that starts and then sits there with nothing loaded.
4. Save and restart
- Save the file. If the panel editor reports invalid JSON, fix it before starting. A missing comma between entries is the usual cause.
- Start the server and watch the console for the scenario name.
5. Gameplay settings
View distance, BattlEye, the third person setting and the rest live in the gameProperties block inside game. They follow the same rules: exact spelling, valid JSON, restart to apply.
If a change does not take effect, confirm the server was stopped when you saved and that the file is still valid JSON.





