Dashboard

Networks and staff access

Connect several Minecraft servers using one network code, assign staff roles and configure shared violation storage.

Add a network

In dashboard Settings, choose Add Server, then Add network.
Enter the network name.
Save its connection code.
Use that same code in web-telemetry.server-token on every intended backend server.
Give each backend a distinct persistent identity and a useful display name.

Servers join that dashboard network when they send authenticated telemetry. The code grants a server connection; it does not create website accounts or grant staff access.

web-telemetry:
  enabled: true
  endpoint: "https://arionac.com/api/plugin/telemetry"
  server-token: "YOUR_NETWORK_CONNECTION_CODE"
  server-name: "Survival-1"
  server-id: "survival-1"
  interval-seconds: 10

Server identity and dynamic services

Use a unique web-telemetry.server-id for each persistent service, or provide ARIONAC_SERVER_ID in its environment. Do not copy one ID across all CloudNet or Pterodactyl instances. If left blank, ArionAC derives an identity from the installation identity and host/listening port for network connections. A display name alone is not a safe identity.

Network servers with no heartbeat for more than 10 minutes are hidden from the ordinary network server list. Their next valid heartbeat makes them appear again. This reduces clutter; it is different from the shorter online/offline freshness indicator and is not a ban or a deletion of the service.

Give staff access

Ask staff to register their own dashboard accounts first. As the workspace owner, open the server or network access settings, enter the account’s email and assign a role. A network membership applies to its linked servers.

Role	Access
Owner	Owns the workspace; manages members and connection codes, changes checks and performs allowed bans, including custom commands.
Operator	Reads data, changes operative checks and performs allowed default ban actions. Does not manage ownership, connection codes or owner-only custom commands.
Viewer	Reads the authorized workspace without changing checks or issuing bans.

Access is checked on the backend for each action. Removing access also prevents undispatched commands from being executed. Global website Admin/Staff roles are separate from a server or network’s Owner/Operator/Viewer access. Do not share the owner’s password or server connection code with staff.

Share violation storage separately

A network dashboard code groups servers visually. It does not connect their local violation databases. For servers rebuilt from templates or for persistent cross-server violation storage, configure MySQL/MariaDB separately on the game servers.

storage:
  TYPE: MYSQL
  HOST: "DATABASE_HOST"
  PORT: 3306
  DATABASE: "arionac"
  USER: "DATABASE_USER"
  PASSWORD: "SET_ON_THE_SERVER"
  USE-SSL: true
  NETWORK-ID: "my-network"

Use the same database and NETWORK-ID for services that should share stored violations. Use a restricted database account and the TLS mode supported by the database host. The default TYPE: FILE stores plugins/ArionAC/violations.yml. When database storage is unavailable, ArionAC reports the problem and can continue on file storage; that fallback does not establish cross-server persistence.

Stored historical VL is not automatically trusted live evidence. A shared database is not a substitute for reliable packet state or a current session’s risk assessment.

Proxy installation

Install ArionAC on each backend game server. Use the matching ArionACBungee.jar on BungeeCord/Waterfall or ArionACVelocity.jar on Velocity when forwarding staff alerts or punishment commands. Configure authenticated forwarding and preserve the bridge secret across backend and proxy configuration.

See proxy routing for command behavior. CloudNet server lifecycle, dashboard grouping, database persistence and proxy command forwarding are distinct features.