Not wired
Everything below is sample data. This build has no API behind it — the panel deployment reads real nodes and servers from Pterodactyl. Player counts are the one thing neither build can show: Pterodactyl knows a container is running, not whether anyone is on it, which needs a Server List Ping probe.
Game servers
Player counts come from the game protocol, not Pterodactyl — a running container says nothing about who is actually connected. Start, stop, console and files live in Pterodactyl; this is the view it cannot give you.
{{ g.stLabel }}
{{ g.name }}
{{ g.game }} · :{{ g.port }}
CRASH LOOP · 3 restarts in the last hour · exit 137 (OOM)
{{ g.players }}
/ {{ g.maxPlayers }}
players
{{ g.uptime }}
Mem
{{ g.mem }}
CPU
{{ g.cpu }}
node02
plannedHP EliteDesk 705 G4 · rack build
Second node lands with the rack build. Wings dials out on first boot; servers migrate here to relieve node01.
Not rebuilt here: files, schedules, eggs, subusers, databases — open Pterodactyl for those. This screen exists for what its API can’t see: real players, crash patterns, node headroom.