Plan | Player Analytics

Plan (Player Analytics) collects gameplay data and displays it in a clear web page. You'll learn who was on the server and when, how long they played, how much total playtime they have, when they last joined, and whether they play regularly — as well as how the server is doing (load, memory, player count over time).

Data is collected in the background and requires nothing from players. After installation, the plugin starts handling the recording on its own, and you log in to the dashboard in your browser. The web runs directly in the plugin, so you don't need a second server or a database — just open the address and port in your browser.

It is most useful for decision-making: which players are active and which return, at what hours the server is full (and when it is empty instead), whether a new player left after five minutes or stayed. This comes in handy when planning events and when deciding what to add to the server.

The dashboard also includes a page with currently connected players, how long they have been playing, and a list of the most active players by time played. A public section that players can see can also be set up — it works well as a server loyalty leaderboard.

Security is important here: the plugin's web contains player names and server information. Run it so that no one from the internet can access it — ideally on an address only you know, or behind a login.

Data stays on your server (in the plugin's files or in your database). Nothing is sent to the plugin author.

1. Download Plan from modrinth.com/plugin/plan-player-analytics for your server version.
2. Upload the .jar to the plugins folder and restart the server.
3. Let the plugin run for a while — player data is collected continuously, and the overview fills up gradually.
4. In game, register an account on the plugin’s website (the plugin command will guide you, usually /plan s registrac) and remember the login credentials.
5. Find out the plugin website address and port (the default is usually 8804) and open it in a browser at your server’s address.
6. Log in and go through the overview: players, time played, activity over time, server status.
7. Set whether part of the overview should be public for players, or everything only for you.
8. Check that the website is not open to the internet if you don’t want it there — and if you do, secure it (long password, access only from selected addresses).
9. Set the data retention length so the database doesn’t grow endlessly (older records can be shortened).
10. Come back to the overview after a week — only then can you see who plays regularly and at what hours.

The plugin's web interface contains player names and server information. Don't leave it open to the internet without security — a long password and access restrictions are the minimum.
Data fills up gradually. On the first day you'll only see what managed to be collected; the real value of the overview comes after a week to a month.
Set how long old data should be retained. Without that, the database or files grow every month and no one reviews them.
The overview is great for decision-making: at what hours the server is alive, which players return and which left after a few minutes. Use it when you're dealing with something — not as a daily check.
If the overview shows fewer players than were actually on the server, verify that the plugin ran the whole time (after a restart, data is added from the start of the run).
The public part is motivating for players (a leaderboard of time played), but it publishes names and times. Make a conscious decision whether you want it.
Back up the plugin folder — it contains the collected data. Without a backup, the play history is irreversibly gone.