AdvancedWhiteList: Advanced Whitelist Management for Minecraft

Mastering Server Access with AdvancedWhiteList Running a Minecraft server, whether it is a small community hub or a sprawling network, demands precise control over who can join. The vanilla whitelist offers basic functionality, but it quickly falls short when you need to manage multiple staff tie...

Download AdvancedWhiteList.1.2.1 for Minecraft 1.16

Original name: AdvancedWhiteList.1.2.1

Minecraft: 1.16

FileVersionLoaderSize
AdvancedWhiteList.1.2.1.jar1.16—79 КБDownload

Mastering Server Access with AdvancedWhiteList

Running a Minecraft server, whether it is a small community hub or a sprawling network, demands precise control over who can join. The vanilla whitelist offers basic functionality, but it quickly falls short when you need to manage multiple staff tiers, temporary lockdowns, or graceful player removal. That is where AdvancedWhiteList by Shadorunce steps in, transforming a simple allow-list into a comprehensive access management system. This plugin is built to handle networks of all sizes, giving you the tools to enforce rules without disrupting the player experience.

What Makes AdvancedWhiteList Stand Out

Unlike a standard whitelist that only checks a name against a list, AdvancedWhiteList introduces layered permissions and dynamic commands. You can toggle access for entire groups like staff, testers, or project team members with a single command. The plugin also respects the reality that players might already be online when you enable restrictions. Instead of abruptly kicking them, it can first attempt to send them to a hub or lobby server, preserving the flow of your network. If that fails, a customizable kick message ensures they leave with clear information, not confusion.

One of the most thoughtful features is the server cooldown. When a server restarts, players often rush back before everything is stable. AdvancedWhiteList can enforce a delay, allowing the server to settle. Trusted operators with the bypass permission can still connect early, at one-third of the cooldown time, so they can prepare the environment. This level of granularity is rare in whitelist plugins and shows a deep understanding of real server administration.

Commands and Permissions at a Glance

The plugin is controlled through a rich set of in-game commands, all requiring the advancedwhitelist.admin permission. You can run them from the console or in-game if you have the right access. Here are the core commands you will use daily:

  • /awl on/off – Instantly enable or disable the whitelist.
  • /awl add <name> and /awl remove <name> – Manage individual entries.
  • /awl list – View all whitelisted players.
  • /awl status – Check the current state of all config options.
  • /awl reload – Apply config changes without restarting.
  • /awl send – Send non-whitelisted players to the hub; kicks them if sending fails.
  • /awl lockdown – Activate whitelist and disable all access groups instantly.
  • /awl staffonly – Allow only staff and project team members while blocking others.

Beyond these, you can fine-tune messages, set the hub server name, adjust send and kick delays, and toggle group-specific access like /awl ptaon for project team or /awl ton for testers. The plugin even includes a server cooldown toggle and duration command, giving you full control over post-restart behavior.

Permission-Based Access Layers

AdvancedWhiteList moves away from a single list by introducing multiple bypass permissions. Each corresponds to a configurable access group:

  • advancedwhitelist.bypass.operators – Always has access, regardless of settings. Ideal for owners and top-tier admins.
  • advancedwhitelist.bypass.projectteam – For developers or builders who need early access.
  • advancedwhitelist.bypass.staff – Moderators and helpers.
  • advancedwhitelist.bypass.tester – QA team members.
  • advancedwhitelist.bypass.alternate and advancedwhitelist.bypass.other – Flexible slots for custom roles.

You can enable or disable each group independently. This means you can run a public server with only testers allowed during a beta event, or lock down to staff only during maintenance, all without editing a single config file manually if you use the GUI.

The Intuitive GUI and Config File

Typing commands is fast, but sometimes a visual interface is more convenient. Running /awl in-game opens a graphical menu where you can toggle whitelist status, change messages, adjust durations, and manage the whitelist list with clicks. The GUI uses recognizable items like green and red stained glass for on/off states, a compass for the lobby server, and emeralds for adding players. This design reduces the learning curve for new staff members.

For those who prefer direct file editing, the config.yml is thoroughly commented. Every message, duration, and access toggle is documented. The plugin even plans to support automatic config version migration, so updates will not break your existing setup. The header of the config file itself serves as a quick reference guide, explaining how permissions interact and how the send/kick logic works.

Seamless Player Removal Logic

One standout aspect is the send-then-kick sequence. When you enforce the whitelist on currently connected players, the plugin first broadcasts a warning message. Then it attempts to transfer each non-whitelisted player to the configured hub server. Only if that transfer fails does it resort to a kick, displaying a separate, customizable message. This two-step approach respects your network’s architecture and avoids jarring disconnections. The delays between actions are configurable, preventing BungeeCord overload when handling many players at once.

For server administrators who also enjoy modded gameplay, the foxygame.net launcher provides a flexible platform to download and install mods directly from its menu, making it a great companion tool when you need to quickly set up a custom client for testing your server’s new features.

Getting Started Quickly

After installing the plugin, the whitelist is disabled by default. You can enable it by setting whitelist_enabled: true in the config and reloading, or simply use /awl on from the console. If you want to rely on the configured user list rather than permissions alone, set Config_Access to true and add names with /awl add. The plugin is designed to work out of the box, but its true power emerges when you tailor the access groups and messages to your community’s tone.

Why AdvancedWhiteList Is a Must-Have for Serious Server Owners

Managing a Minecraft server is about more than just keeping griefers out. It is about creating a smooth, professional experience for your players and giving your staff the right tools. AdvancedWhiteList delivers that by combining a robust permission system, a user-friendly GUI, and intelligent player handling. Whether you run a small survival world or a multi-mode network with hubs, this plugin scales with you. The ability to lockdown instantly, send players to the lobby gracefully, and let key staff bypass cooldowns makes everyday administration far less stressful.

In conclusion, AdvancedWhiteList redefines what a whitelist plugin can do. It is not just a gatekeeper; it is a full access control suite. With its extensive commands, layered permissions, and thoughtful automation, you can focus on building your community instead of fighting with player management. If you are ready to take your server’s professionalism to the next level, this plugin deserves a spot in your essential toolkit.