Troubleshooting

The plugin does not load

Read the first startup exception, not only the final “plugin disabled” line. Check the exact Minecraft version, Java runtime, active JAR and server platform. Remove duplicate old plugin JARs and perform a full restart. A public beta without Folia support must not be made compatible merely by editing its descriptor.

Unsupported future versions and missing native packet adapters require a compatible build, not ProtocolLib. Preserve the original log and report a redacted excerpt with the precise build.

No staff alerts appear

1. Check arionac.alerts on the staff account and use /alerts.
2. Check the detector’s ENABLED state and operative status.
3. Run /arionac check <player> to inspect bypass, server-authorized movement and pauses.
4. Check server tick health, join/teleport grace and connection reliability.
5. For proxy alerts, verify the bridge and alerts.ROUTE. For Discord, verify webhook configuration and channel access.

An unknown or unsupported evaluation is not converted into an alert. Silence alone is not proof that a cheat was detected or that a player was clean.

A legitimate player triggers a check

Keep automatic punishment disabled, preserve the relevant alert and reproduce the specific legitimate situation on a private server. Include game mode, effects, attributes, weapon, block geometry, latency and the plugins modifying the mechanic. Water against walls, stairs/slabs, entity pushing, teleports, explosions and custom launches need their actual context.

Inspect /arionac check, /arionac connection and /arionac risk. Disable the affected detector while investigating rather than resetting all settings. Ensure flight uses server allowFlight and custom movement is authorized before the launch. Do not use a blanket player bypass as a permanent integration fix.

The dashboard says offline

1. Verify web-telemetry.enabled: true and the exact HTTPS endpoint.
2. Check the connection code for mistakes, revocation or account expiry.
3. Check the Minecraft console for telemetry errors and the host’s outbound HTTPS connectivity.
4. Confirm that a single-server code is not reused for several instances.
5. For a network, give every service a distinct server identity.
6. Wait for a successful heartbeat; restarting the browser does not create one.

The online window accounts for the configured heartbeat interval and uses the website’s clock. Network services disappear from the ordinary list after 10 minutes without telemetry, then return with a valid heartbeat.

A dashboard action stays pending

Check that the game server is online and sending fresh telemetry. Verify Owner/Operator access and whether the check is INOP. An accepted check change must be saved by the plugin before the dashboard receives confirmation; inspect console errors and file permissions if it reports a save failure.

For bans, inspect the action’s status, local console and your actual ban plugin. “Accepted” or “forwarded” is not proof that an external ban database completed the action. Do not blindly repeat an uncertain command.

Ores are still visible

Verify the actual JAR’s startup privacy status, perform a full restart after changing packet-privacy, reconnect the client and run /arionac privacy <player>. Separate fully enclosed ores from ores with a legitimate cave sightline or states already disclosed earlier.

If the handler is stopped or missing, include its status and the exact server version in your report. ArionAC does not hide containers or entities. Receiving a masked ore packet does not add evidence or a VL.

Confidence, counters or prediction look unexpected

Confidence is model support rather than a calibrated probability. Evidence weights depend on the observation, correlation and context; they are not required to add exactly 1.0. Decay also changes totals between events.

Diagnostic snapshot prediction and guarded packet correction are different paths. A diagnostic match can coexist with missing authoritative input/world state, and an unknown result is not a pass or cheat verdict. Check your precise version pair and the live eligibility output before expecting correction.

Prepare a useful support report

Include the ArionAC version/build, server distribution and Minecraft version, Java version, client/protocol, affected semantic check, alert excerpt and exact reproduction steps. State whether the situation was legitimate or an intentional private cheat test, and list relevant custom mechanics.

Provide the smallest useful redacted configuration and log excerpt. Exclude tokens, passwords, webhook URLs and unrelated personal information. Join ArionAC Discord support if the guide does not resolve the issue.