This guide covers admin setup, RCON access, Workshop mod installation, scenario mods, BattlEye anti-cheat configuration, and troubleshooting for your Arma Reforger dedicated server. For initial server setup, configuration, scenario selection, and connection instructions, see Arma Reforger Server Setup Guide.
1. Admin Setup
Arma Reforger uses an identity-based admin system. Admins are defined in the config.json file using their Bohemia Interactive (BI) identity IDs.
Finding Your Identity ID
- Launch Arma Reforger and open the Profile section from the main menu.
- Your Bohemia Interactive identity ID is displayed on your profile page. It is a long alphanumeric string.
- Alternatively, you can find it on your Bohemia Interactive account page under your profile settings.
Adding Admins to config.json
- Stop the server from GPanel.
- Open
config.jsonusing the Files tab or via SFTP. - Locate or add the
adminsarray inside thegameobject. Add the identity IDs of each admin player:
{
"game": {
"name": "My Server",
"admins": [
"xxxxxxxxxxxxxxx",
"yyyyyyyyyyyyyyy"
],
...
}
}
- Each entry in the
adminsarray is a string containing one player's Bohemia Interactive identity ID. - You can add as many admins as needed. Separate entries with commas.
- Save the file and start the server. The listed players will have admin privileges when they join.
Admin Capabilities
Players listed in the admins array have access to:
- Kick/Ban players through the in-game server management menu.
- Game Master mode -- If running a Game Master scenario, admins can act as the GM, placing units, objectives, and controlling the scenario in real-time.
- Administrative commands through the in-game console when enabled.
2. RCON Access
RCON (Remote Console) allows you to execute server commands without joining the game. This is useful for automated management, scheduled restarts, and monitoring.
Setting Up RCON
- Set the
ADMIN_PASSWORDstartup variable in GPanel, or setpasswordAdmininconfig.json. This is the RCON password. - Ensure the RCON port is accessible. By default, the RCON port is your game port plus 1 (e.g., game port 2001 = RCON port 2002). Check GPanel's Network tab for your allocated ports.
Connecting via RCON
You can use any BattlEye RCON-compatible client to connect. Popular options include:
- BattlEye RCon -- The official BattlEye RCON client.
- ArmA Reforger Server Tool -- Community tools designed for Reforger server management.
Connect using your server's IP, RCON port, and admin password.
| Command | Description |
|---|---|
#kick <player_id> |
Kick a player from the server. |
#ban <player_id> |
Ban a player from the server. |
#shutdown |
Gracefully shut down the server. It is generally better to use GPanel for stops and restarts. |
#restart |
Restart the current scenario without restarting the server process. |
players |
List currently connected players with their IDs. |
3. Workshop Mod Installation
Arma Reforger supports mods through the Bohemia Interactive Workshop. Mods are added to the server by specifying their mod IDs in config.json.
Finding Mod IDs
- Browse the Arma Reforger Workshop in-game or on the Bohemia Interactive website.
- Find the mod you want to install and note its Mod ID (a long alphanumeric string) and Version number.
- Some mods also have a Scenario ID if they include custom scenarios. You will need this if you want to run a modded scenario.
Adding Mods to config.json
- Stop the server from GPanel.
- Open
config.jsonusing the Files tab or via SFTP. - Locate the
modsarray inside thegameobject. Add each mod using the following format:
{
"game": {
"mods": [
{
"modId": "5965280B2B15DE67",
"name": "Example Mod",
"version": "1.0.0"
},
{
"modId": "ABC123DEF4567890",
"name": "Another Mod",
"version": "2.1.0"
}
],
...
}
}
modId-- The unique Workshop mod identifier.name-- A descriptive name for your reference. This does not affect loading but helps identify mods in the config.version-- The mod version to use. The server will download this version from the Workshop on startup.
mods array from the Workshop. You do not need to manually upload mod files via SFTP. The first start after adding new mods may take longer as the server downloads the mod data.
Load Order
Mods are loaded in the order they appear in the mods array. If you have mods that depend on other mods (e.g., a mod that requires a framework mod), list the dependency first:
"mods": [
{ "modId": "FRAMEWORK_MOD_ID", "name": "Framework", "version": "1.0.0" },
{ "modId": "DEPENDENT_MOD_ID", "name": "Addon", "version": "1.0.0" }
]
4. Scenario Mods
Some Workshop mods include custom scenarios (game modes or maps). To use a modded scenario:
- Add the mod to the
modsarray as described above. - Set the
scenarioIdto the scenario's resource ID, which is provided in the mod's Workshop description.
{
"game": {
"scenarioId": "{MOD_SCENARIO_RESOURCE_ID}Missions/CustomMission.conf",
"mods": [
{
"modId": "SCENARIO_MOD_ID",
"name": "Custom Scenario Mod",
"version": "1.0.0"
}
]
}
}
5. BattlEye Anti-Cheat
Arma Reforger includes BattlEye anti-cheat protection. It is enabled by default and recommended for public servers.
| Setting | Value | Effect |
|---|---|---|
battlEye |
true |
Players must have BattlEye installed and running. Cheaters are detected and banned. Recommended for public servers. |
battlEye |
false |
No anti-cheat enforcement. Players can join without BattlEye. Use only for private/testing servers. |
The battlEye setting is located inside the gameProperties object in config.json:
"gameProperties": {
"battlEye": true
}
6. Troubleshooting
Mods Not Loading
- Verify the
modIdandversioninconfig.jsonare correct. Copy them directly from the Workshop listing to avoid typos. - Check the server console log for download errors. The server may fail to download mods if the Workshop is temporarily unavailable.
- Ensure the mod is compatible with the current version of Arma Reforger. Mods may break after game updates.
- Try removing all mods and adding them one at a time to identify which mod is causing issues.
- Verify your JSON syntax is correct. A syntax error anywhere in
config.jsonwill prevent the entire file from loading.
Server Crashes
- Check the console for error messages before the crash. Common causes include incompatible mods and invalid configuration values.
- If the crash occurs after adding a mod, remove the mod and test again. Some mods may conflict with each other.
- Validate
config.jsonwith a JSON validator to rule out syntax errors. - Try reducing
maxPlayersorserverMaxViewDistanceif the server crashes under load. - If crashes persist, open a support ticket with your server IP, the content of
config.json(redact passwords), and any error messages from the console.
Connection Issues
- If players cannot connect after adding mods, confirm they have the same mods installed. Arma Reforger will prompt players to download required mods when joining, but this can fail if the mod version does not match exactly.
- Verify the
versionfield in your mod entries matches the version available on the Workshop. Outdated version numbers will cause a mismatch. - Check that
battlEyesettings are consistent -- if enabled on the server, players must have BattlEye running. - If the server is not visible in the browser, check that
visibleistrueanda2sQueryEnabledistrueinconfig.json. - Ensure both the server and all clients are running the same game version. Arma Reforger updates can temporarily break compatibility.
Admin Privileges Not Working
- Confirm your Bohemia Interactive identity ID is correctly listed in the
adminsarray inconfig.json. - Identity IDs are case-sensitive. Copy them exactly as shown in your Bohemia profile.
- Ensure
config.jsonis properly formatted. A JSON syntax error will prevent the admins list from loading. - Restart the server after making changes to
config.json. Changes are only read on startup.
Related Articles
- Arma Reforger Server Setup Guide
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Server Startup Guide
Need Help?
If you run into issues with your Arma Reforger server that are not covered here, open a support ticket and include your server IP, a description of the problem, and any relevant error messages from the GPanel console.