Lock Security
LockSecurity! The easiest to use container protection plugin on Bukkit! This plugin allows the ability for you to lock your containers with a key, and only be able to open the container if you have the key in your hand! There is no way that the chest can be accessed by another user unless they have a key with the ID binded to the block you have locked. IMPOSSIBLE to access any functions of the locked block
The plugin is simple to use and get started. First, all you have to do, is craft yourself a rusty old Unsmithed Key. If you right click on a lockable block, that chest and the Unsmithed Key you right clicked with, will be assigned a unique ID in incremental order. All information about the locked block is neatly stored in an SQLite lckinfo.db file inside the LockSecurity folder in your server files. No one will be able to access the contents of that chest... unless... they attempt to open the chest with the key that was binded to it. Simple as that! I know, you're probably thinking, "But why not just try and break the chest and get the contents inside?". That's been thought of. If you are not the owner of the chest (the player who locked it in the first place), you will not be able to break it. What about explosions? That's okay... all locked blocks are explosion resistant! :D No more need to hide your chests! What about doors and redstone? That's though of too! Redstone doesn't open or close locked blocks!
This plugin is highly configurable, including per/world block lock limits, recipe result yieldings, and even a list of blocks that can be locked. As of version 1.5.0, there is an external API which has been fully documented on a BitBucket repository where the source code is privately backed up. If you're a developer, and you would like to create an add-on for LockSecurity, please scroll down to the "LockSecurity API / Add-Ons" section, and hack away!
There are a few commands to help administrators manage this plugin. There are of course a couple of missing features from these commands, and there will be more added in the future. You can view all command references and their related permission nodes by -= Clicking here =-
There are a few permission nodes that should be taken notice of. Although they are very minor, and already have reasonable default values for servers that do not have permission manager plugins, please read the permission node guide page for reference to what they all do. You can view all permission node references by -= Clicking here =-
The following recipe will get you an Unsmithed Key, which can be used to lock a lockable block. This recipe is semi-shapeless. It requires the same format, however not in the same shape. As long as the recipe is in a straight line (or diagonal), the iron bars are on the opposite ends of the wooden plank, and the iron ingot is in the center slot, the recipe will work
Please view the following page on how to use any of the configuration options if they are not already clear, by -= Clicking Here =-
Thank you to AbsintoJ, MrUrica123, and LtJim007 for making such amazing videos explaining how the basic and key features of the plugin works. AbsintoJ has made one in Portuguese, MrUrica in French, and LtJim's video is in English. It gives you a visualization of what the plugin will be like when you install it. Unfortunately, AbsintoJ's is quite outdated to version 1.1.1 of LockSecurity, but again, not a big deal ^-^. LtJim's video was released when version 1.6.1 of the plugin came out, and most recently MrUrica released his video in version 1.8.1.1. I hope you enjoy the videos!!!
As of version 1.5.0 of LockSecurity, there is a very extensive API that has full documentation. If you are a developer interested in creating add-ons for LockSecurity, please, I highly encourage you to do so! I would love to see some neat little add-ons for this plugin, and perhaps even use them! If you create a LockSecurity add-on, do not hesitate to inform me over PM on BukkitDev, Twitter (found below), or in the comments of LockSecurity. Doesn't matter how detailed it is, as long as it's an add-on, I would love to hear about it, and I will list it here :D
I have created an add-on for LockSecurity to show the true power of the new API. It is called LS-ChestCollector! Using locked chests, you can create wireless collection systems, to collect the items you specify in the command when you pick them up! You can check this add-on out by -=Clicking Here=-
About the API. If you would like to know how to actually code an extension to the LockSecurity plugin, go ahead and head over to the BitBucket Wiki page which can be found by -= Clicking Here =-
Perhaps you have an idea for something that should be added? An idea to improve my plugin at all? Or maybe you just have a bug that I couldn't seem to figure out. If you have anything listed above, make a ticket! I get e-mail notifications for when you create a ticket, and I will get to those a lot faster than a comment on my post. That also helps me organize many of the suggestions and bugs I've had in previous versions. Tickets are always preferred over comments, but if you just wanna be nice and rate this plugin based on your usage, feel free to leave a comment instead
This is a list of servers that have the Lock Security plugin installed. If you would like to try out the plugin before downloading it and putting it on your server, feel free to try it out on one of these. If your server has this plugin installed, leave the IP address in the comment, and I'll add it to the list when I have the chance!
As a highschool student, I am very busy and will only be able to work on this when time is available to me. I will make this plugin very interesting, and continue updating with as many features as I possibly can. However, eventually I will run out of gas, and not produce any ideas. Leaving a ticket with suggestions for this plugin is always encouraged if you want to keep this project alive. Thank you for all of the support on this plugin, for the very few of you that are supporting it. Numbers don't matter to me, so I'll keep producing content as long as at least one person is downloading this plugin. Enjoy
I have created a Twitter account specifically for development updates and feature sneak peeks for all of my plugins. I will be posting updates about where I'm at on plugin updates, and open to suggestions on this social media website. If you have a Twitter account and would like to get in contact with me, my development Twitter handle is @2008Minecraft It will be full of sneak peeks for you all to drool at until I fully release it. You'll also get tweets every time I publish an update for a plugin, so keep an eye on that as well ;) Social media is not a necessary, but only optional if you want to know a few things before others do
I work really hard on my projects to try and produce the best updates as I possibly can. As a new and aspiring developer, I am still looking for some means of support for future school endeavors, and getting lessons to code professionally.
If you would like to donate and help support me, that would be very much appreciated. My plugins are not pay-to-play, and donating is simply optional. If you can't support me through monetary means, please feel free to comment instead <3 Anything helps.
1.12
none of the commands work
they just return a message like if I put in
/givekey <name> <#>
it will say
/givekey [player] [count]
I cant seem to get this to work with a spigot server
is there any reason it shouldn't?
conflicts maybe?
Hi great plugin.
But can you add way lock picking minigame.
and a tier system for the minigames so the higher the tier the higher the difficulty of the minigame.
and a admin command that makes a lock not pickable.
Thanks.
Could you add a way to lock more than one block with the same key ID?
I want to have a sort of "master key" that Unlocks all the doors and chests in my base, without having to fill my inventory with keys.
In reply to Goncorer:
Hello, it's me TheAddictedGamer6790, I'm contacting you regarding me uploading an updated version of my plugin review on my YT channel for the latest version (1.8.2) and testing it on Minecraft 1.11.2 spigot. It worked this time :)
Check it out: Click me!
@resoluciones
Absolutely! There is a modifiable block list in the configuration file. Simply remove all blocks excluding CHEST (and TRAPPED_CHEST if you so chose), and you should be all ready to go :D
congrats for the plugin
would it be possible to only allow players to protect chests?
@poiNt3D
I'll see what I can do. The rewrite is almost complete and the API is much more flexible not only for me, but for other developers as well. I will see what I can do ^-^
Can you please add ability to translate item names and lore for keys and unsmithed keys? And, maybe custom recipe?
@owenftw
@Adragondil
Thank you very much! ^-^ Glad you enjoy it
Great plugin!
Good plugin!
@Sir_Cam
Version 1.8.1 :D
"Fixed being able to pull items from locked inventories out of hoppers"
And what about if i place a hopper beneath it? Would the items flow out of the chest?
@kvgeorge1
Awesome! I was not looking forward to debugging a 1.8.1.2 xD
Thank you very much! Whatever you did resolved the issue. The new version does not throw the error anymore.
@kvgeorge1
I just released an attempt to fix this issue. It shouldn't happen anymore I don't believe. Try out version 1.8.1.1 and let me know if that fixes it. If it doesn't, I have no clue. It's seemingly difficult to attempt to fix a bug that is not occurring on my own server
I am running the latest version of 1.9.2 Spigot and still getting the same error:
Could this have anything to do with it?
http://wiki.bukkit.org/Scheduler_Programming#Tips_for_thread_safety https://www.spigotmc.org/threads/asynchronous-entity-add.3526/
@kvgeorge1
I believe that's an issue with your Spigot version. It looks as though it's having issues adding entities to the world upon world initialization. I'd say try and update your Spigot version, and let me know if this continue to happen. Unfortunately, my console fails to yield this exception, so it's quite hard for me to debug. As of currently, that line has nothing to do with worlds or entities at all.