ChestLockLite: Container Protection and Lock Management

Securing player storage against theft or griefing is an essential requirement for survival and multiplayer worlds. ChestLockLite provides container security by letting players safeguard chests, barrels, hoppers, and furnaces without requiring heavy external database dependencies. All records are handled locally while blocking environmental risks such as explosions, hopper siphoning, fire, and piston tampering.

Locking Containers and Managing Passwords

Players can safeguard an individual container by targeting it and running /chestlock lock or the shorthand /cl lock. This assigns private ownership so only the locking player can open the inventory. Granting chestlocklite.use and chestlocklite.lock allows ordinary members to protect their storage blocks.

When shared access is required among allies, owners can apply a credential using /chestlock password with a chosen passphrase, protected by chestlocklite.password. If a password is no longer needed, running /chestlock removepassword strips the restriction. Players can also verify the status, protection state, and current ownership details of any targeted container with /chestlock info, which requires chestlocklite.info. To inspect or manage settings through a visual menu, users who possess chestlocklite.gui can open the interactive interface.

Trusted Companions and Administrative Controls

Beyond shared passwords, players can delegate permanent rights to specific friends through the trust system when given chestlocklite.trust. Once trusted, friends interact freely with the owner's locked storage without repeatedly typing credentials. Removing a player lock entirely is done with /chestlock unlock, requiring chestlocklite.unlock.

Server staff require tools to inspect disputed claims and resolve abandoned builds. Operators hold chestlocklite.admin, which permits administrative lock overrides. Staff can remove an individual lock with chestlocklite.admin.clear, wipe every container registered to a specific player across the server via chestlocklite.admin.clearall, or purge every lock within a defined boundary using chestlocklite.admin.cleararea. Configuration adjustments are reloaded using chestlocklite.admin.reload. For staff members who need to inspect container contents without breaking existing locks, the chestlocklite.bypass node grants passive access while remaining disabled for normal players by default.