[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


    Bubka3 reported no issues above, but you can do a verification for yourself.

    I'm watching for reported issues in 1.3.1 rather than testing it myself.

    There are a number of plugins that Lockette will try to link to if they are loaded, plugins that provide definitions of 'groups' or 'permissions' or 'zones'. This configuration option was added to prevent accessing an external plugin, if it is causing problems either now or in the future.

    Eg, if a future update of a plugin starts to make Lockette throw exceptions, due to an api change, it can be disabled with the config option.

    There were reports that the groups provided by the mcMMO plugin were causing a security issue within Lockette, and I understand that no one really used it for Lockette groups, so it is in the ignore list by default.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  3. using this now and works like a beauty.
  4. Offline


    I can still report this is working fine with a dev build as well.
  5. Offline


    I'm translating the language file from English to Swedish, but can't get the Å, Ä and Ö letters to show correctly ingame. Have saved the .yml file as UTF-8 but still no result...

    What can be done to get this to work?
    When checking the YAML parser online, the Å, Ä and Ö letters turns into: Å - \u00e5 Ä - \u00e4 and Ö - \u00f6

    If I get this to work, I will post the download link on the Lockette forum!
  6. Offline


    I'm not sure how the others did it but you can check the other translations for examples. I'm no Unicode expert. :3

    Send it to me in a conversation so I don't loose it. Or better yet, add it to the repository yourself here, if you know how:

    With new languages being added, I've noticed some issues in some of the existing translations.
    (Possibly due to a change in the yml parser in the past.)

    I'm working on a language-only related update now.

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


    Sounds pretty good!
  8. Offline


    Hej TheMineKraftor!

    I have just done a translation to swedish that I'm running successfully. I used "Notepad++" to edit the .yml, it worked great. I'm abut to have my sister proofread it. (She is a "lågstadielärare".) If you like you can proofread it to. Or I can proofread yours.

    Best regards Magnus Fransson.
  9. Offline


    I've been using lockette ever since I made my first server, Can't remember when that was I think it was about the time enchantments first came out but I just want to say lockette is the best plugin I've ever seen (Protection based) well other then logblock but this works with logblock so it does not matter, anyhow I've not used other chest protection plugins but I've seen them on servers and I just love how lockette is not command based and so simple to do! Love the timer feature too.. example [timer:02] no idea what I would do with out it. So yeah just a big thanks for making the plugin!

    Not sure if you have already done it or not but what would be a great new feature for lockette and would help my server a lot is if you make is so as well as adding a username on the 3rd and 4th line but you could also make groups command based and put it on the sign, ex.. Pretend theres a shop on my server that I don't want to have a portal leading there just a walk in deal but I only want a "Premium member" to enter (like someone who donates to the server) I do something like {/lockette create group Premium} then I enter a node into permissions like lockette.Premium then I add to the shop door on line 3 [Premium] so whatever group (or user) I give that node can enter the shop, Then put a timer on the door so only he can enter, the only problem will be that a Premium member could open the doors for a Member too so if there was a way to stop that it would be great too!
  10. Offline


    Can you add so if someone that's not the owner can't break the sign so they wont get griefed,i switched over to lwc cause of the greifers breaking the signs when i was off and griefing
  11. Offline


    1. Punctuation.
    2. Lockette does what it can to prevent a non-owner from breaking the sign. It works really, really well once it is configured for your server. But if you do not have permissions setup correctly or you allow players to delete the signs with something like WorldEdit, then there's nothing that Lockette can do. You've basically given them permission to break signs.
  12. Offline


    Groups are already supported, but lockette doesn't have groups on its own. It links to other plugins for groups.

    See the list at the top of the OP.
    Groups are specified as [Groupname] on the sign, no matter which external plugin provides.

    What Grey said above, plus my own comment;

    You should be warned that if a conflicting plugin is allowing people to destroy Lockette signs, it may also allow people to destroy LWC chests.

    You can find his translation in the Lockette 1.7.4 release. If you have any corrections to make to the file, do so and add your name as an editor. Then you can send me the update, or alternately you can update the file on github yourself.

    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 havent got this yet but will others be able to destroy the signs
  14. Offline


    1. I don't give a fuck about my punctuation
    2.why are you doing these # things
    3.and i have group manager and i did have them configured perfectly but it still wouldn't work so.....you should just ask questions,like well did you have permissions or group manager?...and not acting like a smart ass so good day

    hmmmm well. i got lwc and it worked fine but i do trust lockette.i had complaints on my server,i set up the permissions just fine in group manager,and still it was so i whent to lwc and it worked....no configureing for a long time and then i configured it to my liking and it's been working ever since,but i do love this plugin....i might even try it with both since thay can work together

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


    Lockette protects all blocks needed to maintain security, including signs, but excluding sand/gravel falling under doors.

    If it is a conflicting plugin, it is not so much a configuration issue as it is removing the bad plugin from your server. Let me know if you find a culprit. (Eg, do you use VanishNoPacket?)

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

    Parker Mckinley

    [SEVERE] Could not load 'plugins/Lockette.jar' in folder 'plugins'
    org.bukkit.plugin.InvalidPluginException: java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:155)
    at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:305)
    at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:230)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:222)
    at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:198)
    at net.minecraft.server.ServerConfigurationManagerAbstract.<init>(ServerConfigurationManagerAbstract.java:50)
    at net.minecraft.server.ServerConfigurationManager.<init>(SourceFile:11)
    at net.minecraft.server.DedicatedServer.init(DedicatedServer.java:105)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:380)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
    Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:676)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41)
    at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:317)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:242)
    at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:144)

    Thats What mine says please help!:(
  17. Offline


    Try updating your java runtimes? And just to be sure, what build of Bukkit are you using?
  18. Offline


    You are more likely to get help if you are polite, and if people can understand you. Punctuation helps people understand what you're trying to say.

    Your original question was "Can you add so if someone that's not the owner can't break the sign so they wont get griefed..." Lockette already does that, when properly configured. I'd offer a sample set of permissions, but I don't use GroupManager. You might check the Advanced Setup (Permissions) section at the top of the thread for more information about how to correctly setup permissions.

    Good luck!
    Michael Erikson likes this.
  19. Offline


    Okay, look i was a little harsh on you, and i know my punctuation, grammar,and spelling is bad. Group Manager is just like permissions just a little different,and i realized i could fix it so only the owner of the sign can break his own sign. But ill stick with LWC, because all the people on my server now how to use it more than this plugin,even though i love this plugin very much I have to stick with the other one.As you can see I'm trying really hard to keep my chat right. ;)..... And yes I can be a dip shit sometimes when they're is something wrong with my server.
  20. Offline


    i am an op, permissions is set to false in the config, admin snoop and admin bypass are both set true, but i cannot open locked chests.
    This server is running CraftBukkit version git-Bukkit-1.3.1-R1.0-b2320jnks (MC: 1.3.1) (Implementing API version 1.3.1-R1.0)

    Lockette v1.7.4
  21. Offline


    why should that stop them from people using a download link on the plugin page?
  22. Offline


    Please add a ticket to the bukkitdev ticket tracker so I don't forget to look into this, though it should be simple enough to check. :3

    I didn't remove the download link, an admin did while I wasn't around.

    In any case, ElgarL now has the proper permissions needed to fix if something happens in the future.

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


    I own a faction server and we love lockette, is there any way that someone can possibly picklock the chest to receive the items? or a plugin that works with this?
  24. Offline


    You could add to the discussion here: http://dev.bukkit.org/server-mods/lockette/tickets/21-suggestion-for-faction-plugin-servers/

    Also if you could teach me more about how factions is used it practice, it may help. I never did come up with a satisfactory answer in regards to Lockette in a PvP environment, but if something can be figured out it can be added.
  25. Offline


    i got lockette but then it says in console cant load plugin lockette wat do i do[sheep]
  26. Offline


    That's nice! I tried to save it in Notepad++ aswell, but I still can't get it to work...
  27. Offline


    Try updating java runtimes?

    There is an option to set which format to save as in N++. I'm using ANSI at the moment, as trying to use UTF-8 causes the raw text to be shown in MC. I'm not sure if this was due to a change in MC or the yml parser within bukkit.

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


    Acru could there be an option to only view whats inside a locked the chest but not edit the contents. That would be perfect for my moderators.
  29. Offline


    BoorMachine I'm not speaking for Acru, but what you're asking for seems like a small change to Lockette... but it isn't.

    If you're already using VanishNoPacket, a vanish'd moderator can have view only and silent access to chests.
  30. Offline


    I just had an interesting idea for a how a lockpicking game might work, for Lockette in pvp worlds. o3o
  31. Offline


    Can you please make it so you have to put [Lockette] on a sign when you try claim a diamond block because I have to keep making it so I don't have permission to use lockette on a diamond block so I can add a sign like Spawn This Way or something like that..

    Also while your at it you could also make it so you can claim gold and iron blocks with a sign that has [lockette] on line 1.. Not that I ever have used lockette to protect my diamond blocks.. I always put them in chests if I'm lucky enough to find them then put lockette on the chest

    Just noticed you can protect any block in the config so forget about what I said about that part

Share This Page