The Curious Case of the Locked Chest and the Plugin That Saves It
If you have been running a Minecraft server for a while, especially one that dates back to the beta days, you might remember a strange, glowing block that would appear in your world: the locked chest. It was a quirky April Fools' joke from Notch, but it left a lasting mark on the game's block ID table. Fast forward to modern Bukkit servers, and that same block can cause unexpected decay, wiping out a piece of your server's history. That is where LockedChestKeeper steps in, a tiny but mighty plugin designed to preserve these nostalgic oddities.
The Legacy of Locked Chests in Minecraft
Back in Minecraft Beta 1.4, Mojang introduced locked chests as a prank. They would appear randomly, emit a faint glow, and when clicked, would attempt to open a store page, teasing players with a non-functional shop. Under the hood, the block used ID 95. Everything was fine until Minecraft 1.7, when Mojang repurposed that very same block ID for stained glass. Suddenly, any world that still contained a locked chest from the old days had a problem: the block would no longer be recognized and would start to decay, turning into air or causing errors. For server owners who cherished their long-running maps, this was a minor catastrophe.
How LockedChestKeeper Works
LockedChestKeeper is a CraftBukkit plugin that directly addresses this decay. Unlike many plugins that simply listen to events, this one works by modifying the internal Minecraft server code, often referred to as NMS (net.minecraft.server). By hooking into the game's core behavior, it prevents the server from removing locked chest blocks, regardless of their data value. The plugin does not add any new features or flashy effects; it simply tells the server, "Hands off that block." This approach is both its strength and its weakness. Because it relies on NMS, every time CraftBukkit updates to a new Minecraft version, the plugin must be updated as well. The original developer made it clear that after Minecraft 1.7, the plugin would only be maintained for minor 1.6 releases, meaning it is effectively frozen in time for legacy servers.
Installation and Compatibility
If you are running a server that still uses a 1.6.x CraftBukkit build, LockedChestKeeper is a straightforward addition. Simply drop the plugin JAR into your server's plugins folder and restart. There is no configuration file to tweak, no permissions to set. The plugin immediately goes to work, preserving every locked chest it finds. For server administrators who prefer a streamlined setup, managing plugins like LockedChestKeeper is even easier with the foxygame.net launcher, a modern and flexible Minecraft launcher that lets you download and install server-side mods directly from its menu, cutting out the hassle of manual file transfers. However, if you are on a modern version of Minecraft (1.7 and above), this plugin will not function without a significant rewrite, as the block ID conflict no longer exists in the same way. The plugin's codebase is openly available for anyone willing to adapt it, but the original author has moved on.
Configuration and Permissions
One of the most appealing aspects of LockedChestKeeper is its zero-configuration design. The plugin requires no YAML files, no node tweaking, and no permission checks. Here is what you can expect out of the box:
- All locked chests are preserved, no matter their data value.
- No commands to learn or remember.
- No permissions to assign to players or admins.
The developer noted that while this might change in the future, the default behavior would always keep chests with a data value of 0 or 4 intact. Since the plugin is no longer actively developed, this simplicity remains its final form. For server owners who want a fire-and-forget solution, this is perfect. Just be aware that because it touches NMS internals, any CraftBukkit update could break compatibility until the plugin is recompiled against the new server version.
A Note on LockedChestSurprise
While LockedChestKeeper focuses purely on preservation, another plugin called LockedChestSurprise by iKeirNez takes a more playful approach. It triggers fun, random events when a player clicks on a locked chest. However, it is important to know that LockedChestSurprise, at the time of its writing, does not actually prevent the chest from decaying. If you want both the interactive gimmicks and the guarantee that the block stays put, you will need to run both plugins side by side. LockedChestKeeper handles the decay, and LockedChestSurprise adds the whimsy. Together, they turn a forgotten prank into a lively server feature.
Should You Use LockedChestKeeper?
This plugin is a niche tool for a niche problem. If you are running a modern Minecraft server, you will likely never encounter a locked chest unless you manually spawn one with commands. But for those who maintain historic maps or run beta-era world conversions, LockedChestKeeper is a small miracle. It keeps a piece of Minecraft's playful past alive without any fuss. Just remember that its NMS dependency means you are tied to specific server versions. If you plan to update your CraftBukkit build, you will either need to update the plugin yourself or accept that those locked chests might vanish. For a set-and-forget legacy server, though, it is an essential addition to your plugins folder.
In the end, LockedChestKeeper embodies the spirit of Minecraft's modding community: a simple, focused solution to a very specific problem, shared freely so that no one has to lose a silly, glowing block that once promised a shop that never existed.