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
Tip: Keep the config.json admin list small; it is your most powerful tier
Tip: Build a separate moderator group with clear rules even though Reforger does not enforce sub-tiers in the file
Tip: Document who has access and why, so removing access later is easy
Note: A Reforger/Bohemia account ID is tied to the player’s game account (not their platform login such as a Steam ID), so it stays the same across name changes and platforms
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.
| Command | Description | Example |
|---|---|---|
#login <password> | Authenticate as admin in-game using the passwordAdmin value from config.json | #login strong-secret |
#logout | Drop admin authentication for the current session | #logout |
Game Master menu | On Game Master scenarios, the live mission-building and control interface available to admins | Opened in-game by an authenticated admin |
Tip: Share the admin password only through a private channel, never in public chat
Tip: Rotate the admin password if it may have leaked, then restart the server
Warning: 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. On LoafHosts you do not need to hand-edit config.json: the Reforger Config Editor has a built-in scenario picker (no manual JSON editing), and the panel’s Rotator tooling can automate cycling scenarios on a schedule. Under the hood this changes game.scenarioId in config.json on restart — so 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
Tip: A predictable rotation schedule drives repeat attendance
Tip: 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.
Tip: Vary the map and faction matchup in Conflict so the same mode plays differently each night
Tip: Use Game Master nights to run scripted operations that a fixed scenario cannot offer
Tip: Mix objective-heavy sessions with lighter ones so the schedule has rhythm
Note: 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 persistent Reforger account/identity ID, because it survives name changes — not the in-session playerId shown by #players, which changes every session.
On LoafHosts you do not have to be in-game to moderate. The panel ships a BattlEye RCon Console for Arma Reforger with structured kick, ban, and unban actions, a live player roster, and a persistent ban list — all from the web panel, with the RCON password never exposed to the browser. Use the RCon Console as your day-to-day moderation tool, and keep the in-game console commands below as the in-session fallback.
| Command | Description | Example |
|---|---|---|
#kick <playerId> | Remove a player from the server for the current session | #kick 7 |
#ban create <id> <durationSeconds> [reason] | Create a persistent ban; 0 seconds means permanent | #ban create 76561198000000000 0 teamkilling |
#ban list / #ban remove <id> | List active bans, or lift a ban | #ban list |
Game Master player management | Kick, ban, and team-manage players from the Game Master menu on GM scenarios | Players panel in the GM menu |
The #players list shows the current-session playerId used by #kick. Persistent bans should target the account/identity ID instead: #ban create accepts a playerId, identityId, or playerName, but only the identity ID guarantees the ban survives across sessions and name changes. Pass the duration in seconds (0 = permanent), and lift bans with #ban list / #ban remove.
Tip: Ban by Reforger ID where possible, since it persists through name changes
Tip: Keep a record of who was kicked or banned and why
Warning: 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
Tip: Consistency matters more than severity; players accept rules that are applied evenly
Tip: 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.
Tip: Schedule a daily restart during a quiet hour to free server memory and reset accumulated AI/entity state
Tip: Schedule regular backups and always back up before mod or scenario changes
Tip: Watch the console after each restart so a new error is caught early
Note: 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
Tip: Never make a permanent decision while angry; a short cooldown leads to better calls
Tip: If staff disagree, decide as a team rather than letting one admin act alone
Frequently Asked Questions
How do I become an admin on an Arma Reforger server?
Admin rights are granted by adding your Reforger ID to the game.admins array in config.json and restarting the server. In-session, you then authenticate with the #login command using the admin password set in config.json.
How do I find my Reforger ID?
Launch Arma Reforger, go to the main menu, and click your profile name or picture. The Reforger ID is displayed there as a string of characters. A Reforger/Bohemia account ID is tied to your game account (not your platform login such as a Steam ID), so it stays the same across name changes and platforms.
Does Arma Reforger have admin permission tiers?
Reforger keeps server admin access simple: anyone in the config.json admins array gets admin tools. There is no deep built-in tier system, so communities typically build their own structure, with a small group of full admins and a wider group of in-game moderators.
How do I rotate scenarios on my Reforger server?
Update the game.scenarioId field in config.json to the new scenario and restart the server, or use admin rotation tooling to switch live. Many communities run a fixed rotation, such as a different scenario each night of the week, and announce the schedule.
How do I kick or ban a player in Arma Reforger?
Use the #kick command to remove a player for the current session and the #ban command to remove them persistently, both with the player ID. On Game Master scenarios, an authenticated admin can also kick and ban from the Game Master menu. Ban by Reforger ID so it survives name changes.
What is the Game Master menu?
Game Master is Arma Reforger’s live mission-building mode. On a Game Master scenario, an authenticated admin opens the Game Master menu to build and control the mission in real time, including spawning units, setting objectives, and managing players.
How should I structure a moderation team?
Publish clear rules, define an escalation ladder from warning to kick to temporary ban to permanent ban, and log every action with the player, reason, date, and moderator. Keep the config.json admin list small and trusted, with a wider moderator group enforcing rules in-game.
How do I keep my Reforger server stable as an admin?
Automate the routine: schedule a daily restart to clear memory, schedule regular backups, and back up before any mod or scenario change. Watch the console after restarts so new errors are caught early, and on Loafbox rely on Terabit.io DDoS protection to stay reachable.