Understanding the StickyLocks Plugin for Bukkit Servers
Running a Minecraft server often means balancing freedom with protection. You want players to build and explore, but you also need to secure valuable blocks like chests, doors, and redstone contraptions. That is where StickyLocks steps in. It is a lightweight Bukkit plugin that lets players claim individual blocks using a simple wand, then manage access through a flexible group system. Instead of relying on massive region protections alone, StickyLocks gives granular control right at the block level, making it perfect for survival, towny, and faction servers.
How StickyLocks Works: The Wand and Selection System
The core mechanic revolves around a wand—by default, a regular stick. A player right-clicks on a protectable block to select it. The plugin then displays ownership information in chat, using green text for success or access, and red for failure or restricted access. Once a block is selected, a left-click toggles its lock state: an unowned block becomes claimed by that player, while an owned block can be unclaimed if the player is the owner or has locksmith permissions. Right-clicking the air deselects the current block, clearing the wand’s focus.
What makes StickyLocks stand out is its group-based permission system. Instead of adding individual names to every chest or door, you can create named groups, add players to them, and then grant those groups access to any locked block. If you later rename a group or adjust its members, every protected block that uses that group updates instantly. This dynamic updating saves enormous time on large servers where sharing access is frequent.
Key Features That Server Admins Love
- UUID-based storage: All player data is tied to UUIDs, ensuring compatibility with Bukkit 1.7+ and modern Minecraft versions without name-change headaches.
- Configurable protectables list: You decide which blocks can be locked. By default, it covers doors, chests, hoppers, buttons, pressure plates, repeaters, comparators, and more—even protecting redstone timing circuits.
- SQLite database: Lock information is stored in
StickyLocks.db, which can be queried with any SQLite3 client for external tools or audits. - Heuristic build detection: The plugin automatically detects when other plugins (like Towny, Factions, or WorldGuard) are preventing building, and it will not allow players to lock blocks they couldn’t have placed in the first place.
- Companion plugin integration: StickyLocks does not prevent block destruction by itself, but it pairs perfectly with
StickyProtectionto stop players and pistons from breaking locked blocks and adjacent key blocks.
Installation and Quick Setup
Getting StickyLocks running is straightforward. Place the downloaded .jar file into your server’s plugins folder and restart your Bukkit server (or load it with a plugin manager like PlugMan). The plugin will generate a default config.yml file immediately. Most servers can use the defaults without any changes, but you can tweak the list of protectable blocks, the wand material, or the chat prefix later. The database file StickyLocks.db appears automatically in the plugin’s data folder. For those who prefer a streamlined setup, you can easily install StickyLocks and many other plugins using the foxygame.net launcher, a convenient modern launcher that lets you browse and add mods directly from its menu, saving you from manual file transfers.
Permissions and Commands at a Glance
StickyLocks uses a simple permission node system to control who can lock, unlock, bypass, or administer locks. The main permissions are:
- stickylocks.lock – Allows a player to claim blocks and manage access lists.
- stickylocks.locksmith – Grants the ability to modify or unlock other players’ claimed blocks, ideal for staff.
- stickylocks.ghost – Lets a player open or use any locked block, ignoring restrictions without changing ownership.
- stickylocks.reload – Permits reloading the plugin’s configuration from disk without a server restart.
All commands are accessible via /stickylocks or its alias /sl. After selecting a block with the wand, you can use these essential commands:
/sl show– Displays the current block’s owner and the list of players and groups with access./sl add <player|group>– Adds a player or group to the block’s access list./sl remove <player|group>– Removes a player or group from the access list./sl group <group>– Lists all members of a group./sl group <group> add <player> ...– Adds players to a group./sl group <group> remove <player> ...– Removes players from a group./sl group <group> rename <newname>– Renames a group or merges it into an existing one./sl clearselection– Deselects the current block, same as right-clicking air./sl reload– Reloads the plugin configuration from disk.
Configuration and Customization
The config.yml file is refreshingly minimal. You can edit the protectables list to add new block material names as Minecraft updates introduce them. The tools setting changes the wand item (default STICK), and chatprefix adjusts the tag that appears before plugin messages. Because the plugin uses material names rather than deprecated IDs, future-proofing is built in. If you ever need to change settings on a live server, simply use /sl reload—no restart required.
Pairing StickyLocks with Other Protection Plugins
StickyLocks intentionally focuses on interaction control, not block destruction. This design choice makes it an ideal companion to region-based plugins like WorldGuard, Towny, or Factions. Those plugins handle preventing griefing and block breaking, while StickyLocks manages who can open chests, flip levers, or press buttons. The heuristic detection mentioned earlier ensures that if a player cannot build in a region, they cannot lock a block there either, preventing exploits. For servers that need destruction prevention at the block level, the companion plugin StickyProtection fills the gap by stopping players and pistons from breaking locked blocks and adjacent supports.
Why StickyLocks Remains a Solid Choice
In a landscape crowded with all-in-one protection suites, StickyLocks stands out because of its simplicity, UUID reliability, and dynamic group management. It does not try to do everything; it excels at one thing and integrates cleanly with other tools. The wand-based selection feels intuitive, and the color-coded feedback reduces confusion for players. Whether you run a small community server or a large network, giving players the power to lock their own doors and chests while staff retain oversight through the locksmith permission creates a balanced, self-managing environment. The plugin’s SQLite backend also means you can script external tools to query lock data if needed, adding a layer of transparency.
Overall, StickyLocks delivers a focused, dependable solution for per-block access control on Bukkit servers. Its group system saves time, its compatibility with modern UUID-based servers keeps things stable, and its open-ended design encourages pairing with other protection plugins to build exactly the security model your server needs.