How to Change Your Arma Reforger Scenario, and How to Find Any scenarioId

The scenario your server loads is one field in config.json. The awkward part is that it is not a readable name — it is a GUID and a file path, and getting one character wrong stops the server booting.

Below are the common official IDs, and — more importantly — the official way to get the exact ID of anything else, including Workshop missions.

Where it goes#

scenarioId lives inside the game block:

{
    "game": {
        "name": "Example Milsim",
        "scenarioId": "{ECC61978EDCC2B5A}Missions/23_Campaign.conf",
        "maxPlayers": 48
    }
}

Copy the whole value including the braces. Then restart the server — the scenario is read at boot, so a running server will not pick up a change.

The authoritative method: -listScenarios#

Before the table, the thing worth knowing: there is an official startup parameter that prints every loadable scenario's .conf path, including scenarios that came from installed mods.

Add -listScenarios to the server's startup parameters and start it. The output lists what that server can actually load, which is better than any published table for two reasons: it reflects your installed mods, and it cannot go stale when Bohemia adds or renames a scenario.

Use the table below for convenience, and -listScenarios whenever you need something that is not on it or want to confirm a value.

Common official scenario IDs#

Conflict is the persistent, objective-based mode most public servers run. Game Master is the live scenario-editing mode. Combat Ops is co-op against AI.

Workshop scenarios#

Community scenarios are not on any official list, so -listScenarios is the method. Start the server with the scenario's mod installed, and its .conf path appears in the output alongside the official ones.

One thing that trips people up: the mod providing the scenario has to be in the server's mods list. A Workshop scenarioId with no corresponding mod entry fails at boot. See adding Workshop mods.

Verify it worked#

1. Validate config.json in the config validator — a broken brace on the scenario line is easy to make and produces a silent boot failure.
2. Restart and watch the log until the scenario reports as loaded.
3. Join and confirm you are in the mode you expected. Conflict and Game Master are obvious on spawn; the Conflict sub-maps are less so, and it is worth checking you got the right one.
4. If the server does not start, the scenario line is the first thing to re-read character by character.

Trusted references#

• Arma Reforger: Startup Parameters — -listScenarios and the rest of the CLI reference
• Arma Reforger: Server Config — the scenarioId field
• Arma Reforger Workshop — the official Workshop browser