Locker
Locker protects your inventories (chests, hoppers, furnaces, ender chests, etc.) against the wrath of other players.
- Minecraft 1.8 ready!
- Access Protection
- Break Protection
- Explosion Protection
- Hopper Protection
- Custom Labels
- Easy usage
- No database required
- Performance optimized
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Installation |
---|
- Download Locker and extract the Locker-<version>.jar file into your "plugins/" folder.
- Download ProtocolLib and extract the ProtocolLib.jar into your "plugins/" folder.
- Download Vault and extract the Vault.jar into your "plugins/" folder.
- Give out permissions (optional; full list available below; give locker.* for all).
- Run your server and Locker is installed.
Migration |
---|
Version 1.2.0 introduced support for UUIDs. This change comes along with some slight changes to the backend which require a migration. However this migration happens automatically the first time a user accesses a chest which is still using the old format. Please note that the current migration process will only work as long as name changing is still impossible. That said opening all protected chests at least once after updating is highly recommended (even though the migration process might change in the future).
To simplify this process a color-code has been added to all protections: If your name on the protection sign is blue, the migration has finished and the sign has been updated internally. Is the player name displayed red, a migration is still required.
Development |
---|
You are interested in working on the next big thing in the Bukkit/Spigot universe? No problem! Feel free to fork our repository at GitHub to get your changes added to the official Locker builds.
Usage |
---|
To create a protection you will need to place a sign anywhere near to the inventory you'd like to protect (above, below, left, right, in front, behind). The sign needs to contain the following text:
[Locker] <Label> <Username> <Username>
The first line always needs to contain the "[Locker]" prefix. The second line optionally contains a label. The third and fourth line contain the owner username (you will only need to use the fourth line if your username is too long to fit into only one line. In that case you will need to split up your username into both lines (e.g. "no" and "tch" will turn into "notch")).
Commands |
---|
This plugin does not have any commands.
Permissions |
---|
- locker.use - Allows to protect inventories.
- locker.override - Allows to override protections and create protections on behalf of others.
Metrics |
---|
This plugin utilizes Hidendra's plugin metrics system, which means that the following information is collected and sent anonymously to mcstats.org:
- A unique identifier
- The server's version of Java
- Whether the server is in offline or online mode
- The plugin's version
- The server's version
- The OS version/name and architecture
- The core count for the CPU
- The number of players online
- The Metrics version
Opting out of this service can be done by editing plugins/Plugin Metrics/config.yml and changing opt-out to true.
Learning More |
---|
- Project leader: Contact @HighLordAkkarin on Twitter
- Lead developers: Akkarin
- Project started: In April 2014
does it have configuration that can be breaked by explosion ?
@CosmoConsole
LoL
[Locker] <Label> <Username> <Username>
Is it possible to add 'friends' to a lock (such as allowing others to access a chest)? Also, can doors be locked?
@NiceFinal
Both the Hopper and Chest have to be locked for Hoppers to correctly work. ;-)
Hi,
How can i setup a chest allow transfer by hopper and lock the chest
@Sage905
Hey,
to be honest with you I'm not quite sure what you changed apart from code formatting ...
Found a bug with UUID processing and a couple of other ones, related to permissions handling.
Unfortunately, I also committed a "hack" to my fork. I don't have time to create a branch, and extract the hack right now, but you can have a look at my commits, and see what I've changed: https://github.com/ptoal/Locker
-Sage
Hey, thanks for the plugin. As a plugin dev myself, I appreciate anyone who takes the time to code/share a plugin, especially with source available.
I will be trying this with Towny, instead of Lockette. I'm hoping that Towny can still destroy these sign locks. Since you've made the source available, I will make a patch, if I run into problems.
Cheers, Sage905
@Bars96
Please keep such comments to yourself. If you think locking inventories via a sign is an original idea, then you're sadly wrong.
I wrote this plugin for my own server just because I want to know what is running on the server and how much lag it causes. You should be thankful that people upload such plugin as open source and free of charge on this platform. You will probably thankful for the replacements which do nearly the same when one plugin goes inactive.
Yet another MachineGuard Reloaded parody?
@MarioG1
So far name changing is not a thing in the Minecraft universe (even though an implementation has been announced and might become available soon). But as far as the information on that topic goes, I'm pretty sure the current implementation will not break even though a player changes his/her name. Even though the method of creating a protection might have to change in future versions due to changing player names.
To your second question: Yes chests are indeed protected against hoppers or any other kind of automation in the game. Hoppers (in block form) are also able to move items if they are protected by the same player. Hopper carts as example are not able to access any protected blocks.
Update: The change to UUIDs will definitely break this and many other plugins. Currently there is sadly not enough information on this topic. Thus we will probably need to wait until something breaks before an update is possible. As I will probably migrate the protection storage (from signs to XML and possibly SQL) in the upcoming versions to support more specific access rules for inventories this change will go along with the existing migrations. But please do not expect a smooth transition. It's not the fault of plugin developers. There is just no clear information and to quote EvilSeph: "the changes are purely based on guesswork". We will see what will happen. Just prepare for the big bang when Mojang flips the switch ;-).
I have tow questions:
How do you handle/store the UUID of an player to support name changing?
Are locked chests protected against hoppers/hopper carts?