Skip to content
Mamba Host Docs

Arma Reforger Setup

Arma Reforger runs on Bohemia’s Enfusion engine and expects modern hardware, fast NVMe storage, and tuned network settings. Mamba Host’s Dell PowerEdge R630 nodes (dual E5-2680v4, 128 GB RAM) are configured specifically for Reforger’s CPU-heavy simulation, Workshop syncing, and real-time scenario editing.

Before You Begin

Section titled “Before You Begin”
  • Steam account owning Arma Reforger with Workshop access.
  • Custom scenarios (.gproj or .scenario) exported from the editor.
  • Decide which official mode (Conflict, Combat Ops, Game Master) or custom mission you plan to run.
  • Mod collection IDs, radio mods, and bespoke assets ready for upload.

Plan Selection

Section titled “Plan Selection”
PlanResourcesPlayer TargetNotes
Starter3 GB RAM / 1 vCPU16–24 playersConflict testing, private ops
Pro5 GB RAM / 1 vCPU32–48 playersPublic Conflict/Combat Ops
Premium8 GB RAM / 2 vCPU60–80 playersGame Master events, heavy mods

Upgrade once CPU averages exceed 80%, AI spikes become frequent, or high-fidelity Workshop assets strain VRAM.

1. Provision the Server

Section titled “1. Provision the Server”
  1. Visit https://panel.mambahost.com → Create Server → Arma Reforger.
  2. Choose plan/region and optional add-ons (MySQL for logging, extra storage, backups).
  3. Deploy (≈2 minutes) and note SFTP/RCON credentials.
  4. Enable automated backups and set retention via Scheduler → Backups.

2. First-Time Configuration

Section titled “2. First-Time Configuration”
  • Change panel + SFTP passwords immediately.
  • Download server.cfg template via SFTP and edit name, description, password (optional), and slot count.
  • Configure RCON credentials for remote admin tools.
  • If running persistent events, document a wipe/rest schedule up front.

3. Workshop & Custom Content

Section titled “3. Workshop & Custom Content”
  1. Create a Workshop collection containing the mods/scenarios you need.
  2. Add the collection ID to workshopMods[] in config; restart to sync.
  3. Upload private/custom scenario files to /scenarios and list them in mission rotation.
  4. For Game Master ops, prepare template missions plus fallback scenarios in case the GM disconnects.

4. Performance & Enfusion Tweaks

Section titled “4. Performance & Enfusion Tweaks”
  • Adjust tick rate/view distance to balance fidelity and CPU.
  • Limit AI groups per faction during 60+ player Conflict matches.
  • Tune networkBandwidth and maxPacketSize for your slot count.
  • Schedule auto restarts every few hours for heavily modded servers to clear VRAM/heap usage.
  • Monitor panel metrics; scale to Premium when CPU headroom shrinks during peak operations.

5. Maintenance

Section titled “5. Maintenance”
  • Stay on the latest stable build; test updates in staging to catch mod incompatibilities.
  • Validate Workshop dependencies after each patch—missing mods block player entry.
  • Back up configs, mod lists, and scenarios before major content drops.
  • Rotate RCON passwords and panel tokens quarterly.
  • Keep change logs for scenario tweaks so GMs can revert quickly.

6. Operations & Security

Section titled “6. Operations & Security”
  • Maintain separate panel accounts for mission makers vs. infrastructure admins.
  • Stream incidents (server restarts, crashes) to Discord via webhook for transparency.
  • Schedule weekly mission tests to verify mods still load after updates.
  • Document SOPs for Game Master handoff and emergency shutdowns.

7. Troubleshooting

Section titled “7. Troubleshooting”
  • Players stuck on “Downloading data”: ensure every mod listed in server.cfg exists, is public, or uploaded manually.
  • Desync/rubber banding: lower view distance, reduce AI counts, or upgrade plans for more CPU.
  • Workshop sync fails: restart; if still broken, clear /workshop cache and re-sync.
  • Game Master crashes: verify scenarios only reference active assets; review logs at /home/container/.config.
  • Voice issues: confirm enableVoN=1 and firewall allows UDP voice traffic (default ports already open).
Section titled “Helpful Links”