Skip to content
ArionAC Dashboard

Server operations

Configuration

Configure ArionAC checks, alerts, protection, storage, telemetry and optional features with the actual YAML settings.

Edit the configuration

The active configuration is plugins/ArionAC/config.yml. YAML indentation and key capitalization matter. Back up the file before editing. Run /arionac reload after ordinary configuration changes; use a full restart for packet privacy or a new plugin build. Do not edit CONFIG-VERSION.

Most detector settings live under checks.<Domain>.<Meaning>. The check reference lists identities and tuning keys. Configuration values are operational limits, not a guarantee of zero false positives.

LANGUAGE: en

punishment:
  ENABLED: false

web-telemetry:
  enabled: false

checks:
  Movement:
    Ascent:
      ENABLED: true
      SETBACK: true

Language, alerts and logs

SettingDefaultPurpose
LANGUAGEenAvailable languages: en, de, es, fr, it, ja, pt. Changing the language regenerates messages.yml with a backup; custom edits are otherwise preserved.
alerts.AUTO-ENABLEtrueEnable alerts automatically for staff who have arionac.alerts.
alerts.COOLDOWN-MS1500Minimum spacing for repeated alerts from the same check and player.
alerts.CONSOLEtrueAlso write alerts to the server console.
alerts.ROUTELOCALLOCAL, BUNGEE or BOTH. Network routing requires the appropriate proxy bridge. BOTH can duplicate alerts for local staff.
alerts.BUNGEE-MIN-VL0Minimum VL for forwarding an alert to the proxy network.
logging.FILEtrueKeep local violation logs under plugins/ArionAC/logs/.
update.NOTIFY-IN-GAMEfalseAlso tell administrators about a newer version in chat. The startup console notice is independent.
freeze.ALLOWED-COMMANDSmsg, tell, r, reply, helpopCommands a frozen player may still use, without a leading slash.
internal.RESEARCH-MODEfalseExpose local recording commands. Leave off unless collecting a specific diagnostic recording.

Prediction and combat model settings

SettingDefaultPurpose
prediction.ENABLEDtrueEnable the diagnostic prediction path.
prediction.COLLECT-FRAMESfalseCollect detailed server/geometry frames. Adds work per movement; enable only for a specific diagnostic need.
prediction.AUTHORITYfalseReserved legacy setting. It does not authorize punishment from server-event snapshot prediction.
prediction.LIVE-CORRECTIONStrueOpt in to guarded physical corrections only where the build, protocol and complete state permit them.
prediction.TELEPORT-GRACE-MS150Minimum settling interval for fully acknowledged packet prediction; missing acknowledgements still block correction.
combat-simulation.ENABLEDtrueEnable packet-time combat evaluation.
combat-simulation.MODESHADOWSHADOW records the result and forwards attacks. CANCEL can reject only a conclusive out-of-reach or missed attack.
combat-simulation.MAX-ENTITIES / HISTORY-STATES256 / 64Bounds for tracked entities and their state history.
combat-simulation.MAX-REWIND-MS / MAX-LATENCY-RISE-MS400 / 250Bounds for possible client-visible history and latency growth.
combat-simulation.COMBAT-FENCE-TICKS / IDLE-FENCE-TICKS2 / 40Synchronization-fence scheduling during combat and idle periods.
combat-simulation.MAX-OUTSTANDING-FENCES32Bound on unanswered synchronization fences.
combat-simulation.COMBAT-WINDOW-MS5000Combat activity window.
combat-simulation.MULTI-TARGET-LIMIT2Allowed distinct targets inside one movement boundary before extreme burst handling.
combat-simulation.RECORDfalseWrite bounded combat-result diagnostics locally.

Keep SHADOW when evaluating behavior on a new server. An inconclusive combat result always forwards the attack. Increasing rewind bounds is not a safe way to compensate for arbitrary lag.

Protection and grace periods

These settings limit legacy movement/combat decisions when the server or player state is uncertain. A high-ping threshold pauses affected checks; it is not a ping-based kick rule. Packet-model corrections have additional independent requirements.

Key under protectionDefaultPurpose
MIN-TPS / MAX-PING16.0 / 1000Pause affected movement/combat checks below the TPS floor or above the ping threshold.
TICK-GATEtrueRespond to degraded or stalled server ticks, beyond the smoothed TPS average.
TICK-DEGRADED-MS / TICK-STALL-MS55 / 150Tick duration thresholds in milliseconds.
JOIN-GRACE-MS / TELEPORT-GRACE-MS3000 / 1500Settling time after join or an ordinary teleport.
SETBACK-GRACE-MS100Short settling time after ArionAC’s own correction.
VELOCITY-GRACE-MS / BLAST-GRACE-MS1500 / 3000Legacy grace after impulses or explosion/wind-charge launches.
GLIDE-GRACE-MS / CONTAINER-GRACE-MS6000 / 2000Grace after gliding or container interactions.
ATTRIBUTE-GRACE-MS / LIQUID-GRACE-MS1500 / 2000Grace after attribute changes or liquid contact. WaterSurface has separate handling.
STEP-GRACE-MS / SPECIAL-BLOCK-GRACE-MS1000 / 1500Grace for stairs/slabs and special movement blocks.
COLLISION-RESCUEtrueAllow guarded extraction from a block when the collision check is enabled; this rescue adds no violation.
SETBACK-MIN-VL / SETBACK-MAX-DISTANCE3 / 16.0Default legacy correction threshold and maximum distance. Individual checks may override the threshold.
CANCEL-CHEATStrueAllow prevention-capable checks to cancel an action after their required evidence; not a universal cancellation switch.

Mitigation

Mitigation can reduce an eligible player’s advantage without issuing a ban. It is a separate policy from prediction corrections and punishment. Review it on a staging server, especially when other plugins modify combat or speed.

Key under mitigationDefault
ENABLEDtrue
LEVEL-1-VL / LEVEL-2-VL / LEVEL-3-VL12 / 22 / 35
DAMAGE-MULTIPLIER-1 / -2 / -30.85 / 0.60 / 0.35
SPEED-MULTIPLIER-1 / -2 / -31.00 / 0.90 / 0.80
KNOCKBACK-TAKEN-MULTIPLIER1.25

Feature-specific settings

The remaining configuration groups have dedicated guides: