How It Works
- You add each mod’s ID (GUID) and name to the
modsarray in your server’s JSON config. - On the next start, the server downloads the listed mods from the Workshop.
- Clients joining your server download any mods they’re missing before entering — no manual installs.
Step 1: Find the Mod ID
Every Workshop mod has a unique 16-character hexadecimal ID (a GUID), for example591AF5BDA9F7CE8B.
- Workshop Website
- In-Game Workshop
Browse the Workshop at reforger.armaplatform.com/workshop. Open a mod’s page — the mod ID is shown on the page and in the page URL. Copy it exactly.
Step 2: Add Mods to Your Server Config
Open your server’s JSON config in the Game Panel File Manager and add entries to themods array inside the game block:
modId— the GUID from the Workshop (required).name— human-readable label; helpful for you, and used in logs (required).version— optional. Add"version": "1.0.1"to pin a specific version; omit it to always run the latest. Pinning avoids surprise breakage when a mod updates, but you must bump it manually.
Step 3: Restart and Verify
Restart the server from the panel. Watch the Console: the server logs each mod as it downloads and loads. Large mods take time on first start — subsequent starts reuse the downloaded files. Once it’s up, join in-game; your client will auto-download the mod list (see Join Your Server).Scenario Mods
Some mods don’t just add content — they add entire scenarios (game modes or missions). For those:- Add the mod to the
modsarray as usual. - Change
scenarioIdto the scenario the mod provides. Mod authors list their scenario IDs on the Workshop page, and the server console prints available scenarios from loaded mods at startup.
Load Order and Dependencies
- If a mod depends on other mods, list the dependencies in the
modsarray too. The Workshop page shows a mod’s dependencies — missing ones typically cause errors at startup or on join. - The order of entries in the
modsarray generally follows list order for loading. For most content mods order doesn’t matter; when two mods patch the same thing, follow the mod author’s recommendation. - Fewer, well-maintained mods beat a huge list: every mod adds download time for new players and potential breakage on game updates.
Common Errors
Server won't start after adding a mod
Server won't start after adding a mod
Usually one of: a typo in the GUID (check every character — it must match the Workshop ID exactly), broken JSON syntax (missing comma/quote), or a pinned
version that no longer exists. The console log names the offending mod.Mod broke after a game update
Mod broke after a game update
Major Reforger updates frequently break mods until authors update them. If your server fails to load or players crash on join after patch day, temporarily remove the suspect mods from the array, restart, and re-add them once updated versions are published.
Players can't join a modded server
Players can't join a modded server
Their client must be on the same game version and able to download the mods. Have them retry (downloads resume), pre-download the mods from the in-game Workshop, and confirm the mod list hasn’t just changed server-side while they were queued.
Related Guides
Server Configuration
The full annotated JSON config reference.
Admin Commands
Admin access, in-game commands, and Game Master.

