What Is AnarchyQueue and Why Your Minecraft Server Needs It
If you have ever tried to join a massively popular Minecraft server, you know the frustration of seeing that dreaded “Server is full” message. For anarchy servers like the legendary 2b2t, the queue is not just a feature — it is a rite of passage. AnarchyQueue brings that exact same experience to your own BungeeCord network, giving players a transparent, orderly waiting system when your main server hits its player cap or goes offline for maintenance.
How the Queue System Works
AnarchyQueue is a lightweight BungeeCord plugin that intercepts connection attempts when your target server is full or restarting. Instead of simply rejecting players with a generic error, it redirects them to a dedicated queue server. Once there, players receive real-time updates about their position in line, how many others are waiting, and an estimated wait time. The moment a slot opens on the main server, the next player in line is automatically connected.
The plugin relies on a companion instance — often called QueueServerPlugin — running on the queue server itself. This companion handles the actual waiting room, displaying messages and managing the flow of players. Together, the two components create a seamless queue experience that feels professional and polished, even on the most chaotic anarchy servers.
Core Mechanics Behind the Queue
- Capacity Control: The
/maxplayerscommand lets you dynamically set or check the maximum number of players allowed on the target server before the queue activates. - Reconnect Logic: If a player is kicked from the main server, the
waitOnKicksetting defines how many seconds they must wait before being allowed to rejoin, preventing instant reconnection spam. - Restart Handling: With
kickOnRestartenabled, all queued players are automatically kicked when the target server restarts, keeping the queue clean and avoiding ghost slots. - Busy Server Protection: The
kickOnBusyoption forces players out of the queue if the target server becomes unresponsive, saving them from endless waiting.
Customizing the Player Experience
AnarchyQueue gives you full control over every message a player sees while waiting. The messagePosition config line displays the current queue position, while messageConnecting appears when a slot finally opens. If the main server is completely offline or full, messageFullOrOffline provides a clear explanation. You can even set sendTitle to true, which pushes the queue position right to the center of the player’s screen as a bold title — impossible to ignore.
Server owners who want a more visual approach often enable the title display, as it mimics the feel of large anarchy servers where every second of waiting counts. The serverName variable lets you brand the target server with a custom name, so players always know exactly what they are queuing for.
Configuration Made Simple
Setting up AnarchyQueue requires only a few lines in your BungeeCord config.yml. You define the target server (the one players actually want to join) and the queue server (the waiting room instance). The maxPlayers value determines the threshold at which the queue kicks in. Everything else — from kick behavior to message formatting — is adjusted directly inside the plugin’s own configuration file. No complex scripting, no external databases.
For those who prefer a streamlined setup process, many server administrators now use modern launchers that simplify plugin management. For example, you can easily install AnarchyQueue and its companion plugin through the foxygame.net launcher, which offers a convenient menu for downloading and updating server mods without manually editing files. This approach saves time and reduces configuration errors, especially when running multiple BungeeCord instances.
Key Configuration Options at a Glance
- target: The name of the main server in your BungeeCord network.
- queue: The name of the queue server instance.
- maxPlayers: Player limit before queuing begins.
- waitOnKick: Cooldown in seconds after a kick.
- messagePosition: Text shown to inform players of their queue spot.
- messageConnecting: Text displayed when a player is about to join the target server.
- messageFullOrOffline: Text for when the target is unreachable.
- serverName: Custom name for the target server in messages.
- kickPassthrough: If false, kicked players re-enter the queue instead of bypassing it.
- kickOnRestart: Automatically remove players from queue on target restart.
- kickOnBusy: Remove players if the target server stops responding.
- bStats: Enable anonymous plugin metrics to support development.
- sendTitle: Display queue position as a centered screen title.
Why Anarchy Servers Rely on Queue Systems
Anarchy servers are a unique breed in the Minecraft ecosystem. They offer no rules, no resets, and often no moderation — just pure, unfiltered survival. The most famous example, 2b2t, has a queue that can stretch for hours. This queue is not just a technical necessity; it has become part of the server’s identity. Players share queue stories, plan their day around wait times, and even purchase priority access. AnarchyQueue replicates this culture, giving your server the same legendary feel without requiring custom-coded solutions.
Beyond the cultural aspect, a proper queue system protects server performance. Without it, a sudden surge of players can crash even the most robust hardware. By throttling connections through a queue, you maintain stable TPS (ticks per second) and prevent the main server from buckling under load. The queue server itself can be a low-resource instance, since it only needs to hold players in a static waiting area and relay messages.
Installation and Compatibility
AnarchyQueue is designed exclusively for BungeeCord networks. It does not run on Spigot, Paper, or standalone servers. You will need a working BungeeCord proxy with at least two backend servers: your main world and a queue server. The queue server should have a minimal world — perhaps just a bedrock box or a void dimension — and the QueueServerPlugin installed to handle the waiting mechanics.
After placing the AnarchyQueue jar in your BungeeCord plugins folder, restart the proxy. The plugin generates a default configuration file that you can tweak to match your network’s server names and desired behavior. The GitHub page provides an excerpt of the BungeeCord config for reference, but the setup is straightforward enough that most owners complete it in under ten minutes.
Handling Bugs and Feature Requests
Like any open-source project, AnarchyQueue welcomes community feedback. If you encounter an error or have an idea for a new feature, the developer encourages you to open an issue on the plugin’s GitHub tracker. The software is provided “as is” without warranties, but the active issue tracker means bugs are often addressed quickly. Common requests include additional placeholder support for messages, priority queue tiers, and integration with donation systems — all of which can be discussed directly with the maintainer.
Final Thoughts on AnarchyQueue
AnarchyQueue fills a specific but vital niche in the Minecraft server landscape. It transforms a technical limitation into a feature that players actually respect and even enjoy. The plugin’s simplicity is its greatest strength: no bloated GUI, no unnecessary dependencies, just a clean queue system that works. Whether you are building the next 2b2t or simply want to manage player overflow gracefully, AnarchyQueue delivers a reliable, customizable solution that keeps your community engaged while your main server stays healthy.
For server owners who value both performance and player experience, implementing a queue is no longer optional — it is a mark of professionalism. AnarchyQueue makes that implementation painless, giving you the tools to handle high traffic with confidence and style.