Workshop mods

Reforger uses Bohemia's own Workshop (not the Steam Workshop) for mods. Mods are identified by a hex ID and listed in your config.json — the server downloads and applies them on boot.

Where to find mods

reforger.armaplatform.com/workshop

Each mod has:

• A name
• A hex modId (e.g. 594D2E0683B812AB)
• A version
• Compatibility flags (PC-only, Xbox-compatible, etc.)

Adding mods to your server

In config.json → game.mods:

"mods": [
  {
    "modId": "594D2E0683B812AB",
    "name": "Server Admin Tools"
  },
  {
    "modId": "5972D7E50AD861A1",
    "name": "Conflict - Everon (Mod)",
    "version": "1.2.0"
  }
]

• modId is required.
• name is informational (server logs use it).
• version is optional — omit to let the server pull the latest. Pin it for stable rollouts.

Save, restart. The server downloads each mod on boot (can be slow on first start — multi-GB packs).

Crossplay caveat

If crossPlatform: true is set in config.json, every mod in your list must be marked Xbox-compatible. The Workshop page for each mod shows the supported platforms.

Adding a PC-only mod to a crossplay server causes Xbox players to be unable to join (and the server will warn on boot).

Players + auto-download

Reforger clients auto-download mods on first connect to a modded server. No subscribe-on-Workshop step like Arma 3.

The download happens inside the game launcher; players see a progress bar before the server connects. After download, subsequent joins are instant.

Server admin mods

Common useful ones:

• Server Admin Tools — extends # commands with kick/ban/ teleport/spawn
• WCS (Workshop Catalogue System) — UI for mission picking
• Conflict — Everon (Mod) — extended Conflict mode with more vehicles/factions
• GameMaster — Zeus-equivalent for Reforger

Modded scenarios

Mods can include their own scenarios. Reference them in scenarioId:

"scenarioId": "{HEX-ID-FROM-MOD}Missions/MyCustomMission.conf"

The hex prefix {...} identifies the mod that owns the scenario. The path after is relative to the mod's directory structure. The mod's Workshop page usually documents the scenario IDs.

Updating mods

Two ways:

• Pinned to a version — bump the version string in config.json, restart. Server downloads new version.
• Latest (no version) — restart pulls the current latest.

For a community server, pinning versions is safer: a mod update breaking your scenario won't catch you off-guard at 2 AM.

When a mod breaks the server

Symptom: server fails to start after a mod update or addition.

1. Check the server log — Reforger names the failing mod explicitly.
2. Remove (or pin to an older version) the offending mod in config.json.
3. Restart.

Workshop mods download into the server's data directory. To force a clean re-download, delete the mod folder under /data/reforger/profile/workshop/ and restart.