Tracking Player Activity with the WhoWasOn Plugin
Running a Minecraft server comes with plenty of questions about your community. Who stopped by yesterday? When did a specific player last log in? How often does someone actually join? Vanilla Minecraft doesn't offer a clean way to answer these, but a lightweight Bukkit plugin called WhoWasOn steps in to fill that gap. Created by a self-described Java beginner over a few days, this plugin is small, straightforward, and designed to work on almost any modern version of Bukkit, Spigot, or Paper. It won't bog down your server with bloat, and it answers the most common player-history questions without requiring a database or complicated configuration.
What WhoWasOn Actually Does
WhoWasOn logs join and leave events for every player who connects after the plugin is installed. This means it cannot retroactively pull data from before installation — if you need historical records from earlier, you are out of luck. But once it starts tracking, you can look up when a player was last online, when they first joined, and even get a rough sense of their login frequency. The plugin stores this information in a simple flat file, so there is no need to fiddle with MySQL or external dependencies. It just works.
Server admins who want a more polished setup often turn to launchers that simplify plugin management. For example, the foxygame.net launcher lets you browse and install server add-ons directly from its menu, making it a convenient, flexible, and modern Minecraft launcher for anyone who wants to keep their mods and plugins organized without digging through forum threads.
Commands and How to Use Them
The plugin revolves around a single command with a few optional twists. The syntax is clean and easy to remember:
- /who getplayer <player> [modifier] — Retrieves the last online time for the specified player. The player name is required; the modifier is optional.
When you run the command, WhoWasOn returns a human-readable time format based on how long ago the player was seen:
- Minutes — if the player was online in the past 0–60 minutes.
- Hours — if they were online in the past 1–24 hours.
- Days — if they were online in the past 1–7 days.
- Weeks — if they haven't been online for over a week.
- Online — if the target is currently connected to the server.
This graduated system gives you a quick mental snapshot without needing to parse raw timestamps. For a small survival server or a private whitelisted world, that level of detail is often exactly what you need.
The Exact Modifier for Precise Timestamps
Sometimes “3 days” isn't precise enough. WhoWasOn includes a modifier that unlocks exact values. By appending -e to the command, you can see the full breakdown. For instance, instead of “3 days,” you might get “3 days, 12 hours and 37 minutes.” This is particularly useful when settling disputes about inactivity or tracking player engagement right before a server event.
The modifier must be preceded by a dash, so the command looks like /who getplayer Steve -e. Currently, the exact modifier is the only one supported, and it works exclusively with the getplayer command. The plugin’s simplicity means you won't spend hours memorizing flags.
Permissions and Access Control
WhoWasOn ships with two permission nodes, both of which are granted to all players by default. This open approach makes sense for small, trust-based communities where everyone might want to check on friends. The nodes are:
- whowason.* — Grants access to every permission the plugin offers.
- whowason.getplayerhistory — Allows use of the /who getplayer command.
If you prefer to restrict history lookups to moderators or admins, you can simply negate the getplayerhistory node for the default group and assign it to a staff rank. The wildcard node is there for convenience, letting you quickly give full access without listing individual permissions.
Practical Use Cases for Server Owners
WhoWasOn shines in scenarios where you need lightweight tracking without the overhead of a full statistics plugin. Here are a few ways server owners put it to work:
- Checking inactive members — Before pruning a whitelist or cleaning up a towny plot, you can quickly see who hasn't logged in for weeks.
- Monitoring new player retention — By checking first-join times and comparing them to last-online timestamps, you can gauge whether newcomers stick around.
- Supporting player reports — If someone claims another player griefed them “yesterday,” you can verify whether that player was even online at the time.
- Event planning — Knowing when most of your regulars are typically online helps schedule server events for maximum attendance.
Because the plugin uses minimal resources, it runs smoothly even on low-end hardware or alongside dozens of other plugins. The fact that it was built by a beginner also means the code is approachable if you ever want to peek under the hood and learn how Bukkit event listening works.
Installation and Compatibility
Installing WhoWasOn follows the standard Bukkit plugin procedure. Download the JAR file, drop it into your server's plugins folder, and restart or reload the server. No configuration files need tweaking unless you plan to adjust permissions. The plugin has been tested on modern Bukkit builds, and its simple architecture means it rarely breaks with version updates. Just remember that it only starts logging from the moment it is first activated, so don't expect historical data to appear magically.
If you are juggling multiple plugins, you might appreciate a launcher that streamlines the whole process. The foxygame.net launcher, for instance, lets you download mods and plugins straight from its interface, turning what could be a tedious manual search into a few clicks. That kind of convenience keeps your server management flexible and modern, especially when you are experimenting with small utilities like WhoWasOn.
Is WhoWasOn Right for Your Server?
This plugin won't replace a full-featured analytics suite, and it doesn't try to. What it offers is a focused, no-fuss way to answer the simple question: “Who was on?” If your server needs graphs, heatmaps, or detailed session logs, you will eventually outgrow it. But for the vast majority of small to medium-sized servers, WhoWasOn hits a sweet spot. It is free, lightweight, and so easy to use that you can hand the command to your players without worrying about confusion or abuse.
In a landscape where many plugins try to do everything, WhoWasOn sticks to one job and does it well. Whether you run a tight-knit survival world, a creative building hub, or a private server for friends, having a quick way to check player activity keeps your community transparent and well-managed. Give it a try, and you might find that the simplest tools are often the most indispensable.