SecureChest

Requires Paper 26.2 and Java 25. Minecraft 1.21 is no longer supported, please stay on version 1.6.0 there. ChestSecure is built and tested for Paper 26.2. Other server forks may work but are not supported.

Added

• Protection area: admins define rectangular areas where locking is possible. Locks outside are removed when the switch is turned on, an area shrinks or is deleted, and the owners are notified.
• Recipe editor for the Chest Key in the admin panel, including how many keys one craft gives (1 to 64).
• Secure Hopper through the Chest Key: right click a hopper that faces a container you locked to turn it into a Secure Hopper. Sneak and right click it with the Chest Key to turn it back. Breaking it drops a normal hopper.
• Admin panel: a button for Chest Keys, a switch for the owner name display, a switch to hide covered names and a switch that makes every new lock cost one Chest Key (off by default).
• Admin menu for single locks: sneak and right click a locked container with the Admin Key to remove it, transfer it or change its trusted players. The owner is notified when the lock is removed or transferred.
• A better chest locator: arrow relative to your view, height hint, and the container glows for you while the ping runs.
• Every player can switch the name above their own locks off, and a name is hidden while a solid block covers the text.
• Furnaces, blast furnaces, smokers, droppers, dispensers, brewing stands, crafters and copper chests can be locked now. Copper golems cannot take items from or put items into locked containers.
• A short message when a lock click is ignored because of the cooldown.

Changed

• Owner names are shown once per group of connected locks of the same owner on the same level, centered above the group.
• The log browser shows names instead of UUIDs, and its action filter covers the new admin and area actions.
• The Chest Key only works for the owner of a lock, also for operators. Admins use the Admin Key and the admin panel.
• Chunk loading no longer scans every lock. The plugin keeps an index from chunks to locks, which keeps owner names fast to restore on servers with many locks.

Removed

• The Secure Hopper item and its recipe. Existing Secure Hoppers keep working, and crafted Secure Hopper items can still be placed. recipes.secure_hopper in config.yml is ignored, and the log says so once.

Fixed

• Double chests: locks could get lost when a second chest was placed next to a locked one, and the check against placing next to someone else's lock now works in every case.
• The plugin did not start with an invalid recipe in config.yml. Invalid recipes log a warning and are skipped.
• Unlocked chests and hoppers no longer cause database lookups on the main thread.
• Owner names and player names in menus show the player name instead of a UUID after a restart or while the player is offline. This bug also affected older versions.
• Owner names reappear after a chunk is unloaded and loaded again.
• Undoing a lock transfer restores the previous owner in the database and no longer overwrites a newer lock at the same position. The owner dialogs ask again after a typing mistake.
• Chest Keys and Admin Keys can no longer be placed as tripwire hooks.

Known limitations

• Redstone can still make a locked dropper, dispenser or crafter hand out its items. Locks protect against players, not against redstone.
• Locked droppers and crafters do not pass items into containers. Only Secure Hoppers move items out of locked blocks.

Update notes

• Back up plugins/ChestSecure before updating.
• config.yml is never written by the plugin, and an existing config.yml keeps working as before. Admin panel changes are stored in areas.yml, recipes.yml and settings.yml.
• The plugin adds the table player_names and the column show_owner_name to the table player_settings in chestsecure.db.
• Admins who used the Chest Key on other players' locks now use the Admin Key and the admin panel.
• Older versions could store a lock on the neighbouring chest when double chests stood next to each other in a row. After the update such a lock belongs to the chest it is stored on, so please check chests in dense chest rows.
• Copper chests change their block type when they oxidize or are waxed, a lock stays valid when that happens.

Full changelog: https://github.com/crimethunder1/SecureChest/blob/main/CHANGELOG.md All configuration keys: https://github.com/crimethunder1/SecureChest#readme