Analytics for Minecraft BungeeCord and Folia servers
MCAnalytics now runs on a BungeeCord or Waterfall proxy as well as Velocity, and on Folia as well as Paper. On BungeeCord the connector reads the address a player typed, records one session from join to quit across every server switch, and reports votes, custom events and a heartbeat. On Folia there is no separate jar: the Paper loader detects Folia and does every read of a player or chunk on the thread that owns it. Both are on every plan, the free one included.
How it works
Put the loader on the proxy
Download the BungeeCord loader from the setup panel, put it in the proxy plugins folder, and start the proxy once. It needs BungeeCord or Waterfall on the 1.20 API or newer, and Java 17.
Pair it from the console
In Settings, Servers, pick BungeeCord and press Get pairing code. Type mca pair and the code into the proxy console. No restart is needed.
Keep backends in backend mode
On each Paper backend, keep settings.bungeecord: true in spigot.yml so sessions stay with the proxy. Give each backend its BungeeCord name.
On Folia, install the Paper loader
Install and pair it exactly as on Paper. The startup line in the console says Folia, so you can see which path is in use.
What you see on the dashboard
Join address on BungeeCord
Read from the handshake and cleaned up the same way as on Velocity, so a player's first join address is kept whichever proxy they used.
Sessions and routes
One session per connection to the proxy. Every server a player visits is added to their route, which feeds the Session paths card.
Health on Folia
Folia has no single TPS or MSPT, so Health shows Not available for those numbers instead of a made up value.
Votes and events
With NuVotifier on the proxy, each vote goes out with the voter's UUID when the proxy knows the name. Other plugins can call MCAnalytics.track.
Limits to know
Lag profiling needs one tick to measure, so it stays off on Folia. Folia sends no quit events at shutdown, so the connector closes every open session itself.
The nLogin premium hook is Velocity only. A premium player checked by a login plugin on an offline mode BungeeCord proxy gets their Mojang account added only when Mojang's signed skin data names them.
Questions
Does it run on Waterfall?
Yes. BungeeCord and Waterfall share one loader, on the 1.20 API or newer.
Is there a separate jar for Folia?
No. The Paper loader and connector look for Folia's region server class at startup, and schedule all work on Folia's own schedulers when it is there.
Do these cost extra?
No. BungeeCord and Folia support is on every plan, the free plan included.
Can I run a BungeeCord and a Velocity proxy in one network?
Yes. They add up in Online now the same way two Velocity proxies do, and a player on either is one player.
Read the docs
- BungeeCord and Waterfall setupInstall the connector on a BungeeCord or Waterfall proxy. It reads the join address and owns sessions, the same as on Velocity.
- Folia supportFolia runs the same Paper loader and connector. Every read of the world happens on the thread that owns it.
- Several proxies and regionsRun the connector on more than one Velocity or BungeeCord proxy, in one region or several, and still count every player once.