Minecraft Community Network
Three servers behind one proxy, with monitoring.
- Role
- Server administrator
- Year
- 2023
- Status
- Live
- Tech stack
- JavaPaperMCVelocityLuckPermsGrafana
$ resource:start core
[ok] 42 resources loaded in 1.2s
[ok] mysql pool ready (12/40)
$ tick 60 · cpu 18% · mem 412mb
This preview is an interface illustration, not a screenshot of customer data.
Problem
Each mode originally had its own server with different rules, so players had to remember several addresses and data often fell out of sync.
Approach
I unified everything under Velocity, standardised permissions with LuckPerms, and stored player data centrally. I also added Prometheus and Grafana for TPS, memory usage, and player counts per server, so problems show up before players complain.
Key features
- One address for three game modes.
- Centralised permissions with LuckPerms.
- TPS and memory dashboard per server.
- Daily automatic backups with seven-day rotation.
Results
- 01
Unplanned downtime decreased because issues were caught from the TPS graph.
- 02
New players no longer need to learn three different addresses.
- 03
Backups proved their worth when one world broke after a plugin update.
Notes
Observability feels excessive until something breaks. After that, the TPS graph is the first thing I open.
Facing a similar challenge?
I am happy to discuss technical problems, even before there is a budget or a full specification.