Generate a Arma Reforger config.json
Arma Reforger reads one nested JSON file, config.json, and half the guides for it describe an older layout with different key names — so a file assembled from forum posts can be valid JSON that the server still does not understand.
Visual Settings
config.json
1 problemAdvertisement
The config.json format
Network settings sit at the top level (bindPort, publicPort), the Steam query lives in an a2s object, and everything about the game — name, passwords, scenario, player cap — sits inside game, with rendering and network ranges one level deeper in game.gameProperties. Strings are double-quoted, numbers and true/false are not, and there are no comments or trailing commas.
Advertisement
The mistake that wastes an evening
The server browser and every status checker rely on the a2s block, and it is not there unless you add it: without it the server runs and players can join by address, but nothing can query it. The other trap is guides using gameHostBindPort and similar names from before the layout changed — those keys are simply ignored now.