AjdnikovPanel

VelocityPaper1.21.xJava 25New · 1.2.0

Network-wide monitoring with a live web dashboard, lag analysis written in plain words, player inspection, alerts and a Discord bot. The hub runs inside your proxy or server — no separate backend, database server or Docker — and the dashboard opens from your AnziLock account, so there is no dashboard port, password or address to set up.

Read the manual Open your networks Ask in Discord

What it talks to

Ports

History lives in a local SQLite file inside the hub. The dashboard reaches the hub through an outgoing, licence-checked relay to AnziLock. Discord and Vault are optional.

Velocity 3.4+
SQLite (built in)
AnziLock relay
Discord
Vault

What you get

Live overview

The proxy and its backends drawn as a topology, plus standalone servers
TPS, tick time, memory, CPU, players and routing, updated as it happens
Players and uptime over 24 hours, 7 or 30 days

Lag analysis in plain words

"Hoppers are slowing the server: 713 hoppers near Steve at 200, 64, -110"
Confirmed causes are measured by sampling slow ticks; possible causes come from counts
Scans are time-sliced, so a scan never causes lag itself

Player inspection

Health, effects, balance, location and session history
Inventory and ender chest drawn with the game's real item icons
Logged sign edits and crafting, and the player's dupe flags

Alerts

Servers going down and coming back up
Lag starting, changing cause and ending
Dupe flags from a simple heuristic that flags and never punishes

Discord, built in

Webhooks with per-channel event and server filters and role pings
A bot with /status, /server, /players, /player, /lag, /scan and /alerts
Runs inside the hub — no separate bot host

Sharing & support access

Let your own staff in as Viewers or Admins
Give AnziLock support temporary read-only access, from 1 hour to 7 days
Every visit and change is written to an audit log

Three jars, one hub

Jar	Install on
`Panel-Velocity-1.2.0.jar`	The Velocity proxy. Hosts the hub and the Discord bot. Recommended for networks.
`Panel-Paper-1.2.0.jar`	One Paper server, for setups without a proxy.
`Panel-Agent-1.2.0.jar`	Every Paper server you want to monitor.

Install one hub. Agents need no licence key; the hub needs one, and an outgoing HTTPS connection to AnziLock.

Limits, stated up front

The dashboard needs AnziLock. While it is unreachable the hub keeps collecting, storing and sending Discord alerts, but nobody can open the dashboard.
The inventory viewer is read-only. Resource-pack item models and player-head skins show their vanilla look.
The dupe detector is a simple heuristic: it flags players and never punishes.
Folia is not supported.

Quick start

Install the hub

Drop the hub jar into the proxy's plugins/ folder, start it once, set licenseKey in config.properties and restart.

Open Networks

Sign in at the licence portal with Discord and open Networks. Your network appears a few seconds after the hub starts.

Register servers

Under Settings → Servers, register each server and copy its API key.

Install agents

Drop the agent on each server, paste server-id, api-key and hub-url, and restart. It appears within seconds.

Questions before you commit?

Support, licence keys, bug reports and feature requests all run through the Discord. Ask anything about AjdnikovPanel there — including whether it fits the network you already run.

Already licensed? Your networks live in the licence portal under Networks — sign in there with Discord, or claim a key with /claim in the Discord.

Join the Discord Back to all plugins