Deranged HostingDeranged Hosting

Shooters Guide

Arma Reforger

Detailed connection, admin, file, settings, mods, backup, wipe, and troubleshooting notes for Arma Reforger dedicated servers.

Order / ManageGet Help

Connect & First Checks

Before editing files

  • Use the in-game server browser or Direct Connect with panel IP and port.
  • Mods are downloaded by the game when configured correctly, but version mismatches can block joins.
  • Scenario ID and mod list define what players load.

Files & Folders

Stop server before edits

config.jsonMain server config: bind address, ports, game settings, scenarioId, server name, password, max players, mods, RCON.
profiles/logs directoryLogs, crash info, and runtime profile data.
addons/mod cacheDownloaded Workshop/addon content depending on setup.

Common Settings

High-use values

game.nameServer browser name.
game.passwordPrivate password.
game.maxPlayersPlayer cap.
game.scenarioIdMission/scenario to load.
game.modsArray of mod IDs/names/versions.
a2s.portServer query/browser port.
rconRemote console settings when enabled.

Admin Setup

Staff access

  • Configure RCON only if needed and protect the password.
  • Use supported admin/RCON workflows from the panel/template.
  • Keep config.json backed up before changing scenario/mods.

Mods & Plugins

Install carefully

  • Add Workshop/resource IDs to the mods array in config.json or panel field.
  • Version mismatches in the mods array can prevent startup or joins.
  • Change one mod at a time and watch logs.

Backups, Wipes, Rollbacks

Protect player data

  • Back up config.json and profiles before scenario or mod changes.
  • For scenario resets, back up persistence/profile data first.

Troubleshooting

Common tickets

Scenario failsBad scenarioId or required mod missing.
Players cannot joinMod version mismatch or password mismatch.
Server not visibleA2S/query port or startup failure. Test direct connect and logs.