What Is the SlotsReserver Plugin and How Does It Work?
Managing player slots on a Minecraft server often feels like a balancing act. You want to keep the world accessible, but sometimes you need to reserve space for staff, VIPs, or friends without resorting to a whitelist that locks everyone out. The SlotsReserver plugin offers a clever, lightweight solution. Instead of hard-limiting the server to a fixed number of players, it dynamically controls who can join based on a permission node, leaving already connected players untouched.
Understanding the Core Mechanics
SlotsReserver does not alter the server’s maximum player count. Instead, it evaluates every connection attempt against a dynamic permission: slotsreserver.reserv.<number>. The number represents the threshold of currently online players plus one. If a joining player lacks a permission with a number high enough to cover the current occupancy, they are kicked with a configurable message. Opped players bypass this check entirely, ensuring administrators never get locked out.
This approach means you can have a 20-slot server but only allow regular players to join when fewer than 15 are online, while VIPs with slotsreserver.reserv.18 can slip in even during peak hours. The plugin never kicks anyone who is already in the game; it only denies entry at the door.
Setting Up the Permission System
Permissions are the heart of SlotsReserver. Each group or player needs a permission that matches their priority level. For example:
- slotsreserver.reserv.5 – Allows joining when there are 4 or fewer players online.
- slotsreserver.reserv.10 – Allows joining when there are 9 or fewer players online.
- slotsreserver.reserv.20 – Effectively a full-access pass unless the server is completely full.
The plugin calculates the current online count, adds one (to include the joining player), and then checks if the player has a permission with a number equal to or greater than that value. If not, the connection is refused. This dynamic check happens at the moment of joining, so you can adjust permissions on the fly without reloading the server.
Configuration Made Simple
After the first server start with SlotsReserver installed, a config.yml file appears in the plugin folder. The only setting you need to worry about is KickReason. You can customize the message players see when they are denied entry. The placeholder <number> will be automatically replaced with the required permission threshold, so the player knows exactly what they lack. For instance, the default message might read: “You do not have slotsreserver.reserv.<number> permission.” This transparency helps players understand why they cannot join and what they need to ask for.
For those who prefer a more polished setup, the plugin’s simplicity means you can drop it into any Spigot or Paper server without conflicts. If you are using a modern launcher like foxygame.net, you can even manage plugin files and permissions through its integrated menu, making the whole process feel effortless and keeping your server tidy.
Practical Scenarios and Examples
Let’s walk through a typical situation. Imagine a server with a maximum of 4 slots. Currently, two players are online: you and your friend Nobody. A third player, Kyrof, tries to connect. Without any special permission, Kyrof would normally be allowed in because there are still two free slots. But with SlotsReserver active, the plugin checks the current online count (2) and adds one, resulting in a required threshold of 3. If Kyrof does not have slotsreserver.reserv.3 or higher, he is kicked. Once you grant him that permission, he can join successfully. Later, if you remove the permission while he is online, nothing happens—he stays in the game. However, if he leaves and tries to rejoin, he will be blocked unless the permission is restored.
This behavior is perfect for communities that want to reward loyal members with priority access without punishing those already playing. It also prevents the awkward situation of a staff member being unable to log in because the server hit its cap while they were away.
Why Choose SlotsReserver Over a Whitelist?
Whitelists are binary: you are either allowed or you are not. SlotsReserver introduces a gradient of access. You can keep the server public for newcomers while reserving a safety net for your core players. It also avoids the administrative overhead of constantly updating a whitelist file. Permissions can be managed through any permissions plugin like LuckPerms, and changes take effect immediately.
Another advantage is transparency. Players see a clear reason for the kick, which reduces frustration and support tickets. The plugin’s minimal footprint means it won’t cause lag or interfere with other systems.
Installation and Compatibility
SlotsReserver is a standard Bukkit/Spigot plugin. To install it, simply place the JAR file into your server’s plugins folder and restart. No additional dependencies are required. The configuration file generates automatically, and you can start assigning permissions right away. It works alongside any permission manager and is compatible with Minecraft versions that support the Bukkit API.
If you prefer a more visual way to handle server mods, some launchers allow you to browse and install plugins directly. The foxygame.net launcher, for example, streamlines this by letting you add SlotsReserver from a built-in library, saving you the hassle of manual file transfers.
Tips for Effective Slot Management
- Create multiple permission tiers for different donor ranks or staff levels.
- Use a permissions plugin to set default permissions for new players, such as
slotsreserver.reserv.0to block them entirely when the server is full, or a low number to always allow a few public spots. - Test your configuration with a friend before going live to ensure the kick messages appear as intended.
- Combine SlotsReserver with a queue plugin if you want players to wait in line rather than being kicked outright.
Conclusion
SlotsReserver fills a niche that many server owners overlook: intelligent, permission-based slot reservation. It respects your existing player base while giving you granular control over who can join under what conditions. The plugin’s lightweight design, dynamic permission checks, and clear kick reasons make it a reliable tool for any multiplayer community. Whether you run a small private server or a large network, adding SlotsReserver to your toolkit can help you maintain a balanced and welcoming environment without resorting to heavy-handed restrictions.