This update focuses on closing critical security loopholes related to Minecraft physics and redstone mechanics. We highly recommend all users update to this version to ensure maximum protection for their players' containers.
Changelog
Fixed Piston Exploit: Locked containers (Chests, Barrels, Shulker Boxes, etc.) and their attached signs can no longer be moved or retracted by Pistons or Sticky Pistons.
Fixed Gravity/Physics Exploit: Resolved a bug where signs could be "popped off" as items by dropping gravity-affected blocks (like Sand or Gravel) onto them or by updating the blocks behind them.
Improved Sign Stability: Added logic to prevent signs from breaking when the environment undergoes a physics update, provided the parent container is still present.
Added Robust Null Checks: Improved the code to handle sign-line detection more safely, preventing rare internal console errors when interacting with blank signs.
Config Update: Added new message nodes for piston and physics denials to keep players informed.
️ Key Features
Piston Proof Protection Blocks pistons from pushing or pulling locked containers and their signs. Thieves can no longer use redstone to steal your chests!
Anti-Gravity Security Prevents sand, gravel, and other falling blocks from breaking lock signs. Your protection stays intact even if someone tries to use physics exploits.
Smart Merge Protection Prevents players from placing a chest next to a locked one. This stops the "double-chest merge" exploit used to bypass locks.
Explosion Immunity Locked containers and signs are 100% immune to TNT, Creeper blasts, and any other entity explosions.
Action Bar Alerts Receive real-time, non-intrusive feedback. Instead of cluttering the chat, lock status messages appear smoothly above your hotbar.
Advanced Hopper Blocking Prevents unauthorized item extraction by blocking the placement of hoppers under or around locked containers.
⚙️ How to Update
Download the ChestLocked-1.2-FIX.jar.
Replace your old JAR in the /plugins/ folder.
Update Config: Either delete your old config.yml to let a new one generate, or manually add the piston-denied and physics-denied lines from the documentation.
Restart your server.
Need Help? If you encounter any issues with the new Piston or Physics protection, please reach out via the discussion tab or our support channel!