Learn how to configure admin access, use in-game admin commands, set up BattlEye anti-cheat, and manage your Arma 3 server with RCON tools. For initial server configuration, see our Server Setup Guide. For mod management, see the Mod Installation Guide.
Admin Password Configuration
The admin password is set in your server.cfg file. This password grants full server control to anyone who logs in with it in-game.
// server.cfg - Admin Password
passwordAdmin = "YourSecureAdminPassword";You can also set a separate command password for server-side scripting commands (rarely needed for most server operators):
serverCommandPassword = "AnotherSecurePassword";In-Game Admin Login
To log in as admin while connected to your server:
- Press the chat key (default:
/in the chat channel) to open the chat input. - Type the following command:
#login YourSecureAdminPasswordIf the password is correct, you will see a confirmation message in the chat. You now have access to all admin commands for the duration of your session.
Admin Commands Reference
Once logged in as admin, you can use the following commands in the chat input. All commands are prefixed with #:
| Command | Description |
|---|---|
#login <password> |
Authenticate as server admin. |
#logout |
Revoke your admin session. |
#kick <player_id> |
Kick a player from the server. Use the player's ID number from the player list. |
#ban <player_id> |
Ban a player from the server (added to ban.txt). |
#restart |
Restart the current mission. All players stay connected but the mission reloads. |
#reassign |
Move all players back to the role selection (lobby) screen without restarting the mission. |
#missions |
Open the mission selection screen, allowing you to change the current mission. |
#shutdown |
Immediately shut down the server. All players are disconnected. |
#lock |
Lock the server, preventing new players from joining. |
#unlock |
Unlock the server, allowing new players to join again. |
#monitor <interval> |
Display server performance information at the given interval (seconds). Use #monitor 0 to disable. |
#debug off |
Disable voice-over-network debugging indicators. |
#init |
Re-initialize the server (reload server.cfg without full restart). |
#exec ban <player_id> |
Alternative ban command that also adds to the BattlEye ban list. |
#kick and #ban commands use the player's numeric ID, not their name. You can find player IDs in the server console output in GPanel, or use the player list accessible through the in-game escape menu.
Managing Bans
Bans are stored in the ban.txt file in your server directory. Each line contains a player's Steam64 ID (or GUID). You can manage bans by editing this file directly:
// ban.txt format
// Each line: GUID or Steam64ID
76561198012345678
76561198087654321To unban a player, remove their entry from ban.txt and restart the server (or use #init to reload the configuration).
BattlEye Anti-Cheat Configuration
BattlEye (BE) is the anti-cheat system used by Arma 3. It is highly recommended to keep BattlEye enabled on public servers to prevent cheating and exploits.
Enabling BattlEye
Ensure the following is set in your server.cfg:
BattlEye = 1; // 1 = enabled, 0 = disabledBattlEye Configuration Files
BattlEye configuration files are located in the battleye/ directory within your server profile or server root. The main configuration file is beserver_x64.cfg (or beserver.cfg on 32-bit):
// battleye/beserver_x64.cfg
RConPassword MyRconPassword123
RConPort 2306
MaxPing 250| Setting | Description |
|---|---|
RConPassword |
Password for RCON (Remote Console) access. Required for external RCON tools. |
RConPort |
Port used for RCON connections. Default is game port + 4 (e.g., 2306 if game port is 2302). This port must be accessible if you want to use external RCON tools. |
MaxPing |
Maximum allowed ping before BattlEye kicks the player (separate from server.cfg maxPing). |
BattlEye Filter Files
BattlEye uses filter files to detect and block suspicious scripts and commands. These are text files in the battleye/ directory:
scripts.txt— Filters for script executionremoteexec.txt— Filters for remote execution callspublicvariable.txt— Filters for public variable broadcastssetdamage.txt,setpos.txt, etc. — Filters for specific commands
Each line in a filter file has the format:
// Filter line format: ACTION FILTER_STRING
// Actions: 1 = log, 2 = log+kick, 3 = log only (no kick), 4 = kick without log, 5 = log+ban
// Example scripts.txt entries:
5 createVehicle // Ban anyone using createVehicle in scripts
1 "BIS_fnc" // Log BIS functions (usually safe)
7 "" // Default action for unmatched entries (7 = log)battleye/ directory to identify which filter is triggering and add appropriate exceptions.
BattlEye RCON Tools
RCON (Remote Console) allows you to manage your server externally without being logged into the game. There are several popular RCON tools for Arma 3:
BEC (BattlEye Extended Controls)
BEC is a comprehensive server management tool that connects via BattlEye RCON. Features include:
- Scheduled restart messages and automatic restarts
- Player monitoring and kick/ban management
- Automated messages (rules, announcements)
- Whitelist management
- Custom command scheduling
BEC configuration requires your server's IP, RCON port, and RCON password as set in beserver_x64.cfg.
DaRT (Arma RCON Tool)
DaRT is a lightweight, GUI-based RCON client. To connect:
- Download DaRT from its official source.
- Enter your server IP, RCON port (e.g.,
2306), and RCON password. - Click Connect.
- Once connected, you can view players, send messages, kick/ban players, and execute server commands.
Common RCON Commands
These commands can be sent through any BattlEye RCON client:
| Command | Description |
|---|---|
players |
List all connected players with their IDs, IPs, and GUIDs. |
kick <id> <reason> |
Kick a player with an optional reason message. |
ban <id> <minutes> <reason> |
Ban a player for a specified duration (0 = permanent). |
bans |
List all active bans. |
removeBan <ban_id> |
Remove a ban by its ID (from the bans list). |
say -1 <message> |
Send a global message to all players (-1 = all). |
say <id> <message> |
Send a private message to a specific player. |
loadBans |
Reload the ban list from file. |
writeBans |
Write current bans to the ban file. |
loadScripts |
Reload BattlEye filter scripts. |
loadEvents |
Reload BattlEye event scripts. |
#lock |
Lock the server (same as in-game command). |
#unlock |
Unlock the server. |
#shutdown |
Shut down the server. |
#restart |
Restart the current mission. |
#reassign |
Move all players to role selection. |
#missions |
Open mission selection. |
Server Logs
Arma 3 generates several log files that are essential for troubleshooting server issues, tracking player activity, and diagnosing BattlEye events.
| Log File | Location | Description |
|---|---|---|
| RPT Log | <profile>/*.rpt |
Main server log. Contains startup info, errors, script logs, and crash reports. New RPT created each server start. |
| Console Log | server_console.log |
Output defined by logFile in server.cfg. Contains console output including player connections. |
| BattlEye Logs | battleye/*.log |
BattlEye filter violations, kicks, and bans. Check these when players report false kicks. |
| Net Log | <profile>/net.log |
Network diagnostics (if -netlog launch parameter is used). |
Access logs through the File Manager in GPanel or via SFTP. The RPT log is the most important file for diagnosing crashes, mod issues, and script errors.
Related Articles
- Arma 3 Server Setup Guide — Initial server setup, server.cfg, difficulty settings, and performance tuning.
- Arma 3 Mod Installation Guide — Steam Workshop mods, SFTP upload, load order, and signature verification.
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Getting Started with Your New Server
Need Help?
Need help configuring admin access, BattlEye, or RCON on your Arma 3 server? Open a support ticket and our team will be happy to assist.
