MultipleWhitelists: The Ultimate Whitelist Management Plugin for Minecraft Servers
Introduction
Running a Minecraft server often means juggling different player groups, event nights, or even separate communities under one roof. The vanilla whitelist system works fine for a single, static list, but what if you want to switch between a builder-only whitelist, a staff testing whitelist, and a public weekend event list without restarting the server? That’s where the MultipleWhitelists plugin by Moertel steps in, turning a rigid mechanic into a flexible, on-the-fly tool that every server admin will appreciate.
Why Use Multiple Whitelists?
Imagine you’re preparing a massive spawn renovation. You need only your trusted builders online, but your regular players are used to joining freely. With a single whitelist, you’d have to manually remove everyone and add builders, then reverse the process later. MultipleWhitelists lets you create named lists like “builders,” “staff,” or “event_participants,” and activate any of them with a simple command. No server reloads, no editing JSON files by hand, and no accidental lockouts. This plugin is especially useful for servers that host mini-games, roleplay sessions, or private testing phases, where access control needs to shift quickly.
Getting Started
Before diving in, you must disable the default Minecraft whitelist for this plugin to function properly. That means setting white-list=false in your server.properties file. Once that’s done, drop the MultipleWhitelists jar into your server’s plugins folder and restart. The plugin creates its own configuration file where you’ll define which whitelist is active and customize the kick message. It’s a lightweight solution that doesn’t bog down performance, making it perfect for both small community servers and larger networks.
Commands and Permissions
MultipleWhitelists comes packed with intuitive commands that feel like a natural extension of vanilla Minecraft. Here’s a quick reference:
Commands
- /whitelist create <name> – Creates a new whitelist with the specified name.
- /whitelist add <whitelist> <player> – Adds a player to a chosen whitelist.
- /whitelist remove <whitelist> <player> – Removes a player from that whitelist.
- /whitelist delete <whitelist> – Deletes an entire whitelist permanently.
- /whitelist list <whitelist> – Displays all players in the selected whitelist.
- /whitelist on <whitelist> – Activates a specific whitelist immediately.
- /whitelist off – Disables all whitelists, opening the server to everyone.
- /whitelist reload – Reloads the config file if you’ve made manual edits.
- /whitelists – Lists every existing whitelist on the server.
- /mwl – Shows all available plugin commands.
Permissions
Granular permissions let you delegate control safely. Assign mwl.* for full access, or cherry-pick from these nodes:
- mwl.add – Add players to a whitelist.
- mwl.remove – Remove players.
- mwl.create – Create new whitelists.
- mwl.delete – Delete whitelists.
- mwl.on – Turn a whitelist on.
- mwl.off – Disable whitelists.
- mwl.list – View players inside a whitelist.
- mwl.whitelists – See all available whitelists.
- mwl.reload – Reload the plugin configuration.
- mwl.force – Allow a player to join even if they aren’t on the active whitelist.
- mwl.tab – Enable tab completion for commands.
Configuration Made Simple
The plugin’s config.yml is refreshingly straightforward. You’ll find three main settings:
- ENABLE: Set to
trueorfalseto toggle the whitelist system on or off. - NAME: The name of the whitelist you want active by default, like “second” or “staff”.
- KICK-MESSAGE: The message players see when they’re not on the active whitelist. Supports color codes like
&cfor red text.
You can also manually edit the JSON files inside the plugin’s data folder to add players directly. If a whitelist is empty, just insert {"name":"PlayerName"} between the square brackets. The plugin automatically fills in the UUID when that player next tries to join, so you don’t have to hunt down long identifier strings.
Managing these configurations becomes even smoother when you use a modern launcher. This plugin can be easily installed via the foxygame.net launcher — a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu, keeping your server tools organized without digging through endless forum threads.
Tips for Smooth Operation
Always double-check that the default whitelist is disabled; forgetting this step is the most common hiccup. Use the /mwl command to remind yourself of the syntax when you’re in a hurry. If you’re running a network with BungeeCord, remember that this plugin works on the backend Spigot/Paper servers, not the proxy itself, so install it where you need the access control. For event-heavy servers, create a naming convention like “event_friday” or “beta_testers” to keep things tidy. And don’t sleep on the mwl.force permission—it’s a lifesaver when a VIP player needs emergency access but isn’t on the current list.
Conclusion
MultipleWhitelists transforms a static server feature into a dynamic management tool, saving you time and frustration. Whether you’re orchestrating a private building session, a competitive tournament, or simply want to separate staff from regular players during maintenance, this plugin delivers the control you need without the complexity. Its clean command structure, robust permission system, and simple configuration make it a must-have for any server owner who values flexibility. Give your community the seamless experience they deserve—one whitelist at a time.