[SEC] Lockette - Simple chest and door lock, no databases! [Moved to BukkitDev]

Discussion in 'Inactive/Unsupported Plugins' started by Acru, Feb 14, 2011.

  1. Offline


    Lockette - The sign-based container and door lock for Bukkit! - by Acru Jovian

    ElgarL has been assigned as the current maintainer of this project, please forward any important issues to him as well. This post is abandoned, but proceed to BukkitDev for updates.

    Download it at BukkitDev! (Alternate) (JAR) (Source), also view the Change Log on BukkitDev.

    Supported external plugins:
    • Permissions - Permissions/Groups
    • GroupManager - Permissions/Groups
    • PermissionsBukkit - SuperPerms/Groups
    • PermissionsEx - SuperPerms/Groups
    • bPermissions- SuperPerms/Groups
    • Towny - Groups/Zones
    • SimpleClans - Groups
    • mcMMO - Groups (Disabled by default now, due to issues.)
    • Factions - Groups
    • LWC - Zones
    • Register - Economy
    Alternate languages included:
    Confirmed compatible plugins: ColorSign, SpeedSign.
    Conflicting plugins: ChestShop, Most sign editors!

    The active Lockette information page will commute to BukkitDev soon, but the forum thread is still the best place for discussion.


    The purpose of this plugin is to restrict access to the contents of chests, dispensers, furnaces, and doors without the use of a database to track containers.

    To use, simply place a signpost on the floor directly beside a chest or other container to be locked. Enter [Private] as the first line. Your own name will automatically be entered on line 2 as the chest owner. Optionally type in the full names of two other users allowed to access the chest's inventory on lines 3 and 4.

    When done correctly, the sign will automatically fix itself to the side the target chest, protecting it from unauthorized access! Only the chest's owner can then break the sign or chest. (Warning: Anyone with permission to use WorldEdit commands or similar can circumvent the protection by removing the sign.)


    Additionally, you can enter [Everyone] on lines 3 or 4 instead of a user name to allow everyone access to the contents of a private container, or [Operators] to allow ops access. If a Permissions plugin is available, you can use groups like [Moderator] or [Admins] or others as defined in the Permissions settings files.

    The owner of a container can add more users by placing additional signs beside the container with the heading [More Users], where lines 2-4 specify the names of the additional users. You can edit the users on previously placed signs by right clicking the sign, and using the command '/lockette <line number> <text>' to change it.

    Working with Doors:

    To protect a door, you can use the same method as protecting a container, the sign will attach to the door automatically. In addition, you can attach a [Private] wall sign to any side of the blocks just above or just below a door. For double doors only one side needs a sign. Door support is enabled by default in the config file.

    Once a door is protected it will only open for someone listed as a user, and will not respond to redstone power or switches unless [Everyone] is listed as a user. Iron doors which usually won't open from clicking will work just as wooden doors. In addition, double doors will open together automatically!

    You can also use [More Users] signs as with containers, with the caveat that the sign cannot be placed on the block above the door if the [Private] sign is not above the door as well! (This is done to prevent a security uncertainty issue.)

    Protected doors will be closed automatically if a timer is set. A timer can be set globally with a configuration option, or individually for each door by using the tag [Timer: #] on line 3 or 4 of the [Private] sign, where # is the number of seconds that the door should remain open. If the timer is set to 0, this means the door will never automatically close. If no timer is specified, protected doors will use a global timer set in the configuration file. If the server is shut down cleanly any open doors will be closed, but in the event of a server crash while a door is open, it may remain so. Note that the initial state of a door is assumed to be closed.

    Care must me taken to place protected doors on a stable block. Building a door on sand, gravel, leaves, TNT and et cetera are allowed by the plugin, but cannot be secured fully. :3 Additionally, it should be noted that most status messages still refer to locked blocks as containers, so for the purpose of simplicity, doors should be considered as a type of container.

    • No passwords or databases needed!
    • Permission checks run in constant time, no matter how many protected containers.
      • One owner and up to 11 additional users supported. (17 for double chests!)
      • Allows access to [Everyone] while still protecting the container from vandalism.
      • Allows group names in conjunction with many other plugins.
    • Special powers for ops or admins, configurable with permissions.
      • Reports when an admin does something naughty.
    • Protects single and double chests, dispensers, and furnaces.
      • Explosion and block-break protection for the protected container and sign.
        • Option to protect all containers from explosions.
    • Full support for doors, both wooden and iron!
      • Double doors are handled automatically, with no redstone.
      • Doors can be set to close automatically, via a timer setting.
      • Redstone hacking is disabled for protected doors.
    • Prevents creation of chests larger than 2 blocks.
    • Informative or helpful messages when interacting with containers.
      • The first time a chest is placed, a help message will be shown.
      • Types of messages shown are configurable in settings.
      • Additional language support.

    Advanced Setup (Permissions) (open)

    Advanced Setup:
    There are a few things you can now customize in the configuration files for the plugin, found in the plugins/Lockette folder. After running the plugin for the first time, two files will be created, config.yml and strings.yml. The first holds the following settings:
    • enable-permissions - Allows the use of permission nodes to specify who can do what. If this is disabled, groups will still be used but admin status is taken from the ops file. Defaults to false.
    • enable-messages-* - Enables or disables groups of messages listed in the strings.yml file. Not counting the broadcast ones.
    • broadcast-*-target - Sets the group or player that specific broadcast messages should be sent to. This can be set to "" for no one.
    • explosion-protection-all - Enabling this extends explosion protection to all containers on the server, not just [Private] ones. Default is disabled.
    • allow-admin-bypass - Allows admins to go though any protected door. Default is true.
    • allow-admin-snoop - Allows admins to peek into chests owned by other people. Default is false, and this setting is recommended! A broadcast message will be sent each time an admin snoops in a protected container where the admin doesn't have permission to. The message will be sent to a player or group as specified in another option. Admins can still break protection on chests if this is disabled, however.
    • enable-protection-doors - Enables support for private doors, defaults to true.
    • default-door-timer - Sets the door closing timer for all protected doors on the server, unless overridden by a specific sign. Defaults to 0, which disables the door closing timer.
    In the strings.yml file, you can set alternate language tags for [Private] and such, in ANSI format. If you need characters not in ANSI then you might try UTF-8 format, though it seems bugged tight now. The default alternate tags are in French, but server ops are free to translate the whole file into the language of their choice. If you do this, please share it back to me~ :3 If you want to disable only a specific message, you can set it to "", the empty string. Admins can use the command '/lockette reload' after editing the configuration files, to reload them.

    If a Permissions plugin is not available or the enable-permissions option is set to false, Lockette will use the ops file to determine who are admins. Admins can break the protection on any chest, and look inside protected chests (only if the related option is set), as well as reload the plugins configuration files. All non-ops will be able to create protected containers for themselves.

    If a Permissions plugin is available and the enable-permissions option is set to true, the following nodes will be used instead of the ops file and are included by default in the '*' node:
    • lockette.user.create.* - Permission required to create a protected container or door. Possible sub-nodes include chest, dispenser, furnace, and door. (The permission lockette.create.all is still supported, but obsolete.)
    • lockette.admin.create.* - Allows admins to create containers and doors for other users. Possible sub-nodes include chest, dispenser, furnace, and door. Leave line 2 blank for the default behavior or enter the name of your choice. Capitalization matters.
    • lockette.admin.break - Allows breaking protection on containers.
    • lockette.admin.bypass - Allows opening of any locked door.
    • lockette.admin.snoop - Allows peeking in protected containers. (The setting allow-admin-snoop must be true.)
    • lockette.admin.reload - Allows use of the reload command.

    Technical Information (open)

    Technical Information:

    This plugin has been tested and shown to be working for many builds of CraftBucket though a number of the more recent builds had a serious issue, so I'm suggesting a minimum build of 561 now. If you update past what is listed in the post's title and the plugin seems to break, it is probably not my fault. Post a note anyway and I'll see about fixing. I'll try and keep up with the new recommended build system, but for latest builds that break things, you should expect some time to pass before I take care of the issue, as this plugin is now mature. :3

    If there are multiple containers by the placed sign, the plugin will use the NESW rule to choose the first container that is not yet private. To elaborate, the plugin will check to the north of the sign first, and if no container or door is available to the north, it will continue checking clockwise around the sign.

    Due to the current implementation of the explosion event, this plugin will cancel all explosions that would damage the container or sign, rather than just remove the container and sign from the blocks to be damaged. Canceled explosions still knock signs off the walls. Canceled explosions leave signs looking blank, but this is just a graphic glitch, reconnect to fix.

    Bonus: This plugin will prevent chests bigger than 2 blocks from being created via glitches. (Again, this could be circumvented using WorldEdit commands, so take care who has access to such a plugin.)

    This plugin was inspired by the old hmod plugins Lock by Roman "kingseta" Pramberger and ChestCapsule by Fernando "Fergo".

    Hooking into Lockette (open)

    Hooking into Lockette:

    If you are a plugin author and want to connect to Lockette, you can use a public static function to get information about the protected status of a block.

    More info later, perhaps, but if you need the details now then go poke through the source~

    Future Possibilities:

    There are a number of things that have been suggested, and they tend to be added to the list below if I think they might be a good idea. However, some sort of locked container limit is requested often but this is not possible without a database to track the number of locked containers someone has. All things considered, this will not be supported. On the up side, without a database you can have literally millions of locked containers without any sort of lag, and there are permissions to restrict who can create locked chests. Perhaps only allow Moderators to create locked chests for other users, if you don't want to allow infinite locked chests.

    Aside what has already been implemented, the following may or may not appear in future versions:
    • Furnace/dispenser clusters, protected by a single sign.
    • [Log] sign to list recent users of a container or door.
    • iConomy fee for protecting containers/doors.
    • Worldguard connection.
    • [Protected] tag for viewing only.
    • Specific time range that doors can be opened.
    • DataLog plugin support.
    • More types of protected blocks, such as brewing stands.
    If you want any of the above features sooner than never, let me know! However, I currently see Lockette as functionally complete, for the most part, in that it already has all the functionality it needs. Future updates will mostly be to account for changes in Minecraft and Bukkit.

    Final Note:

    Please leave a reply if there are any bugs or suggestions, and if you like this plugin you can click the like button at the bottom of this post~ Thanks to those few that have donated! [​IMG]
  2. Offline


    lol. FAIL. You are 100% correct.

    new test! Now with 100% more fencegate!
    Inscrutable likes this.
  3. Offline


    Is there a possibility to place a hook in Lockette or make a config setting so we can add extra blocks ID's used as chests?
    My server has a mod installed, it adds 3 diffrent chests: iron, gold and diamond
    (It is an Industrialcraft² addon)
    Thanks for your attention.
  4. Offline


    All the commands are doing nothing with the version 1.4.9 beta...

    Could you fix that ?
  5. Offline


    I'd advise you to:
    1) confirm that Lockette is actually installed. Check your server logs for "Lockette" entries.
    2) set yourself to Op to test it
    3) configure permissions as appropriate for your server
  6. Offline


    Yeah, I thought it was me at the start too and then checked all those things, it was driving me nuts.
    But in the end I narrowed it down to a conflict with WorldEdit (Tested 5.0 and 5.1-Snapshot).

    When WorldEdit is loaded as well, none of the commands work for Lockette. Lockette still thinks it working and interacts with sign placement, but no commands respond. Tested with just the two plugins on CB 1.0.1

    Let me know if I can help with any more info ;)
  7. Offline


    Hm... sounds like a good test. What commands are you trying to use? I just did a quick test... the version and line editing commands worked just fine.
    CB 1619 & 1648, WorldEdit 5.0. Lockette 1.4.9b
  8. Offline


    Thanks for the quick Reply Greylocke. It looks like I told a lie, but narrowed down the problem better.
    I am running CB 1597, Lockette 1.4.9.b and WorldEdit 5.1 Snapshot(s).

    I thought I swapped my WorldEdit with 5.0, but I actually only swapped between two different 5.1 snapshots. WorldEdit 5.0 does not cause the problem, only the WorldEdit 5.1-dev.

    With WorldEdit 5.1-dev, Lockette does not response to any commands. Even typing /lockette by itself does not list the commands. I am using WE 5.1 on our server because I found 5.0 to have a few bugs (/SP area with drop many items caused the server to reboot etc). Any ideas? Or is it not something you can address until the final WorldEdit 5.1 Release?
  9. Offline


    1) Installed - we can lock our chests
    2) I am Op
    3) There's no permissions plugin

    I'am testing with Zero plugins but only Lockette... to see if another plugin is blocking the Lockette commands.

    Result : "/lockette" is doing nothing.

    So, for now, if we want to edit a sign, we have to remove it and replace it near the chest with the new lines...
  10. Offline


    Will there be PermissionsEX support? I tried using a PEX group in a sign and it didn't recognize it.
  11. Offline


    Hi Acru,

    I use Bukkit 1597 and your Plugin works great, but i can't add users of the Sign whit "More Users" on line 2-4.


    I have the Plugin reloaded as i upgraded of the newest version.

    But after the auto restart from the server, it full work.

    Nice WORK. THX :)
  12. Offline


    I am currently only allowing ops to create locked chests for users and this works fine, the only thing that I have noticed, is that once a chest is owned by someone, the owner is than allowed to add a "More Users" sign to the chest, is there a way to restrict owners of chests from making "More Users" signs?

    Also is there a way that I can prevent an owner of a chest from editing the chest sign?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  13. Offline


    i get this error while using bPermissions but idk if it's from Lockette or other plugin
    05.01 11:36:17 [Server] SEVERE     at java.lang.Thread.run(Thread.java:722)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.craftbukkit.scheduler.CraftWorker.run(CraftWorker.java:34)
    05.01 11:36:17 [Server] SEVERE     at com.earth2me.essentials.storage.AbstractDelayedYamlFileReader.run(AbstractDelayedYamlFileReader.java:38)
    05.01 11:36:17 [Server] SEVERE     at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    05.01 11:36:17 [Server] SEVERE     at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:24)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:32)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.JavaPluginLoader.getClassByName(JavaPluginLoader.java:221)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:36)
    05.01 11:36:17 [Server] SEVERE     at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    05.01 11:36:17 [Server] INFO [dynmap] Using Permissions 2.7.2 for access control
    05.01 11:36:17 [Server] SEVERE     at java.security.AccessController.doPrivileged(Native Method)
    05.01 11:36:17 [Server] SEVERE     at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    05.01 11:36:17 [Server] SEVERE     at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
    05.01 11:36:17 [Server] SEVERE     at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
    05.01 11:36:17 [Server] SEVERE     at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
    05.01 11:36:17 [Server] INFO [Lockette] Enabled link to plugin Permissions for Groups, version 2.7.2
    05.01 11:36:17 [Server] SEVERE     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    05.01 11:36:17 [Server] SEVERE     at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
    05.01 11:36:17 [Server] SEVERE     at java.lang.ClassLoader.defineClass1(Native Method)
    05.01 11:36:17 [Server] SEVERE     at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    05.01 11:36:17 [Server] SEVERE     at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:24)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:32)
    05.01 11:36:17 [Server] SEVERE     at org.bukkit.plugin.java.JavaPluginLoader.getClassByName(JavaPluginLoader.java:217)
    05.01 11:36:17 [Server] SEVERE     at java.util.HashMap$KeyIterator.next(HashMap.java:841)
    05.01 11:36:17 [Server] SEVERE     at java.util.HashMap$HashIterator.nextEntry(HashMap.java:806)
    05.01 11:36:17 [Server] SEVERE java.util.ConcurrentModificationExceptio
    EDIT:I fixed that error(it was something wrong with my world.yml from bPermissions)
    but i still get this error after the server says "Done"

    05.01 11:48:48 [Server] SEVERE     at java.lang.Thread.run(Thread.java:722)
    05.01 11:48:48 [Server] SEVERE     at org.bukkit.craftbukkit.scheduler.CraftWorker.run(CraftWorker.java:34)
    05.01 11:48:48 [Server] SEVERE     at com.arandomappdev.bukkitstats.CallTask.run(CallHome.java:97)
    05.01 11:48:48 [Server] SEVERE     at com.arandomappdev.bukkitstats.CallTask.postUrl(CallHome.java:128)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1296)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:846)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:928)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:992)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.http.HttpClient.New(HttpClient.java:316)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.http.HttpClient.New(HttpClient.java:300)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.http.HttpClient.<init>(HttpClient.java:213)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.http.HttpClient.openServer(HttpClient.java:483)
    05.01 11:48:48 [Server] SEVERE     at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
    05.01 11:48:48 [Server] SEVERE     at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
    05.01 11:48:48 [Server] SEVERE     at java.net.Socket.connect(Socket.java:528)
    05.01 11:48:48 [Server] SEVERE     at java.net.Socket.connect(Socket.java:579)
    05.01 11:48:48 [Server] SEVERE     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
    05.01 11:48:48 [Server] SEVERE     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:176)
    05.01 11:48:48 [Server] SEVERE java.net.UnknownHostException: bukkitstats.randomappdev.com
    05.01 11:48:48 [Server] INFO Could not call home.
    05.01 11:48:47 [Server] INFO Could not call home.
  14. Offline


    One of your plugins is trying to report some usage stats back to its Developer. To stop it, open the config.yml in the "stats" folder and set "opt-out" to true.
  15. Offline


    thanks man that stopped it!your the best
  16. Offline


    Just a bit of an update in my investigating, the incompatiblty with WorldEdit 5.1 starts with this build:

    And then continues on until the most current build.
  17. Offline


    interesting. I don't know why WE would interfere with Lockette, but I bet @sk89q & team would be able to put their finger on it pretty quick. Have you posted anything on the WE forum, redmine, or irc?
  18. Offline


    Yeah, I just made a post in the WE forum just then. In build #704 they made changes to the WorldEditPlayerListener and dynamic command registration, which seems too much of a coincidence to by unrelated.
  19. Offline


    There is a glitch to get past doors now. If you rapidly click the door you are able to slip though. Many people on my server have started switching to iron doors because of this. Can you please fix this glitch? I have an idea on how it can be fixed too, you could make it so you can click the door thats locked once but if you click it again in the same minute you will lose health. If you did this people couldn't get past the wooden lockette doors. Thank you.
  20. Offline


    I found a major bug. I noticed people where getting robbeb and stores where getting destoryed. And I found out why. If you place a fence gate under the chest it unlockes it. Please fix it! Love the plugin but cant take my server members getting robed.
  21. Offline


    Top line. Red letters.

    Notice: The fence gate exploit was fixed in version 1.4.9, please update.

    Patch Lockette. Ban exploiters. The world is a better place.
  22. Offline


    I was wonder if you could implement a way to lockette workbenches.
  23. Offline


  24. Offline


    Can i suggest add a option to disable protection for locked chest if get blast by tnt.
    thanks :D
  25. Offline

    xT3Cno HUNT3Rx

    Hey i have a idea for lockette: is their any way of adding a option so no one can break a sign only the person who placed it also when you have a sign on a chest it cant break unless the person who put the sing on the chest.
    I think you should do this, this is a excellent plugin But the thing that lets it down is people can destroy the chest or sign. I know it shows a message to every one when one is broken but it would be easier to stop them from being able to break it. What i am asking for is not hard to do i have seen plugins what do this and they are simple i don't know the name but its about a bed plugin.
  26. Offline


    How do you stop admins from going through doors?
  27. Offline


    @xT3Cno HUNT3Rx , @lilkitty99 These functions are available by setting your permissions and config appropriately.

    To prevent players from breaking signs, do not set lockette.admin.break. (Of course Ops can do anything, so if your players are Ops, there is nothing you can do to stop them.)

    To prevent admins from going thru doors, in the config set allow-admin-bypass to false or in permissions do not set lockette.admin.bypass for your admin group.

    c'mon people. Read.
  28. Offline


    I have a problem where my chests will continuously open and close sometimes when I open them.

    Also, could you add where pressure plates activate doors? For example, if I have access to that door it should open for me and it would make this plugin that much better if I could open multiple doors by touching one pressure plate then walking on the other side which would close them both. :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  29. Offline

    xT3Cno HUNT3Rx

    @Greylocke i don't have permissions and i cant get it to work on my server also most permission type plugins ether fail or lag the crap out of servers. a lot of people complain i know about 10 people who don't use permissions due to lag and before any one says o its poor internet, get a better computer ooo. That's not the solution my mate owns a gaming computer worth over £1000 it can run multiple games at one without running slow, minecraft and a server is a walk in the park with his computer. the multiple games he can play is MW3,minecraft,HALO reach, BF3, F1 2011, MW2, COD 4, dead island i don't know why he does it but of course he cant play all at once tho.
  30. Offline


    @xT3Cno HUNT3Rx I'm not going to try to disprove your experience with permissions managers, but there exists a large body of evidence that runs contrary to your opinion, as there are literally thousands of servers running permissions. Like them or not, permissions managers are the key that unlocks practically every plugin's features.

    I'd encourage you to give permissions managers another try. I can recommend both PermissionsBukkit and bPermissions with Lockette. I don't have any experience with PEX.

    @Helladen I had a similar issue, but I don't have it now. I'm pretty sure that after I updated craftbukkit & spout that the problem went away. I'm currently running cb1648 & spout657. You might try updating to at least those versions and see if your problem goes away, too.
  31. Offline

    xT3Cno HUNT3Rx

    @Greylocke hey i have a question can you use bother plugins together (PermissionsBukkit and bPermissions).
    Also do you have any experience with servers because at the moment im making a map for a server and what some tips and/or help setting it up. Like how you change the name from your IP x.xxx.xx.xx to like xT3CnoCraft.com or something like that and how can you host it without it running on your computer and is their any thing im missing?

Share This Page