Skip to content
ArionAC Dashboard

Detection

Check reference

Understand ArionAC movement, combat, packet and interaction checks, including experimental and diagnostic restrictions.

Check identities and switches

Checks use semantic names in alerts, configuration, logs and dashboard controls. There is one Placement.Scaffold detector. Use checks.<identity>.ENABLED to change a switch, or toggle an operative check with the dashboard or /arionac disablecheck <identity>.

The tables describe detector intent and the keys exposed by the current configuration. They are not a claim that every situation, version or cheat setting has passed live acceptance. The loaded build and its runtime eligibility determine what can be evaluated.

PUNISH-VL is a deprecated compatibility setting; it does not authorize per-check automatic bans. Where present, SETBACK and SETBACK-MIN-VL control guarded legacy movement corrections, not the global evidence punishment policy.

Combat checks

IdentityPurposeOther configuration keys
Combat.ReachAttack range against possible target geometry; server-granted weapon range matters.MAX-REACH, CANCEL, SPEAR-EXTRA-REACH
Combat.AttackAnimationAttack/animation sequencing.MAX-SWING-AGE-MS
Combat.AimGeometryCoarse attack orientation geometry.MAX-ANGLE
Combat.TargetSwitchINOP. Disabled and cannot be made operative by a toggle.SWITCH-MS (legacy; no operational detection)
Combat.HitboxAttack geometry relative to the possible target hitbox.HITBOX-EXPANSION
Combat.CriticalStateImpossible critical-attack state.—
Combat.RaycastPacket-time full-block line-of-sight obstruction. Incomplete history is inconclusive.CANCEL
Combat.BowChargeShortened full bow draws with item context.MIN-FULL-DRAW-MS

combat-simulation.MODE: SHADOW forwards evaluated attacks. The packet-time evaluator only rejects a conclusive reach/miss in CANCEL mode with the necessary state. Detector-specific cancellation settings still have their own guards.

Movement checks

IdentityPurposeOther configuration keys
Movement.VelocityAcknowledged impulse-response observations. Alerts/evidence and permitted physical restoration are separate; no automatic sanction from this detector.—
Movement.GroundStateRepeated ground claims unsupported by the surrounding geometry.GROUND-REACH, BUFFER
Movement.HoverRepeated hover inconsistent with the available movement context.MAX-AIR-TICKS
Movement.AscentPowered upward motion beyond the modeled legitimate options.MAX-RISE-PER-TICK
Movement.GravityFall progression outside the available gravity context.MIN-AIR-TICKS, LENIENCY
Movement.PredictionApplied packet-model correction observations; supporting evidence, separate from automatic punishment.MIN-VERTICAL-OFFSET, MIN-HORIZONTAL-OFFSET, BUFFER
Movement.GroundSpeedGround speed with attributes, momentum and surface context.BASE-SPEED, TOLERANCE, BUFFER, AVG-SPEED
Movement.AirSpeedAirborne horizontal speed context.MAX-AIR-SPEED
Movement.WaterSurfaceTravel on a liquid surface without a legitimate movement explanation.MIN-SPEED, BUFFER
Movement.StepStep-up height with server attribute context.MIN-STEP, MAX-STEP
Movement.FallDamageUnambiguous missing fall damage; server-cancelled damage remains authorized.MIN-FALL-BLOCKS, APPLY-DAMAGE
Movement.WallClimbUnsupported wall ascent.MIN-AIR-TICKS, BUFFER
Movement.ElytraGlide energy and climb context, including legitimate boosts.MAX-NET-GAIN, MAX-CLIMB-BUDGET
Movement.VehicleUnsupported vehicle movement patterns.BUFFER
Movement.JumpHeightJump height with the available effect/attribute context.MAX-RISE
Movement.JumpImpulseUnsupported upward jump impulse.MAX-RISE-PER-TICK, BUFFER
Movement.JumpDistanceUnexplained jump distance.MAX-DISTANCE
Movement.AirDirectionExperimental; off by default. Air-direction patterns alone are not proof.MAX-ANGLE, MIN-SPEED
Movement.WebMovement inconsistent with applicable web slowdown.MAX-SPEED, MAX-RISE
Movement.ClimbSpeedClimbable-block speed.MAX-UP, MAX-DOWN
Movement.CollisionUnsupported movement through collision geometry.SETBACK-MIN-VL
Movement.SprintStateSprinting state/orientation context.MAX-ANGLE

Authoritative movement requires sufficient state and a permitted version pair. Creative, Spectator, server-authorized flight and explicit custom movement allowances must not be interpreted as unauthorized flight. See custom mechanics.

Packet and connection checks

IdentityPurposeOther configuration keys
Packet.TickRateSustained client timing excess, with synchronization and server-health context.MAX-BALANCE-MS, BUFFER
Packet.MotionDataInvalid or non-finite movement data.—
Packet.HeldSlotInvalid held-slot values.—
Packet.InteractionDataInvalid interaction packet data.—
Packet.ActionDataInvalid action packet data.—
Connection.StallsExperimental; off by default. Communication gaps can have legitimate network causes.MAX-GAP-MS
Connection.AcknowledgementsDiagnostic compatibility entry; off by default, does not generate cheat observations.MAX-DIVERGENCE-MS (legacy)

Connection Safety is a separate subsystem. A stable high ping or a burst of delayed TCP packets is not by itself a ban reason.

Interaction and placement checks

IdentityPurposeOther configuration keys
Interaction.BreakSpeedBreaking faster than permitted, while accounting for tools and effects; instant-break blocks are excluded.MAX-BREAKS-PER-SECOND, MIN-DIG-MS, SPEED-FACTOR
Interaction.ConsumeTimeShortened applicable item-consumption timing. Items with distinct timing are excluded from the generic food test.MIN-CONSUME-INTERVAL-MS, MIN-EAT-DURATION-MS
Placement.RateSustained excess packet-use rate per acknowledged client tick. Supporting evidence; no standalone cancellation or punishment.WINDOW-CLIENT-TICKS, EXCESS-USES-PER-CLIENT-TICK
Placement.ScaffoldRepeated impossible full-cube placement-face geometry. Legitimate bridging is not automatically a scaffold verdict.BUFFER

Availability and tuning

Default-disabled experimental checks are not equivalent to fully validated detections. INOP checks cannot run. Diagnostic entries can expose state without generating evidence. Removed rotation/clicking heuristics, AuraBait, ShieldAttack, Tower, Improbable and the former cloud detector are not part of the current advertised detection set.

The dashboard’s separate Movement.LiveCorrections control writes prediction.LIVE-CORRECTIONS. It controls permitted physical correction, not a separate detector or proof that a correction is available on every version.

AntiXRay protects ore information and is listed separately in the dashboard; it is not a violation-generating detector. AntiESP, entity hiding and container hiding are not provided.

If a detector is noisy, capture the legitimate situation and inspect /arionac check <player> and /arionac risk <player>. Disable only the affected check while investigating. Do not lower every threshold to pursue an arbitrary check count.