> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabihosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Install Mods on an Arma Reforger Server

> Add Workshop mods to your Arma Reforger server hosting - find mod IDs, edit the mods array in your JSON config, and let clients auto-download on join.

Arma Reforger mods come from the official **Arma Reforger Workshop** — Bohemia's own platform, built into the game (not Steam Workshop). Installing mods on your server is refreshingly simple: you list them in your server config, the server downloads them on startup, and every player who joins **auto-downloads the same mods automatically** — on PC and console alike.

## How It Works

1. You add each mod's **ID (GUID)** and name to the `mods` array in your server's JSON config.
2. On the next start, the server downloads the listed mods from the Workshop.
3. 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 example `591AF5BDA9F7CE8B`.

<Tabs>
  <Tab title="Workshop Website">
    Browse the Workshop at [https://reforger.armaplatform.com/workshop](https://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.
  </Tab>

  <Tab title="In-Game Workshop">
    Open **Workshop** from the Reforger main menu, find the mod, and open its details page — the mod ID is listed there. This is handy for confirming a mod actually works on your game version first.
  </Tab>
</Tabs>

## Step 2: Add Mods to Your Server Config

Open your server's JSON config in the [Game Panel](https://panel.wasabihosting.com) **File Manager** and add entries to the `mods` array inside the `game` block:

```json theme={null}
"game": {
  "name": "My Wasabi Modded Server",
  "scenarioId": "{ECC61978EDCC2B5A}Missions/23_Campaign.conf",
  "mods": [
    {
      "modId": "591AF5BDA9F7CE8B",
      "name": "WeaponSwitching"
    },
    {
      "modId": "5965550F24A0C152",
      "name": "Where Am I"
    }
  ]
}
```

* `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.

<Warning>
  Keep the JSON valid: entries are separated by commas, and the last entry has **no** trailing comma. A malformed `mods` array stops the server from starting. See [Server Configuration](/games/arma-reforger/server-configuration) for the full file layout.
</Warning>

## 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](/games/arma-reforger/join-server)).

## Scenario Mods

Some mods don't just add content — they add entire **scenarios** (game modes or missions). For those:

1. Add the mod to the `mods` array as usual.
2. Change `scenarioId` to 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 `mods` array 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 `mods` array 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

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## Related Guides

<CardGroup cols={2}>
  <Card title="Server Configuration" icon="gears" href="/games/arma-reforger/server-configuration">
    The full annotated JSON config reference.
  </Card>

  <Card title="Admin Commands" icon="terminal" href="/games/arma-reforger/admin-commands">
    Admin access, in-game commands, and Game Master.
  </Card>
</CardGroup>

Running lots of mods? NVMe storage and fast CPUs make modded servers start and run smoothly — [get your Arma Reforger server](https://wasabihosting.com/game-servers/arma-reforger) from €12.49/month.