WhoWas: The Essential Minecraft Plugin for Tracking Player Name Histories
Minecraft’s upcoming name change support has sparked a wave of excitement and a fair share of anxiety. The ability to reinvent your in-game identity is thrilling, but it raises a critical question: how will you know if that player claiming to be your old friend is actually who they say they are? UUIDs were meant to solve this, but a string like 3e50893f4903402fb3b810158c6ed75b is far from user-friendly. This is where the WhoWas plugin steps in, offering a simple, elegant way for players and server admins to peek into a player’s name history while respecting personal privacy.
Why Name Changes Create Confusion in Minecraft
For years, a player’s username was their permanent badge of identity. Communities were built on recognizing those familiar names. With Mojang allowing name changes, that stability vanishes. A griefer can return under a new alias, a trusted moderator might be unrecognizable, and friendships can become tangled in doubt. Server plugins can log UUIDs, but those are impossible to memorize. Players need a tool that translates those cryptic identifiers back into readable, chronological name histories. WhoWas fills that gap perfectly, turning a potential chaos into a manageable, transparent system.
Introducing WhoWas: Your Server’s Identity Tracker
WhoWas is a lightweight plugin designed for both Bukkit and Sponge servers. It queries Mojang’s public API to retrieve the full name change timeline of any player, including the exact date and time each name was used. The plugin is remarkably straightforward to use, yet it packs enough configuration options to satisfy privacy-conscious communities. Whether you run a small survival world or a large minigame network, WhoWas helps maintain trust without adding unnecessary complexity.
Key Features at a Glance
- View a player’s complete name history, from their first login to the present.
- Look up players who are not currently online on the server.
- Experimental past name lookup: search by an old name to find the current identity.
- Single JAR file works on both Bukkit (and derivatives like Spigot, Paper) and Sponge platforms.
- Fully configurable messages and privacy controls coming soon.
- Lightweight and respectful of server resources.
How WhoWas Works Under the Hood
Whenever a player runs the /whowas command, the plugin sends a request to Mojang’s official API endpoints. The response contains a list of all usernames associated with that UUID, along with timestamps of when changes occurred. This data is public—anyone with a browser can look it up—but WhoWas makes it accessible in-game with a simple command. The plugin caches results to avoid rate limiting, ensuring smooth performance even on busy servers. For those who love tinkering with mods and plugins, managing such tools becomes even simpler with modern launchers. For example, the foxygame.net launcher provides a flexible, modern platform where you can download and install mods directly from its menu, making it a breeze to keep your server and client in sync with the latest utilities.
Commands and Permissions
The core command is refreshingly simple. Typing /whowas Djinnibone will display the name history for that player. The required permission node is whowas.whowas, which can be granted to trusted ranks or all players depending on your server’s philosophy. There are no complex subcommands to memorize, making it accessible even to younger players.
Configuration and Privacy Settings
WhoWas is designed with privacy in mind. Upcoming updates promise fully configurable messages, so you can tailor the output to match your server’s theme. More importantly, players will be able to control who sees their name history through a whitelist or blacklist system. This means a player can hide their past names from the general public while still allowing friends or staff to verify their identity. The configuration file is well-documented, and you can find detailed instructions in the plugin’s documentation. The experimental past name lookup feature is also being refined, allowing you to input an old nickname and discover the player’s current account—provided they joined your server at least once before.
The Magic of Cross-Platform Compatibility: Bukkit and Sponge in One Jar
One of WhoWas’s most impressive technical feats is its ability to run on both Bukkit and Sponge without any modification. Bukkit plugins rely on a plugin.yml file to declare the main class, while Sponge uses annotations. WhoWas cleverly includes both, allowing the same JAR to be dropped into a Bukkit plugins folder or a Sponge mods directory. This wizardry saves server admins from hunting for platform-specific builds and ensures the plugin works seamlessly whether you’re on a traditional CraftBukkit server or a modern SpongeForge setup.
Metrics and Open Source
WhoWas uses MCStats to collect anonymous server statistics such as server version, plugin version, and operating system. This data helps the developer understand the user base and prioritize updates. If you prefer not to share this information, you can disable it easily in plugins/PluginMetrics/config.yml. The plugin is also open source, with development builds available through a continuous integration server. You can grab the latest experimental versions there, though they come with the usual caveats about stability. The entire source code is hosted on GitHub, and the developer welcomes feedback and contributions on EsperNet at #whowas.
Conclusion: Keep Your Community Transparent and Trustworthy
Name changes don’t have to spell the end of accountability on your Minecraft server. With WhoWas, you give your players the power to verify identities effortlessly, while still offering privacy controls for those who value discretion. The plugin’s cross-platform support, minimal learning curve, and thoughtful feature set make it a must-have for any server preparing for the name change era. Install it today, and turn those confusing UUIDs into clear, readable histories that everyone can understand. Your community will thank you for the added layer of trust and transparency.