BattlEye + RCON

BattlEye is Arma 3's anti-cheat layer. It also doubles as the server's RCON system — admin tools and dashboards talk to your server through BattlEye's RCON port.

Enabling

In server.cfg:

BattlEye = 1;

A /data/arma3/battleye/ folder gets created on first start with the default filter set.

Setting the RCON password

/data/arma3/battleye/BEServer_x64.cfg (or BEServer.cfg on 32-bit):

RConPassword <your-rcon-password>
RConPort 2306
RConIP 0.0.0.0
MaxPing 250

Restart for changes to apply.

Connecting an RCON client

Tools like BERCon, Arma Server Manager, or any BattlEye-compatible dashboard connect with:

• Host: your server IP
• Port: the RConPort from above (default 2306, UDP)
• Password: your RConPassword

Useful for moderation when you're not in-game.

Common BattlEye filters

The default filters in /data/arma3/battleye/ are aggressive and will flag legitimate mods. The main culprits:

• setdamage.txt — flags scripts setting unit damage; ACE medical triggers this
• setvariable.txt — flags setVariable calls; many mods use this for persistence
• setpos.txt — flags teleport scripts; admin tools trip it
• addmagazinecargo.txt — virtual arsenal trips it
• createvehicle.txt — vehicle spawn scripts

Each filter file has a numeric prefix (5, 6, 7) controlling what BattlEye does on match: 1=log only, 5=kick. Edit per- line as needed.

Whitelist-by-content-hash

For specific values you trust (e.g. ACE medical states), append !"value" to the line — that exempts that exact value from the filter.

Disabling for testing

If you're debugging and want to confirm BattlEye is the culprit, temporarily set BattlEye = 0; in server.cfg and restart. Never leave it off in production — kicks happen for a reason.

Player-side BattlEye

Players need BattlEye installed (the Arma 3 launcher offers it automatically; some Linux + cracked clients lack it). Connections from clients without BattlEye get refused if your server has it enabled.

RCON via BEC (BattlEye Extended Controls)

BEC is a long-running RCON automation tool. It connects via the same RCON port and can:

• Schedule restarts with player warnings
• Auto-respond to chat commands
• Track player join/leave
• Auto-ban on rule violations

Set it up on a small VPS (not the game server box) — BEC connects remotely, monitors, and acts.