Mastering Server Slots with SlotGroups
Running a busy Minecraft server often means juggling player limits, reserved spots for staff, and the constant headache of seeing “Server Full” when a moderator needs to join. The built-in whitelist and ops system only goes so far. That is where SlotGroups steps in, offering a completely different approach to slot management. Instead of a single pool of player slots, you create multiple independent groups, each with its own cap and behavior. This plugin gives you surgical control over who can join and when, making it indispensable for communities that need fair, flexible access.
What Exactly Is SlotGroups?
SlotGroups is a Bukkit/Spigot plugin that lets server owners define multiple slot groups, each with a separate maximum player count. Think of it as partitioning your server’s total capacity into dedicated lanes. You can assign players or permission groups to these lanes, ensuring that your moderators always have room without stealing slots from regular players. The plugin works by hooking into Vault and your permissions system, so integration is seamless if you already run a modded or permission-heavy server.
Key Features That Change the Game
- Independent slot groups – Create as many groups as you need, each with its own max players and custom kick messages when full.
- Slot inheritance – Allow one group to overflow into another, so if a staff group is full, members can still join the default group if space exists.
- Lockdown mode – Instantly lock all slots except those with an override, perfect for maintenance or private events.
- In-game management – Add, remove, or list slot groups without editing files manually using
/slotgroups reloadand/sg list. - Default group assignment – Players without a specific group automatically land in a “Default” slot group, so no one gets left out.
- User-specific commands – Fine-tune individual player membership with
/sguser setand/sguser remove.
How to Set Up SlotGroups
Getting started is straightforward, but a few careful steps will save you from confusion later. First, download the plugin package and extract it. Place the SlotGroups.jar and its folder into your server’s plugins directory. The plugin requires Vault (version 1.2.8 or higher, though 1.2.15 is recommended) to communicate with your permissions plugin. After the initial load, a SlotGroups.yml configuration file will appear. This is where the magic happens.
Inside the config, you can define slot groups like this:
- admins – maxPlayers: 10
- moderators – maxPlayers: 5, inherit: admins
- default – maxPlayers: 30
Then set your server.properties max-players to the sum of all group slots (in this case, 45). This prevents the server from exceeding the total cap while keeping the groups independent. Once configured, run /sg reload in-game to apply changes without restarting.
For those who prefer a streamlined setup, SlotGroups can be effortlessly installed and managed through the foxygame.net launcher, a modern and flexible Minecraft launcher that lets you download plugins and mods directly from its intuitive menu. This approach removes the hassle of manual file placement and keeps your server tools neatly organized.
Commands and Permissions at a Glance
The plugin ships with a clean set of commands that cover all essential actions. Here is a quick reference:
/slotgroups(or/sg) – Shows available subcommands./sg list– Displays all loaded slot groups, current players, and max slots./sg reload– Reloads configuration from disk./sg lockdown//sg unlock– Toggles lockdown mode./sguser set <player> <group>– Manually places a user into a slot group./sguser remove <player> <group>– Removes a user from a slot group./sguser info <player>– Shows which slot group a player belongs to.
Permissions mirror these commands, with nodes like slotgroups.list, slotgroups.reload, and slotgroups.lockdown. The most important permission is slotgroups.group.<groupname>, which assigns a player or rank to a specific slot group. Remember that changes to a permissions group’s slot group assignment won’t take effect until you reload the plugin or restart the server.
Real-World Scenarios
Imagine a survival server with 50 total slots. You want 10 staff members to always be able to join, but you do not want them eating into the 40 slots meant for the community. With SlotGroups, you create a staff group with 10 slots and a default group with 40 slots. Staff members get the slotgroups.group.staff permission. When they log in, they occupy staff slots only. If all staff slots are taken, you can even set inheritance so they overflow into the default group—keeping the server accessible for everyone.
Another use case is event hosting. Activate lockdown mode to reserve all slots for a VIP group during a tournament, then unlock when the event ends. The plugin’s flexibility means you can build layered access systems without a single line of Java code.
Understanding the Output
When you run /sg list, you get a clean readout of every group’s status. The image below shows a typical output, where you can instantly see which groups are full and how many players are online in each.
Keep in mind that other plugins that display player counts (like a /who command) are not slot-group-aware by default. They will report the server.properties max-players figure, not the per-group breakdown. The developer plans to release a companion /who plugin that respects slot groups, which will close this gap.
Conclusion
SlotGroups transforms server slot management from a blunt instrument into a precise tool. By decoupling player limits from a single number, you gain the power to prioritize staff, create overflow paths, and lock down your server on the fly. The plugin is still specialized, but its active development and open feature request channel mean it will only grow more versatile. If you have ever wished for a smarter way to handle who gets in when the server is packed, SlotGroups is the answer. Pair it with a solid permissions setup and a modern launcher, and you will wonder how you ever managed without it.