Server operations

Bans and ban waves

Configure automatic punishment, manual dashboard bans, custom commands, ban waves and proxy routing in ArionAC.

Automatic punishment is opt-in

ArionAC uses your existing ban system through a console command. It does not keep a second independent ban list. Automatic punishment defaults to disabled. Before enabling it, review legitimate gameplay, integrations, the accepted evidence and whether your actual ban command works.

punishment:
  ENABLED: false
  COMMAND: "ban %player% Unfair Advantage [Arion: %check%]"
  BROADCAST: true
  BUNGEE: auto
  BUNGEE-SECRET: ""

ENABLED allows the global punishment policy; it does not make every alert punishable. Per-check PUNISH-VL and PUNISH-COMMAND are deprecated compatibility values. Supporting or incomplete observations cannot bypass central eligibility.

Configured command placeholders

Placeholder in punishment.COMMAND	Meaning
%player%	Player name
%uuid%	Player UUID
%check%	Semantic check identity associated with the action
%vl%	Total live evidence at punishment time
%evidence%	Live evidence
%confidence%	Labelled support score
%risk%	Risk index

# Example for an installed ban plugin that supports this syntax:
punishment:
  COMMAND: "ban %player% 30d Unfair Advantage [Arion: %check%]"

Command syntax depends on your ban plugin. Test it with an account you control. BROADCAST controls the configured punishment announcement in messages.yml.

Manual dashboard bans

Select a reported player and choose a direct ban or add them to Ban Wave. Default mode uses the game server’s configured punishment.COMMAND. Manual staff actions are separate from automatic evidence eligibility; disabling automatic punishment does not itself remove authorized manual bans.

Owner and Operator can use allowed default actions. Custom commands require Owner access and web-telemetry.custom-commands: true. Set this key to false if dashboard staff should only use the configured default command.

ban %player% 7d Unfair Advantage

A custom dashboard command must contain %player%. Only that placeholder is accepted in the custom field. Enter one command, with no newlines or control characters. A custom command executes as server console and should be reviewed accordingly.

Ban waves and action status

Review the queued players and commands, then execute the selected wave. Up to 100 active ban actions are allowed per server, and a player cannot have two active actions on the same server. Queued entries can be removed before execution. Executing a wave dispatches its entries to that server; it is not an atomic transaction across several independent servers.

Status	Meaning
Queued	Saved for review; not sent for execution.
Ready / dispatched	Awaiting delivery, or sent to the server and awaiting its receipt.
Accepted	The plugin accepted command dispatch. Check the external ban system for the actual resulting ban.
Forwarded	Sent to the proxy bridge; not a receipt proving the proxy ban completed.
Failed	Validation or execution failed; inspect the reported reason.
Uncertain	No trustworthy completion receipt. Check the server/ban system before manually repeating the action.
Cancelled	Removed from the queue before dispatch.

Offline servers cannot execute an immediate action. Requests and receipts are scoped to the server and account permissions. A missing receipt is not blindly retried: otherwise an ambiguous command could execute twice.

Proxy command routing

punishment.BUNGEE accepts auto, true or false. Auto detects supported proxy-forwarding configuration; true always forwards to the proxy; false executes locally on the backend console.

Forwarding requires the appropriate ArionAC proxy bridge. BUNGEE-SECRET must match the bridge’s configuration when used. The bridge does not acknowledge the external ban plugin’s completed ban. Failed forwarding does not fall back to a local ban. Verify the intended target before enabling this on a network.

Network staff alerts use the separate alerts.ROUTE setting. Alert routing does not choose where punishment commands execute.