Integrations/Velocity
Running Velocity? Every backend gets its own dashboard.
Install the clan.me plugin on each Paper or Spigot backend behind your Velocity proxy, lobby, survival, minigames, whatever you run. clan.me detects the proxy automatically and rolls every backend into one public page and one dashboard, with alerts that still name the exact backend that needs attention.
How clan.me detects Velocity
No config on your end. It just knows.
Reads paper-global.yml automatically
The plugin checks proxies.velocity.enabled on startup. If it's true, the backend reports behind_proxy in its heartbeat, no config on your end.
Modern forwarding, already secure
Velocity's modern forwarding pairs a shared forwarding.secret between velocity.toml and each backend's paper-global.yml. clan.me doesn't touch that secret, it only reads whether forwarding is on.
Every backend rolls up
Add each backend under Settings → Network on your lobby's dashboard. They stay private and roll into one public page and one set of charts.
In your dashboard
One aggregate headline, every backend broken out
Players online across network
42
Lobby, survival, and creative, each with its own status dot, player count, and TPS.
Setup
One backend at a time
Add your lobby first
Sign in and add your lobby (or hub) server the normal way. This becomes your network's root, the server your public page and dashboard live on.
Add each backend
From Settings → Network, name each backend, survival, creative, skyblock. clan.me generates a token for it immediately.
Install and restart
Drop the same clan.me plugin JAR into each backend's plugins/ folder, paste its own token into config.yml, restart.
The proxy itself needs nothing installed. Velocity isn't a Bukkit plugin, so clan.me only ever runs on the Paper or Spigot backends behind it.
Common questions
Does clan.me need anything installed on Velocity itself?
No. Install the clan.me plugin only on your Paper or Spigot backends. Velocity needs nothing installed, clan.me detects the proxy from each backend's own paper-global.yml.
Do I need to configure forwarding.secret for clan.me?
No. That secret is between Velocity and your backends for player-identity forwarding, clan.me never reads or needs it. clan.me only checks whether proxies.velocity.enabled is true.
Does legacy forwarding work the same as modern forwarding?
For clan.me's detection, yes, either way paper-global.yml reports proxies.velocity.enabled: true. Modern forwarding is what Velocity recommends today regardless of clan.me.
Do I need a separate token for each backend?
Yes. Each backend gets its own token, derived from a shared secret unique to your network. If one leaks, rotate the shared secret from Settings → Network and every backend's token regenerates in one action.
Running BungeeCord instead? See the BungeeCord integration page. See all integrations →
One dashboard for your whole network.
Install the plugin on your lobby in 60 seconds, then add each backend from Settings → Network.