Arma Reforger server_config.json Explained: Every Setting
An Arma Reforger dedicated server is configured by one JSON file, commonly called config.json or server_config.json, that the server is pointed at with -config. On ChicagoServers the panel does that for you: you change the common settings on the Startup tab and edit the rest in Server config on the Configs tab. The game defaults that matter most: game port 2001 (UDP), Steam query port 17777, 64 player slots, BattlEye on, and the server visible in the browser.
This guide walks through every key in the official Bohemia Interactive Community Wiki "Server Config" page, including the renames that break older tutorials. The wiki's newest version marker on that page is 1.2.0, while the game itself has since reached 1.8 (August 2026). Everything here was checked against the wiki on 2026-11-01, so confirm against the wiki and the patch notes after a major update.
- On ChicagoServers, open your server in the panel: the basics are on the Startup tab, the full file is Server config on the Configs tab. The panel installs and starts the server; update it with Update now on the Steam update bar (app ID 1874900 stable, 1890870 experimental; switch with Branch).
- Game defaults:
bindPort2001 (UDP),a2s.port17777,maxPlayers64 (range 1 to 256),visibletrue,battlEyetrue. On the panel the ports are assigned for you. - Since 0.9.8.73 the old
gameHost*keys becamebind*andpublic*, andsupportedGameClientTypesbecamesupportedPlatforms. scenarioIdlooks like{ECC61978EDCC2B5A}Missions/23_Campaign.conf. Set it in the Scenario ID field on the Startup tab; the official IDs are in our scenarios guide.- Set Admin password on the Startup tab, or list IDs in
game.admins, before you need them; admins log in with#loginin chat.
On this page
- Editing the config file on ChicagoServers
- Ports and addresses: bindPort, publicAddress and a2s
- The game block: name, passwords, admins, players
- gameProperties: view distance, BattlEye, voice and perspective
- The operating block
- A complete example server_config.json
- Old key names that break older tutorials
- Server not showing up or players cannot join
- Frequently asked questions
Editing the config file on ChicagoServers
You do not install or launch the server yourself. The panel installs it and starts it with your settings. When a game update is out, the Steam update bar at the top of the page shows it: click Update now (a running server stops and starts again by itself), or Validate to repair files. If you need the experimental build instead of stable, click Branch, choose it and Switch branch (make a backup first). Match the branch to the one your players run.
- Change the basics on Startup
Open your server, then the Startup tab. Server name, Scenario ID, Join password, Admin password, RCON password, Show in server browser, Crossplay (Xbox and PlayStation) and BattlEye are fields there. Click Save startup.
- Edit the rest in Server config
Open the Configs tab and pick Server config. Use the Settings view for labeled fields or Text for the whole file, then click Save.
- Restart
Click Restart at the top of the page. Changes apply when the server next starts.
The file must be strictly valid JSON, so no comments and no trailing commas. A server that refuses to start after an edit often has a stray comma or quote; the Console and Troubleshoot tabs show why. Settings the panel controls (the name, passwords, ports and player slots) are written from the Startup tab and your plan at every start, so editing them in the file does not stick.
For reference, this is how the game's own launch commands look when you run the server yourself. On ChicagoServers the panel builds the launch for you, and launch options without a Startup field are staff-only.
# Windows
ArmaReforgerServer.exe -config ".\Configs\my_server.json" -maxFPS 60
# Linux
./ArmaReforgerServer -config /home/USER/.config/ArmaReforgerServer/config.json -profile /home/USER/.config/ArmaReforgerServer -maxFPS 60-maxFPS is not in the config file; it is a launch option. Bohemia says it is heavily recommended, with a value between 60 and 120, because otherwise the server can try to use all available resources. There is no Startup field for it, so contact support if you want it set or changed.
Ports and addresses: bindPort, publicAddress and a2s
| Setting | What it does | Default |
|---|---|---|
bindAddress | Local IP the server socket binds to. Usually left empty. | empty (treated as 0.0.0.0) |
bindPort | UDP port the server listens on (1 to 65535). | 2001 |
publicAddress | The IP clients use to reach you. Either the server's own public IP or that of the machine forwarding to it. | empty (detected automatically by the backend) |
publicPort | UDP port registered with the backend. Match bindPort if the server has its own public IP; otherwise use the forwarded port. | 2001 |
a2s.address | IP the Steam Query (A2S) socket binds to. Required if you use the a2s block. Added in 0.9.9.31. | none |
a2s.port | UDP port for Steam Query requests. | 17777 |
rcon | Optional remote console block with address, port, password, permission, blacklist, whitelist and maxClients. | port 19999, permission monitor |
The panel assigns your server's ports (Startup tab, Network), so do not change bindPort, publicPort or the a2s port in the file: ports are written from the Startup tab at every start. The table is here so you know what each key means. Players need UDP 2001 and the query port 17777 open if you run the server yourself; on ChicagoServers there is nothing to open. RCON is optional: set the RCON password on the Startup tab and the Console tab handles RCON for you. If you configure the rcon block yourself, use a strong password with no spaces and keep permission at monitor (read-only commands) unless you truly need admin.
The game block: name, passwords, admins, players
| Setting | What it does | Default | On ChicagoServers |
|---|---|---|---|
game.name | Server name in the browser, 0 to 100 characters. | none | Server name on the Startup tab |
game.password | Password players must enter to join. Empty means open. | empty | Join password on the Startup tab |
game.passwordAdmin | Admin password. Players log in by typing #login PASSWORD in chat. | empty | Admin password on the Startup tab |
game.admins | Array of identity IDs and/or Steam IDs of server admins (since 0.9.9.31). From 1.0.0, listed users can use #login without a password. | empty array | Server config on the Configs tab |
game.scenarioId | Which scenario to run. See the scenarios guide. | none | Scenario ID on the Startup tab |
game.maxPlayers | Player slots, 1 to 256. | 64 | Set by your plan |
game.visible | Whether the server appears in the Server Browser. | true | Show in server browser on the Startup tab |
game.crossPlatform | If true, adds the PC and Xbox platforms to the supported platforms when missing. Does nothing when false. | false | Crossplay (Xbox and PlayStation) on the Startup tab |
game.supportedPlatforms | Platforms the server accepts. The wiki lists PLATFORM_PC and PLATFORM_XBL (Xbox). | ["PLATFORM_PC"] | Server config on the Configs tab |
game.mods | Mods clients must have, each with modId, name and version. See the mods guide. | empty array | Mods tab, or Server config |
About crossplay: the wiki page lists only the PC and Xbox values. Hosting guides, including our own knowledgebase article on crossplay, also use PLATFORM_PSN for PlayStation 5 players, and the panel's Crossplay (Xbox and PlayStation) field covers both consoles. Check the current wiki and patch notes for your version before you rely on it. Console players and mods are a separate problem; see the mods guide.
A note on the name key inside mods entries: it has no function and is only a comment to remind you which mod an ID is.
gameProperties: view distance, BattlEye, voice and perspective
| Setting | What it does | Default |
|---|---|---|
serverMaxViewDistance | Maximum view distance the server allows, 500 to 10000. | 1600 |
serverMinGrassDistance | Minimum grass distance in meters (0, or 50 to 150). 0 imposes nothing on clients. | 0 |
networkViewDistance | Maximum streaming range for replicated entities, 500 to 5000. | 1500 |
fastValidation | Fast validation of map entities on join. Bohemia says to enable it for internet-facing servers and disable it only for local debugging. | true |
battlEye | Turns BattlEye anti-cheat on or off (since 0.9.8.73). On the panel, use the BattlEye field on the Startup tab. | true |
disableThirdPerson | Forces first-person view. | false |
VONDisableUI | Hides the voice-over-network UI. | false |
VONDisableDirectSpeechUI | Hides the direct speech UI. | false |
VONCanTransmitCrossFaction | True lets players transmit on other factions' radios; false makes them listen only. | false |
missionHeader | Overrides parts of the scenario's own header, for example m_iPlayerCount. Not in the template. | none |
These keys live in Server config on the Configs tab (except battlEye, which has a Startup field). Servers running a milsim ruleset usually set disableThirdPerson and the two VONDisable options to true, as in Bohemia's own example. Leave BattlEye on for a public server.
The operating block
| Setting | What it does | Default |
|---|---|---|
lobbyPlayerSynchronise | Sends the player identity list to the GameAPI with the heartbeat (since 0.9.8.73). | true |
disableCrashReporter | Disables the server-side crash report. Same as the -disableCrashReporter launch parameter. | false |
disableServerShutdown | Stops the server shutting itself down when the backend connection is lost. Other errors, like a corrupt config, still shut it down. | false |
disableAI | Prevents AIWorld from initializing or ticking, which turns AI off entirely. | false |
aiLimit | Maximum number of AIs (since 0.9.8.64). Negative means no limit. The -aiLimit launch parameter overrides it; launch options are staff-only on ChicagoServers. | -1 |
playerSaveTime | Seconds between player saves, for both online and local storage. | 120 |
slotReservationTimeout | Seconds a slot is held for a kicked player, 5 to 300 (since 0.9.9.31). At the minimum it is effectively off. | 60 |
These keys are all in Server config on the Configs tab. Version 1.0.0 also added a navmesh streaming option under operating; read the wiki for its current key name and behavior, because it changed in 1.2.0. Version 1.2.1 also added a join queue setting (joinQueue) that is not covered in the table above; check the wiki for its fields.
A complete example server_config.json
This is a reference for the full file layout and the keys you can change by hand (admins, gameProperties, operating, mods). On ChicagoServers the name, passwords, scenario, ports, player slots and BattlEye are written from the Startup tab and your plan at every start, so set those there. If you run your own machine, replace the example IP with your server's public address. The scenario is Conflict on Everon. Remove the mods entries if you are not using mods.
{
"bindAddress": "0.0.0.0",
"bindPort": 2001,
"publicAddress": "203.0.113.10",
"publicPort": 2001,
"a2s": {
"address": "203.0.113.10",
"port": 17777
},
"game": {
"name": "My Community | Conflict Everon",
"password": "",
"passwordAdmin": "change_this_admin_password",
"admins": [],
"scenarioId": "{ECC61978EDCC2B5A}Missions/23_Campaign.conf",
"maxPlayers": 32,
"visible": true,
"supportedPlatforms": ["PLATFORM_PC"],
"gameProperties": {
"serverMaxViewDistance": 2500,
"serverMinGrassDistance": 50,
"networkViewDistance": 1000,
"disableThirdPerson": false,
"fastValidation": true,
"battlEye": true
},
"mods": []
},
"operating": {
"lobbyPlayerSynchronise": true
}
}The view-distance values come from the example on the Bohemia wiki. They are a sensible starting point, not a rule. a2s.address is the local address the query socket binds to, so on a machine of your own behind NAT use its local IP there rather than the public one.
Old key names that break older tutorials
| Old name | Current name |
|---|---|
gameHostBindAddress | bindAddress |
gameHostBindPort | bindPort |
gameHostRegisterBindAddress | publicAddress |
gameHostRegisterPort | publicPort |
playerCountLimit | game.maxPlayers |
supportedGameClientTypes | game.supportedPlatforms |
root/passwordAdmin | game.passwordAdmin |
The wiki marks these renames as happening before 0.9.8.73. If you copy a config from an old video or forum post and settings seem ignored, look here first.
Hosting with ChicagoServers? The ArmA Reforger server hosting page lists what is included, such as free server backups and SFTP file access.
Server not showing up or players cannot join
- Not in the browser: check Show in server browser on the Startup tab (
visible), and that the server finished starting without errors on the Console and Troubleshoot tabs. If you run your own machine behind NAT or with several network interfaces, also checkpublicAddress. - Can see it, cannot connect: make sure the server is running and players use the address shown at the top of the server's page. On a machine you run yourself, confirm UDP
2001(or yourbindPort) is reachable from outside, and that a forwarded port matchespublicPort. - BattlEye problems: BattlEye is on by default (
battlEyetrue), so players need it working too. Check the server log on the Console tab and the client logs before deciding to turn it off with the BattlEye field on the Startup tab. - Admin login fails: the password must match Admin password on the Startup tab. Click Save startup and Restart after changing it, then type
#login PASSWORDin chat with no quotes. - Config ignored: make sure you clicked Save in Server config on the Configs tab and then Restart. Values that have a Startup field (name, passwords, scenario, ports, slots) are written from that tab at every start, so change them there. On a machine you run yourself, confirm the path passed to
-config; the parameter is ignored when you launch with-server, which is the local-world mode.
Frequently asked questions
What ports does an Arma Reforger server use?
The game port defaults to 2001 over UDP (bindPort and publicPort), and the Steam Query (A2S) port defaults to 17777. The optional RCON block defaults to port 19999. On ChicagoServers the panel assigns your ports; they are listed on the <strong>Startup</strong> tab under <strong>Network</strong> with the address to copy, and there is nothing to open on your side.
How do I make myself admin on my Arma Reforger server?
Set <strong>Admin password</strong> on the <strong>Startup</strong> tab, click <strong>Save startup</strong>, click <strong>Restart</strong>, join the server, and type #login followed by that password in chat. You can also list your Steam ID or identity ID in game.admins in <strong>Server config</strong> on the <strong>Configs</strong> tab; since 1.0.0 listed users can log in without a password.
How do I enable crossplay on an Arma Reforger server?
Turn on <strong>Crossplay (Xbox and PlayStation)</strong> on the <strong>Startup</strong> tab, then <strong>Save startup</strong> and <strong>Restart</strong>. In the config file the equivalent is game.crossPlatform set to true, or you list the platforms yourself in game.supportedPlatforms. The Bohemia wiki documents PLATFORM_PC and PLATFORM_XBL. Modded servers and console players have limitations, so test with the platforms you want to support.
Where do I get a valid scenarioId?
The official ones are in our scenarios guide, for example {ECC61978EDCC2B5A}Missions/23_Campaign.conf for Conflict on Everon. Enter the one you want in <strong>Scenario ID</strong> on the <strong>Startup</strong> tab. The -listScenarios launch option logs every valid ID but is staff-only on ChicagoServers, so contact support if you need the full list for your build.