{"id":1966,"date":"2022-08-21T10:02:32","date_gmt":"2022-08-21T10:02:32","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=1966"},"modified":"2026-06-15T19:24:34","modified_gmt":"2026-06-15T19:24:34","slug":"how-to-install-mods-on-arma-reforger-server","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/how-to-install-mods-on-arma-reforger-server\/","title":{"rendered":"How to Install Mods on Arma Reforger Server"},"content":{"rendered":"\n

Adding Workshop mods to an Arma Reforger dedicated server is not a “drop files in a folder” job like older Arma titles. Everything runs through a single JSON array in your server config, and the server downloads each mod from the Workshop backend on startup. Get the format right and your server pulls every mod automatically; get one field wrong and the server either refuses to launch or quietly drops players from Xbox and PlayStation. This guide walks through the exact mods<\/code> array structure, how to find a mod’s modId<\/code>, how to pin versions, how load order actually behaves, and the console crossplay caveat that catches almost everyone. It is written against the current 1.7.0.41 “Partisan Update” (released May 28, 2026) and the official Bohemia Interactive server config specification.<\/p>\n\n\n\n

Where mods live: the mods<\/code> array in config.json<\/h2>\n\n\n\n

Arma Reforger has no separate mod loader and no -mod<\/code> launch parameter for dedicated servers. Mods are declared inside your config.json<\/code> \u2014 the same JSON file you pass to the server with -config<\/code> \u2014 under game.mods<\/code>. When the server starts, it reads that array, contacts the Workshop backend, downloads any mod it does not already have cached, and loads them before the scenario.<\/p>\n\n\n\n

The array sits inside the game<\/code> block, alongside fields like name<\/code>, scenarioId<\/code> and maxPlayers<\/code>. A vanilla config simply has \"mods\": []<\/code>. Here is the minimal shape, trimmed down to the parts that matter for modding:<\/p>\n\n\n\n

{\n  \"bindAddress\": \"\",\n  \"bindPort\": 2001,\n  \"publicAddress\": \"\",\n  \"publicPort\": 2001,\n  \"a2s\": { \"address\": \"\", \"port\": 17777 },\n  \"game\": {\n    \"name\": \"My Modded Server\",\n    \"scenarioId\": \"{ECC61978EDCC2B5A}Missions\/23_Campaign.conf\",\n    \"maxPlayers\": 64,\n    \"modsRequiredByDefault\": true,\n    \"mods\": [\n      { \"modId\": \"59672945D69497A0\", \"name\": \"Server Admin Tools\", \"version\": \"1.0.5\" },\n      { \"modId\": \"5972D43D44FCABDD\", \"name\": \"Example Optional Mod\", \"required\": false }\n    ]\n  }\n}<\/code><\/pre>\n\n\n\n
That is the whole mechanism. Every other modding detail \u2014 finding the GUID, pinning a version, controlling load order, handling consoles \u2014 is about filling out the objects inside that array correctly. For a full breakdown of every other field in the file (networking, RCON, view distance, BattlEye and so on), see our Arma Reforger server configuration guide<\/a>.<\/p>\n\n\n\n
The four fields of a mod entry<\/h2>\n\n\n\n
Each element in the mods<\/code> array is a JSON object with up to four fields. Only one of them is strictly required.<\/p>\n\n\n\n
\n
Field<\/th>Required?<\/th>Type \/ default<\/th>What it does<\/th><\/tr><\/thead>
modId<\/code><\/td>Yes<\/td>string (GUID)<\/td>The mod’s unique identifier from the Workshop. This is the only field that actually selects the mod.<\/td><\/tr>\n
name<\/code><\/td>No<\/td>string<\/td>Human-readable label. Purely a comment for your own reference \u2014 it has no functional effect on which mod loads.<\/td><\/tr>\n
version<\/code><\/td>No<\/td>string<\/td>Pins a specific mod version. If omitted, the server uses the latest available version.<\/td><\/tr>\n
required<\/code><\/td>No<\/td>bool, defaults to modsRequiredByDefault<\/code> (true)<\/td>If false<\/code>, the mod is auto-removed with a log warning when it can’t be downloaded, instead of blocking server start. Added in 1.2.1.<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n
The single most common mistake is assuming name<\/code> matters. It does not. You can type “Server Admin Tools” or “asdf” \u2014 the server resolves the mod entirely from modId<\/code>. Keep name<\/code> accurate purely so your config stays readable, especially once you have a dozen mods stacked up.<\/p>\n\n\n\n
Finding a mod’s modId<\/code> on the Workshop<\/h2>\n\n\n\n
The modId<\/code> is a GUID \u2014 a 16-character hexadecimal string like 59672945D69497A0<\/code>. It is not the mod’s display name and not a Steam Workshop numeric ID. Arma Reforger uses its own Workshop, and there are three reliable ways to get the GUID:<\/p>\n\n\n\n