Running an Arma Reforger server as an admin means three things: granting the right people admin access, keeping the scenario and layer rotation fresh, and moderating players fairly with the tools at hand. Admin rights are assigned by Reforger ID in config.json, and from there an admin can use in-game tools, the Game Master menu, and console commands. This guide covers admin roles, scenario and layer rotation, and the day-to-day moderation workflow that keeps a military-sim community healthy.
Admin Access and Roles in Reforger
Arma Reforger grants admin rights through the game.admins array in config.json, which holds the Reforger IDs of trusted players. Anyone listed gets admin tools. Reforger itself keeps this simple rather than offering a deep tiered permission system, so in practice a community builds its own role structure on top: a small group of full admins in config.json, and a wider group of moderators who enforce rules in-game without server-file access.
- Collect the Reforger ID of each admin from the main menu profile screen
- Add each ID to the game.admins array in config.json
- Restart the server so the admin list takes effect
- Have each admin confirm access by running #login with the admin password in-game
- Keep the config.json admin list small; it is your most powerful tier
- Build a separate moderator group with clear rules even though Reforger does not enforce sub-tiers in the file
- Document who has access and why, so removing access later is easy
- A Reforger ID is account-bound and is not the same as a Steam ID
Logging In and Using Admin Tools
Being in the admins array grants the rights, but an admin still authenticates in-session. The #login console command with the admin password elevates the admin during play, and from there they can run management commands and, on Game Master scenarios, open the Game Master menu.
#login strong-secret#logoutOpened in-game by an authenticated admin- Share the admin password only through a private channel, never in public chat
- Rotate the admin password if it may have leaked, then restart the server
- Admin actions are visible to the server and should be treated as on the record
Scenario Rotation
A server that runs the same scenario forever gets stale. Scenario rotation keeps the experience fresh by cycling through different Conflict campaigns and Game Master missions. The simplest approach is to change game.scenarioId in config.json and restart, but a planned rotation, for example a different scenario per night of the week, gives your community something to look forward to.
- Build a list of scenarios you want in rotation, each with its full scenarioId
- Decide a cadence, such as a fixed scenario per weeknight or a weekly swap
- To change the active scenario, update game.scenarioId and restart, or use admin rotation tooling
- Announce the rotation schedule so players know what to expect
- Take a backup before swapping scenarios on an active server
- A predictable rotation schedule drives repeat attendance
- Keep a couple of scenarios in reserve so you can react if one is not landing with players
Layer and Mission Variety
Beyond swapping whole scenarios, you can vary the experience within a game mode. Conflict offers different maps and faction matchups, and Game Master lets an admin build a fresh mission live every session. Treating each session as a chance to vary the map, the factions, or the mission design keeps even a single game mode from feeling repetitive.
- Vary the map and faction matchup in Conflict so the same mode plays differently each night
- Use Game Master nights to run scripted operations that a fixed scenario cannot offer
- Mix objective-heavy sessions with lighter ones so the schedule has rhythm
- Game Master is Reforger's live mission-building mode; an authenticated admin shapes the mission in real time
Player Moderation Tools
Moderation in Reforger is handled through admin tools and console commands. Kicks remove a player for the session, bans remove them persistently, and on Game Master scenarios an admin can also manage players directly from the menu. The reliable identifier for a ban is the player's Reforger ID, because it survives name changes.
#kick 7#ban 7Players panel in the GM menu- Ban by Reforger ID where possible, since it persists through name changes
- Keep a record of who was kicked or banned and why
- A kick is temporary for the session; use a ban when you need the removal to stick
Building a Moderation Workflow
Tools only work well inside a process. A healthy server has written rules, a consistent escalation ladder, and a record of enforcement so decisions are fair and defensible. The goal is that any moderator handling the same situation reaches the same outcome.
- Publish clear server rules where every player can see them
- Define an escalation ladder, for example verbal warning, then kick, then temporary ban, then permanent ban
- Log every moderation action with the player, the reason, the date, and the moderator
- Offer an appeals channel so mistakes can be corrected
- Review tough cases as a staff team to keep enforcement consistent
- Consistency matters more than severity; players accept rules that are applied evenly
- Train new moderators on the escalation ladder before giving them tools
Server Routine and Automation
An admin's job is easier when routine work is automated. The LPV5 panel includes scheduling and backup tools, so restarts, backups, and recurring tasks can run without anyone remembering to do them. A predictable routine also makes problems easier to spot, because anything unusual stands out against a stable baseline.
- Schedule a daily restart during a quiet hour to keep memory and AI clean
- Schedule regular backups and always back up before mod or scenario changes
- Watch the console after each restart so a new error is caught early
- Loafbox includes Terabit.io L4/L7 DDoS protection, which keeps a public community server reachable under attack
Handling Incidents and Disputes
Even a well-run server has incidents: a heated dispute, a suspected cheater, a teamkilling complaint, or a contested ban. The admin's job is to slow the situation down, gather facts, and decide calmly. Treating incidents with a steady process protects both the community's trust and the admin team's credibility.
- Separate the parties and calm the immediate situation before deciding anything
- Gather facts from the server log, witnesses, and any recordings
- Apply the escalation ladder rather than reacting emotionally
- Communicate the decision and the reason to the affected player
- Record the outcome so it informs future decisions
- Never make a permanent decision while angry; a short cooldown leads to better calls
- If staff disagree, decide as a team rather than letting one admin act alone