LockettePro
LockettePro 2.2.0 - UUID Support
High performance sign-based lock plugin, highly customizable
Moved to Spigot... Please follow link:
https://www.spigotmc.org/resources/lockettepro-uuid-support.20427/
Quick Links
Download | Configuration | Wiki | GitHub​
Transfer between Lockette & LockettePro​
What is LockettePro?
Remember the sign-based lock plugin Lockette that is popular for years? LockettePro is a deep remade & rewrite of the original Lockette. It has massive performance enhancement, fixed bugs and very customizable. LockettePro's behavior is 100% same as Lockette. You may switch between those plugins anytime.
Why LockettePro?
I am deeply depressed with the original Lockette. Its codebase is messy, performance is bad, unnecessary checks are everywhere... It also uses legacy deprecated methods, having a piston-related bug for years... It is not very possible to fix all the issues, so I started to start a brand new plugin. And today, I am proudly to present you the ultimate sign lock plugin, LockettePro.
LockettePro - Pros
- No database. All information required for a lock is recorded on the sign.
- Switch to LockettePro and switch back to Lockette worry-free anytime.
- Absolutely better performance. Performance test comparison below.
- Language files are editable, with UTF-8 support.
- Able to disable "bloat" features easily with no affect to performance.
- Customizable. For instance, you can set lockable for every single block.
- Original Lockette's UUID support is not actually working between server restarts, just saying...
LockettePro - Cons
- Lack of admin snooping alert and I am not likely to add this soon.
- (Seems like I have resolved every other cons, great!)
LockettePro vs Lockette Performance - Using Timings v2
This test is focused on the most serious performance issue caused by hoppers InventoryMoveItemEvent. The event happens when hoppers are trying to pull items from the container above. Test is performed on my server with a monstrous Chest-Hopper rig consisting 10000 sets of locked chest and hoppers.
Lockette: 41.8 microseconds per event
LockettePro without cache: 19.4 microseconds per event
LockettePro with cache set to 10 seconds: 4.3 microseconds per event
How to Use LockettePro?
The usage of Lockette and LockettePro are exactly the same. For players, just hold a sign in your hand, then right click a chest or any lockable block. If you want to lock a door, you may put a sign on the block above or below the door too. You may also SHIFT+RIGHT CLICK the block to prevent it get automatically locked, or you can write [Private] text manually on signs as well. After locking, you may add a second sign on chest/block will add a [More Users] sign so you can add more users to a chest/block. In order to add another user name on a sign, first right-click to select a sign, then enter /lock <line number> <name>. For server owners please take a look at the configuration below.
Commands and Permissions
Main command is /lock. Aliases contains /lockit, /lockette and /lockettepro.
- Edit a sign: lockettepro.edit /lock <line number> <player> to add a player to the sign.
- Reload configuration: lockettepro.reload
- Admin break lock: lockettepro.admin.break
- Admin use block (snoop chests): lockettepro.admin.use
- Admin override placing interference blocks: lockettepro.admin.interfere
Configuration
Source
https://github.com/connection-lost/LockettePro
Supported Plugins
WorldGuard & Residence:
If a player does not have the "break" permission to a block due to WorldGuard or Residence, then he cannot lock it.
Towny:
If a sign has a user line formatted "[TownName]", this means any player in town "TownName" will have access to this chest. Players are not allowed to lock a chest in the wilderness unless he has permission lockettepro.towny.wilds
Factions:
If a sign has a user line formatted "[FactionName]", this means any player in faction "FactionName" will have access to this chest.
Other plugins:
Some plugins are born to compatible with Lockette/LockettePro thanks to Bukkit's event priority mechanics. Players are not able to lock a chest/block that has already protected by another plugin. Known compatible plugin includes ChestShop.
Braggins
The goal of LockettePro is to deliver a high-quality, and high performance sign-based lock plugin that can completely replace original Lockette. Like LockettePro? Missing features? Issues or bugs? What can I help to make it better? Leave a comment in the discussion, I want to know!
- My English is not very good, if I made some errors please don't laugh at me :)
I have found a weird bug where fence gates can't be locked next to each other, here's a clip I recorded of this bug
If it isn't a bug please let me know :)
I know this may be hard to implement, but would there be a way for the chests to automatically realize if a player changed its username? I changed my username, and now all of my chests on my minehut server are locked for me. Now i have to wait 30 days to change it back.
In reply to debtisbad:
If you are OP, you can just break the signs. If you aren't OP, ask an admin that is willing to help you.
when will this come out for 1.14?
I have problems installing lockette in aternos
someone can help me pls? c:
Hello. i have an issue with being able to lock chests in a worldguard'd region.
steps to reproduce: install lockette and worldguard and worldedit. test that lockette works on a chest bydefault. then select and define a region with worldguard using a woodenaxe and /rg define xxxx. test lockette again with all default settings on everything. does not work, and i have all admin prermissions and op.
to go further, giving normal users rights to break and build blocks does not work either, even though they can place and take away the chest just fine and use it too. however placing a sign on the chest is greeted with "you cannot use lockette on this chest" and i don't know why. i've enabled all flags i could think of and it still doesn't work... and its not permissions because even i have all permissions and it still doesn't work.
i've been looking around for hours for anything on this and not one single forum post about using worldguard and lockette together. only in worldguard's page it mentions to use lockette instead of its chest thing and here, says just to give players rights to break blocks. none of that helps.
minecraft version 1.11.2. worldguard 6.2 (the one that supports 1.11.2 because the lastest version does not and would not work.) and most recent version of lockette from this exact page.
is there any suggestions to try... or a known fix for to be able to use worldguard with lockette?
I have a suggestion: Group Inheritance.
So say I put on a sign, [mod] as a permitted user. Mods can now access the chest. But Admins, who inherit the mod group, cannot. I want Admins to inherit the permission to enter that chest.
If you're worried about compatibility, I obviously don't know how the plugin is written but, you could have say, [mod]+ to give all ranks that inherit mod to use it, and leave [mod] with no inheritance.
On Spigot 1.11.2 I can't open locked iron doors unless I'm holding a block. This happens with original Lockette as well. It might have to do with the event listener being called twice, I remember having an issue like that with ScriptCraft on 1.9.
Also, I immediately disabled the quick protect feature, because it means you can't place signs over doors, and I like to label my doors. And shouldn't you at least send an admin a warning message when they bypass a door?
And what's the permissions to actually allow players to use Lockette...? When they place a sign on a chest they get [ERROR] with 'You cannot lock this' error in chat.
This plugin is definitely one of the essentials, but we've found an issue in that permissions are not extended to SignShops - players that don't have Lockette permissions on a chest can link the chest to their own shop and buy/sell items. Can this be prevented?
Thanks!
i want this feature for my donor ranks so how can i remove lock permission from my members?
Are there any economy / limitations that this plugin uses? I'd love to use it on Herocraft RPG, but I really cant if its unlimited.
Missing Feature:
The old lockket had [OP] lock signs so only ops can open it
Works on 1.9.4 perfectly, no issues :)
how do I request features? would I put that as an issue on github?
Using Spigot 1.9.2, This Plugin is working great without any issues for my use. Thank you. Will report if issues are found.
@frankwu
More on that idea, the money should go to the first person on the sign, the maker of the sign. If a locked door/chest doesn't have the fee tag, it works as normal. A permission node for adding the 'fee' tag would be useful. I also think it would be a good idea to have a confirmation message for paying the fee since i know people would hide the sign and charge ridiculous amounts of money.
I really wish I had found this sooner. I'm very excited. However, I have a request.
The original Lockette had some things in the strings file that indicated there would be a fee option. If I could add a fee to a door/chest so that anyone not listed on the sign could use it for a fee, using iconomy / Vault, I would be so happy.
@zainmz
Sure, but I don't think there is a reasonable solution to effectively "REMOVE" a lock after a certain amount of time. Instead, the lock will be "ineffective".
We had a discussion about this here.