Arma Reforger Server Config Example
Use this example as a readable starting point for an Arma Reforger dedicated server config.json, then adjust names, ports, scenario, passwords, admins, and mods for your own host.
Example config.json
This example is intentionally conservative. Replace the scenario, passwords, admin IDs, and Workshop mod IDs before using it on a public server. The official field reference is the Bohemia Interactive server config documentation.
{
"bindAddress": "0.0.0.0",
"bindPort": 2001,
"publicAddress": "",
"publicPort": 2001,
"a2s": {
"address": "0.0.0.0",
"port": 17777
},
"game": {
"name": "My Arma Reforger Server",
"password": "",
"passwordAdmin": "replace-this-admin-password",
"admins": [],
"scenarioId": "{ECC61978EDCC2B5A}Missions/23_Campaign.conf",
"maxPlayers": 32,
"visible": true,
"crossPlatform": true,
"modsRequiredByDefault": true,
"mods": [
{
"modId": "5965550F24A0C152",
"name": "Example Workshop Mod"
}
],
"gameProperties": {
"serverMaxViewDistance": 2500,
"networkViewDistance": 1000,
"serverMinGrassDistance": 50,
"fastValidation": true,
"battlEye": true
}
}
}
What to change first
- Set
game.nameto the server name players should see. - Replace
passwordAdminwith a real secret and keep it out of shared files. - Choose the correct
scenarioIdfor the mission you want to run. - Update ports if your host panel or firewall uses different values.
Where mods go
Workshop mods belong inside game.mods. Each entry needs a modId. A name helps humans read the file, and a version can pin a specific release when you need that behavior.
Validate before restart
Copy the edited file into the Arma Reforger Config.json Validator before deploying. It catches JSON syntax problems, duplicate mod IDs, malformed mod entries, and common field type issues that are easy to miss by eye.