Bans, kicks, and server allowlist

BattlEye sanctions, player kicks, server access, faction access records, and moderation logs.

Kick an online player

From Online, you can kick the current slot through RCON. The panel checks again that the verified GUID still belongs to that slot before sending the command, because slot numbers are reused. When a GUID can be mapped to a Steam ID, the kick is linked to the player's history. The permission is rcon.kick.

Temporary and permanent bans

The orange “Ban” button appears in Players and Details when the administrator has permission. The dialog offers preset or custom duration in minutes, or a permanent option with a red border. The server sends addBan GUID minutes reason to BattlEye and records the sanction in ac_bans; duration 0 means permanent. The panel prevents a second active panel ban for the same player. If the player is online and kick permission is present, it also attempts to remove that session.

A ban counts as active when applied to RCON, not revoked, and either permanent or ending in the future. php bin/battle-eye.php --loop checks expiry every five seconds, runs writeBans in BattlEye to clear expired entries, and marks the panel record Expired. If RCON is unavailable, it retries on the next cycle. Manual unbanning requires rcon.unban; deleting an active ban record requires that permission too.

Server allowlist

Server allowlist contains authorized GUIDs. When enabled, the worker maintains a BattlEye RCON session, listens for verified GUID events, and kicks any player absent from the list using the configured message. It periodically checks online players to recover from missed events after reconnection. The panel refuses to enable an empty allowlist or remove its last authorized entry while enabled.

RCON limit: a player can reach slot selection before their GUID is verified. Without a mission or server-side integration, blocking them before that screen cannot be guaranteed.

Faction access records in profiles

Player profiles also include civilian, police, and medic access flags in ac_whitelist. These are administrative records; enforcing them inside an Altis Life mission requires a mission adapter. They are separate from the RCON server allowlist.

Logs and auditing

Logs can be filtered by action, module, administrator, target, outcome, and dates. Records include actor, target, previous and new values, an optional reason, IP, request ID, and outcome. Kicks and bans generate RCON records. Deleting one entry and clearing the list have different permissions; maintenance is separately recorded in ac_log_maintenance.