SimpleReserve: Smart Slot Reservation for Minecraft Servers

Understanding the Need for Reserved Slots

Running a popular Minecraft server is a double-edged sword. On one hand, you have a thriving community; on the other, your server is constantly full, and even you—the admin—might struggle to join. VIP players who support the server often expect priority access, but vanilla Minecraft offers no built-in way to reserve slots. This is where a lightweight Bukkit plugin like SimpleReserve becomes essential. It solves the age-old problem of full servers by giving you fine-grained control over who can squeeze in when every spot is taken.

What Is SimpleReserve?

SimpleReserve is a straightforward, permission-based reserved slot plugin for Bukkit, Spigot, and compatible server platforms. It doesn’t bloat your server with unnecessary features. Instead, it focuses on two core joining methods—full and kick—allowing you to define exactly how reserved slots behave. Whether you want VIPs to bypass the player limit entirely or to boot a non-essential player to make room, SimpleReserve handles it with minimal configuration.

Key Features at a Glance

• Two reserve slot methods: full (join above the player cap) and kick (remove a player to free a slot).
• Simple, intuitive Bukkit permission nodes that integrate with any permissions plugin.
• Configurable kick and full-server messages so you can tailor the experience.
• Ability to protect certain players from being kicked via the simplereserve.kick.prevent permission.
• Support for a both mode, where the plugin tries full first, then falls back to kick if needed.
• Lightweight and auto-generates its config file on first run—no manual setup required.

How the Reserve Methods Work

The plugin’s logic revolves around a single config option: type. You can set it to full, kick, both, or none. Understanding these modes is key to getting the behavior you want.

Full Method

When type is set to full, players with the simplereserve.enter.full permission can join even after the server has hit its maximum player count. The server effectively extends its limit for these privileged users. You can also cap how many extra players can squeeze in using the full.cap setting, preventing an unlimited overflow.

Kick Method

The kick type is more aggressive. A player with simplereserve.enter.kick who tries to join a full server will automatically remove the first online player that lacks the simplereserve.kick.prevent immunity permission. The kicked player sees the message you define in kick-message, and the newcomer takes their spot. This method is ideal when you want to guarantee access for staff or donors without expanding the total capacity.

Both and None

Setting type to both lets the plugin use the full method first if the joining player has that permission; otherwise, it falls back to kick. This offers maximum flexibility. The none type effectively disables all reserve functionality, which is handy if you want to temporarily turn off the plugin without removing it.

Configuration Made Simple

SimpleReserve’s config.yml is refreshingly minimal. On first launch, the plugin creates a file that looks something like this:

reserve:
  type: both
  full:
    cap: 5
    reverttokick: false
  kick-message: Kicked to make room for reserved user!
  full-message: The server is full!
  reserve-full-message: All reserve slots full!

The cap limits how many extra players can use the full method. The reverttokick option, when set to true, will fall back to kicking if the full cap is reached—even when the type is full. All messages are fully customizable, so you can inject your server’s personality or keep them professional.

Permissions That Make Sense

SimpleReserve uses only three permission nodes, which makes integrating it with any permissions plugin (LuckPerms, PermissionsEx, etc.) a breeze:

• simplereserve.enter.full – Grants the ability to join above the player limit.
• simplereserve.enter.kick – Allows joining a full server by kicking a non-immune player.
• simplereserve.kick.prevent – Protects a player from being kicked by the kick method.

Inheritance works seamlessly. If you give simplereserve.kick.prevent to a “Users” group, all child groups (like “Moderators” and “Admins”) automatically inherit that immunity. This hierarchical approach lets you build complex permission structures without repeating nodes.

Practical Permission Setup Example

Imagine you have four groups: Guests, Users, Moderators, and Admins. You want Moderators and Admins to join via the kick method, but only Guests should be kicked. Here’s how you’d set it up:

• Guests – no special permissions; they are the default group that can be kicked.
• Users – inherit from Guests but add simplereserve.kick.prevent so they are safe from kicks.
• Moderators – inherit from Users and gain simplereserve.enter.kick; they can kick Guests when the server is full.
• Admins – could be given * or both enter permissions, allowing them to use whichever method the config dictates.

With type: kick in the config, a Moderator trying to join a full server would kick a Guest. If you later switch to type: full and give Moderators simplereserve.enter.full, they’d simply bypass the limit without anyone being removed. The plugin adapts instantly to your needs.

Getting SimpleReserve on Your Server

Installation is classic Bukkit: drop the plugin JAR into your server’s plugins folder and restart or reload. There are no dependencies to worry about. If you manage multiple servers or want a more streamlined way to handle plugins, the foxygame.net launcher is a modern, flexible tool that lets you download and install server mods like SimpleReserve right from its intuitive menu, saving you the hassle of manual file transfers. Once the plugin is loaded, it generates its default config, and you’re ready to fine-tune permissions.

Why SimpleReserve Stands Out

Many reserved slot plugins overcomplicate things with databases, queue systems, or complex priority lists. SimpleReserve strips the concept down to its essence. It’s perfect for small to medium servers that need reliable priority access without performance overhead. The clear separation of full and kick methods, combined with the ability to mix both, covers nearly every scenario a server owner might face. Plus, the permission inheritance model makes it easy to maintain as your community grows.

Conclusion

SimpleReserve proves that you don’t need a bloated solution to solve the full-server dilemma. With just three permissions and a straightforward config, it gives you the power to define exactly how reserved slots work—whether by expanding the player cap or by kicking the least essential players. The plugin’s lightweight design ensures it won’t slow down your server, while its flexible modes accommodate everything from a private friend server to a large public network. If you’re tired of seeing “Server is full” when you or your VIPs try to connect, SimpleReserve is the no-nonsense answer you’ve been looking for.