Root-Ping - Detailed Connection Analytics

Root-Ping — Detailed Connection Analytics owns /ping on Paper/Spigot. Today it shows live latency + server load in chat and writes rich connection samples to MySQL. That sample stream is the foundation for a full interactive analytics surface on the roadmap.

What you get now

• /ping (alias /latency) — player ping + TPS / MSPT / online / heap in one shot
• Periodic background samples while online (default every 5 minutes) so quality is measured over a session, not only when someone types a command
• Detailed MySQL rows via Root-Core DB settings (root_ping_samples) — ping, IP, protocol, client brand, locale, view distance, virtual host, TPS/MSPT, heap, CPU, disk, host label, server id
• Multi-host labels — auto towny / claims / local (or override) so Claims vs Towny (or any labeled host) can be compared later
• Configurable chat messages — prefix, ping line, server line
• Root-Essentials aware — when Root-Ping is installed, Essentials leaves /ping alone

Roadmap — interactive analytics
Root-Ping is intentionally shipping the collector first. The MySQL schema is already shaped for dashboards, not just a one-line /ping.

Planned interactive analytics (web / developer portal style):

• Per-player latency timelines — ping over a session or across days; spikes vs steady play
• Host & region comparisons — Claims vs Towny (or your own host-labels); which entry hostname / virtual host correlates with worse RTT
• Server-load correlation — overlay player ping with TPS, MSPT, heap, and online count from the same sample row
• Client fingerprint views — protocol, brand, locale, view distance distributions (ops-friendly; privacy-aware)
• Filters & drill-down — by player, server id, host label, time range, trigger (COMMAND vs INTERVAL)
• Live / near-live ops panels — “who is lagging right now?” without digging through SQL by hand

Until that UI lands, you already have the hard part: continuous, structured samples you can query yourself or feed into your own BI tools. Interactive charts and filters will read the same tables — no re-instrumentation planned.

Commands
Command Description
/ping
Show your ping + current server load
/latency
Same as /ping
/ping reload
Reload config (staff)
Permissions

• rootping.use — use /ping (default: true)
• rootping.admin — /ping reload (default: op)

Installation

1. Install Root-Core first (shared config folder + MySQL settings)
2. Drop root-ping-*.jar into /plugins
3. Restart the server
4. Edit plugins/RootMC/root-ping.yml (created on first run)

Depends

• Root-Core (required) — database settings, server id, RootMC config folder
• Root-Essentials (soft) — avoids duplicate /ping ownership

Config highlights

• enabled — master switch
• interval-minutes — automatic sample period (default 5)
• server-id / host-label — optional overrides for analytics grouping
• messages.* — fully customizable chat lines ({ping}, {tps}, {mspt}, {online}, {max}, {heap})

Support
Site: https://rootmc.net/plugins/
Discord: https://discord.com/invite/yeQA4VkmRM
Test live: play.rootmc.net
Made for RootMC — Paper 1.21+ / Paper 26.x.