[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


    Never had a problem with this plugin. I have used this since 1.8.1 and now at 1.1. Great Job and keep up the good work!
    10/10 - A Necessary Plugin for any server in my opinion.
  3. Offline


    Lockette is broken for me.

    CB - 1.2.3-R0.1

    [SEVERE] Could not load 'plugins\Lockette.jar' in folder 'plugins'
    org.bukkit.plugin.InvalidPluginException: java.lang.NoClassDefFoundError: org/bukkit/event/block/BlockListener
        at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:148)
        at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:287)
        at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:211)
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:207)
        at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:183)
        at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:53)
        at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:156)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)
    Caused by: java.lang.NoClassDefFoundError: org/bukkit/event/block/BlockListener
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(Unknown Source)
        at java.security.SecureClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.access$100(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        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(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at org.yi.acru.bukkit.Lockette.Lockette.<init>(Lockette.java:33)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:144)
        ... 8 more
    Caused by: java.lang.ClassNotFoundException: org.bukkit.event.block.BlockListener
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        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(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 27 more
  4. Offline


    Can you make it so OPS/Admins can open locked chests...got to make sure no one griefed
  5. Offline


    I was wondering where I could find a list of permission nodes for lockette? I need them to config permissions please
  6. Offline


    Perhaps instead of not paying any attention, you could notice it's been updated, download the updated version and let that fix your problem?

    They are in the OP of this thread...

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


    ok thanks
  8. Offline


    he made it work for 1.2.3
  9. Offline


    There are some * shortcut perms listed in the plugin.yml too (inside the jar), though they may not be working right for some.

    Thank you~
  10. Offline


    Give your admins lockette.*

    Jeez, why are some of you so damn stupid. Read the original post.
  11. Offline


    [quote uid=12037 name="Acru" post=1002071]I don't see an attached file, sorry. Can you put it somewhere and send a link?[/quote]
    Well, i see it attached, anyways heres on Mediafire: <Edit by Moderator: Redacted mediafire url>
    Last edited by a moderator: Dec 15, 2016
  12. Offline


    exploits: sticky pistons pull locked trapdoor and bonemealed trees break chests or signs
  13. Offline


    Still a top notch additive to the server! Always keep up the great work Acru!
  14. Offline


    Working perfectly in 1938 on a heavily modded bukkit with a crap ton vanilla mods.

    BTW that feature you said you would consider in the future. The big one was Iron Chests mods. It acts exactly as a normal chest (even the block size where you can see down the edges) accept it has about 5 diff chests and they use damage value's so if that feature does get added all we need is maybe terms called metadata so we can add example 181:2

    There is also a really crazy reenforced door acts exactly like iron doors for nuclear meltdowns to help protect people on the outside. It looks pretty bad-ass and so that be a .nice one we love to customize hehe.

    Thanks :)
  15. Offline


    Suggestion: Make it work with factions, say instead of putting other users name down you could put in [(faction)] of yours or a allied clan so that all of you faction members/allied clan members could use the door/chest whether or not you are in your faction area.
  16. Offline


    giantfood are you saying that it is not currently working with Factions? I don't use it, but according to the Features list: Core: Factions support for groups. (And fixed it again.)
  17. Offline


    I dont use towny and I dont want to restrict where you can use the lockette chests, but I do want to reduce the amounts placed to prevent very ugly spam (like people only buying collecting wood and only placing hundreds of unremovable chests )

    And since keeping a counter of the chests per user, to limit the amount of users requires a database and has a lot of impact on the performance, this is not really a good option.

    But asking a configurable amount of money to make a chest use lockette limits the amount of chests a user can place without having to save his amount of chests into a database. Therefore it will perform very fast only when creating a case it will have to lookup if the user has enough case. But this is only on creation and for one specific user so the database query is very fast.

    So I think the best idea is to implement a variable in the config with a price to make a chest use lockette. Its not much work either, if you use Vault.
  18. Offline


    Can you support Towny so that a plot owner can break someone elses lockette chest if it is on there plot?
  19. Offline


    My memory may be playing tricks on me, but I'm pretty sure he said in the past that he wouldn't support that due to a risk of abuse. For example, player A places a locked chest full of diamonds in unclaimed land, player B finds the chest and then claims the land so they can destroy said chest and steal it's contents.
  20. Offline


    How to disable the message when you open someone's door, I did it last version but i don't remember how. Its really bothersome seeing that red message "You have opened blahblah's door please close it behind you!"
  21. Offline


    im not that dumb lol. Im using the latest build of lockette!
    Edit: Restarted my server with a whole fresh build and no more errors.
  22. Offline


    You can enable this if you configure Towny correctly. Tell it to remove signs when someone does a /plot clear, and it will kill the Lockette signs. Of course, it might kill signs you don't want to destroy but that's the best you can do.
  23. Offline


    Are you sure? Just the version released two days ago works fine with build 2034 (the 1.2.3-R0.1 Beta Build).
  24. Offline


    I'll double check sticky pistons, but bonemealed trees are fixed in 1.5, for MC 1.1 and 1.2.3. Builds older than R6 I can't reliably fix for.

    I believe the trouble with the trees started with a certain commit, but I'm not sure exactly where it first appeared.

    I need Jenkins to find it. :<

    A fee for locking something is planned and the support for it is in place, though it is not yet implemented.

    (There isn't a specific version goal set for this feature.)

    This could be the case, but I don't know enough about how Towny ownership works to know the best way to deal with the issue, tbh.

    If there is any specific message you don't want to see, set it to "" in the strings.yml

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


    Does it support Minecraft 1.2.3 yet?
  26. Offline


    Tested only up to build 2034 but yes.
    Sorken likes this.
  27. Acru
    "[Lockette] This zone is protected by towny.wilds."

    I have tried giving the node lockette.towny.wilds. Still it will not allow placing protections in the wild. What am i doing wrong?

    Edit: And suddenly, after about 20 zillion reloads it just starts working.. must be PEX related.
  28. Offline


    Thank you for that.
  29. Offline


    None of my users can create locks except me. I deop myself and put myself in the same permission group, and I am able to create locks just fine, but no one else can.

    Sorry forgot to mention, i'm using cb2034 and Lockette 1.5
    This is my config:
    Show Spoiler
    enable-messages-user: true
    enable-messages-owner: true
    enable-messages-admin: true
    enable-messages-error: true
    enable-messages-help: true
    explosion-protection-all: false
    enable-chest-rotation: false
    enable-permissions: true
    enable-protection-doors: true
    enable-protection-trapdoors: true
    allow-admin-snoop: true
    allow-admin-bypass: true
    allow-admin-break: true
    enable-quick-protect: true
    enable-color-tags: true
    default-door-timer: 0
    broadcast-snoop-target: ''
    broadcast-break-target: '[Operators]'
    broadcast-reload-target: '[Operators]'
    strings-file-name: strings-en.yml

    EDIT: Ok works perfectly fine now. It wasn't you it was groupmanager, which is broken in all incarnations in 1.2 (I'm now using PEX for the first time in my life lol)
  30. Offline


    It protects my doors but people are able to glitch in by spamming it after some time and holding forward. any ways to prevent this?
  31. Offline


    I thought that Acru had added a fix for that in a previous version. The new internals must have changed enough to un-fix it. I know he's planning another release soonish... maybe this can be a part of it? *poke*

    My opinion - I have zero tolerance for this sort of exploiting. It is better to get rid of those kinds of players than to spend all your time playing policeman. Treat the cause, not the symptom. Your whole world will be better for it.

Share This Page