How to add Workshop scenarios to an Arma Reforger server?

Want to run a Workshop scenario on your Arma Reforger server? Follow this step-by-step to add the mod, set server.json, and boot cleanly. Even first-time hosts can nail this.

Prerequisites

• Access to your Oxygenserv panel (login and password)
• Arma Reforger server installed and reachable
• The scenario’s Workshop page URL (reforger.armaplatform.com/workshop)
• Server stopped before editing (prevents file corruption)
• File editor in panel to open server.json

Detailed steps

1. Grab scenario details from the Workshop
   Open the Arma Reforger Workshop and find your scenario (e.g., “Everon Conflict”, “Custom Mission”). On the mod/scenario page, copy the exact Name, Version, and ID (examples: ID 59AD59368755F41A, version 1.2.3). Keep casing and spaces exactly as shown. Tip: paste these values into a notes file—you’ll drop them into the config next.
2. Stop the server before you edit
   In Oxygenserv panel, open your Arma Reforger service and hit the red “Stop” button. Wait until the console clearly shows the server is stopped (no more scrolling logs). If it hangs for 30+ seconds, refresh and confirm the state again. Never edit while it’s still “Stopping”.
3. Add the scenario’s mod to server.json
   Go to “Files” and open server.json in the editor. Find the "mods": [] array, insert a new line right after the first [ and paste this template EXACTLY: { "modId": "IDHere", "name": "NameHere", "version": "VersionHere" }. Replace with your real values (e.g., { "modId": "59AD59368755F41A", "name": "Everon Conflict", "version": "1.2.3" }). If you add multiple mods, put a comma , between each block } except after the last; one extra comma will cause a “JSON parse error” on boot.
4. Set the Scenario ID (what to launch)
   Two paths depending on your panel: a) “Startup” tab → “Scenario ID” field: paste the full ID like {59AD59368755F41A}Missions/23_Campaign.conf. b) If there’s no field, in server.json under the "game" section, add/edit "scenarioId": "{59AD59368755F41A}Missions/23_Campaign.conf". The part in braces is the mod GUID, followed by the exact mission .conf path (usually documented on the Workshop page). If you don’t know the path, check the mod description—it typically lists Missions/... to use.
5. Save, start, and read the logs
   Click “Save” top-right, go back to “Console”. Hit the green “Start” and watch for lines like “Workshop mod loaded” then “Scenario loaded”—that means you’re good. If you see “Scenario not found” or “Cannot open … .conf”, your scenarioId is wrong (GUID or path); paste it exactly. If you get “JSON parse error”, fix commas/quotes in mods; if “version mismatch”, update the version to match the Workshop release.
6. Test from the game client
   Launch Arma Reforger and join via server browser or direct connect. If the server doesn’t list, confirm your ports are open (typical: game port 2001, query port 17777 over UDP). If players get “Required mods missing”, the mod didn’t load correctly—recheck step 3. Once in, verify the correct scenario name/briefing appears and no prolonged black screen occurs.

Tips & optimization

– Pin mod versions: keep the exact "version" value to avoid out-of-sync issues after Workshop updates. Update deliberately and test.
– With multiple mods, order matters: load frameworks first, scenarios after, to satisfy dependencies.
– In server.json, set "playerCountLimit" to the scenario’s recommendation (e.g., 20/32) for stable performance.
– Tame latency: set "maxPing" (e.g., 250) to filter poor connections and protect gameplay quality.
– Keep a text file with your key IDs (modId, scenarioId) for quick rebuilds or migration.

FAQ

I can’t find the Missions/… .conf path. Where is it?

Check the mod’s Workshop description—authors usually provide the exact path (e.g., Missions/23_Campaign.conf). Alternatively, install the mod locally, open its folder, and locate the .conf mission file. Then set {GUID}Missions/xxx.conf in scenarioId (replace {GUID} with the modId in braces). Restart and confirm in logs.

Players see “Required mods missing”

Ensure the scenario mod is listed in "mods": [] with correct ID and version. Confirm the server actually loads it (look for “Workshop mod loaded” on boot). If the author lists dependencies, add those mods to mods as well. Restart after each change.

The server boots but loads the wrong scenario

Your scenarioId likely points to a different .conf. Replace it with the author-provided value (GUID+path), e.g., {59AD59368755F41A}Missions/MyScenario.conf. Save, restart, and watch for “Scenario loaded” to confirm.

Nice work! Your Arma Reforger server now launches the exact Workshop scenario you want. Keep iterating—test, tweak, and save a working config to move even faster next time.

Related articles

• How do I add mods to a Euro Truck Simulator 2 server?
• How do I change mission (scenario) in Arma Reforger?
• How do I install mods on a Palworld server?