Connect the dashboard

Create your account on the website

Register at arionac.com/register, then sign in at the dashboard login. If registration is disabled by the website operator, contact support. The in-game /arionac dashboard command gives the website link; it does not create an account or issue a password.

Starting ArionAC does not automatically create a dashboard. Telemetry is disabled until the server owner deliberately enables it and supplies a valid connection code.

Add a single server

1. Open Settings in the dashboard and choose Add Server.
2. Select Add single server and give it a recognizable name.
3. Save the connection code shown after creation. Treat it like a password.
4. Copy the code into the server’s web-telemetry.server-token, enable telemetry and set the HTTPS endpoint.
5. Reload ArionAC or restart the server, then wait for a fresh heartbeat.

web-telemetry:
  enabled: true
  endpoint: "https://arionac.com/api/plugin/telemetry"
  server-token: "YOUR_CONNECTION_CODE"
  server-name: "Survival"
  server-id: ""
  interval-seconds: 10
  custom-commands: true

A single-server code binds to one server identity. Reusing it across several servers is rejected; create a network instead. The dashboard connection does not require entering website database credentials into the game plugin.

Checks and live data

The dashboard shows the selected server’s players, detections, evidence and physics diagnostics. An online indicator comes from website-received heartbeats and their configured interval. It does not merely inspect whether the Minecraft process exists.

With Owner or Operator access, you can request a check change. The plugin receives it with telemetry, validates the request, applies it and saves the accepted setting to config.yml. The dashboard distinguishes the requested state from the reported state. Wait for the plugin acknowledgement before assuming it changed.

Movement.Prediction controls its detector; Movement.LiveCorrections independently controls prediction.LIVE-CORRECTIONS. Enabling corrections does not bypass version, geometry, acknowledgement or synchronization restrictions.

INOP checks remain blocked. An offline server or stale check list cannot provide immediate confirmation. A save failure is reported rather than displayed as success.

Direct bans and ban waves are available according to workspace access and server capabilities. See the punishment guide.

Connection codes and account lifetime

Only the owner manages connection codes. Revoke a leaked code or generate a replacement in the dashboard, then update the connected server configurations. Network codes must be managed on the network, not on each automatically linked server.

All accounts expire after 30 days without dashboard use, including Admin and Staff. Automatic telemetry does not extend this period. Expiration removes the account and its owned server/network links and associated telemetry; connection codes stop working. Preserve separate operational backups and sign in regularly if you want to keep the workspace.