[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


    is there a config set up? i need it to base it off what i have! thanks!

    you need to make a sine above the door, i found that will do it. and it must be enabled in the config
    Line 1: [Private]
    Line 2: YourUserName
    Line 3/4: OtherUserNames

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


    Hello. I'd like to help you with the translation file for Romanian. Can you PM me ?
  4. Offline


    To look doors (including iron doors) you have to place the sign above or in front of the door you want to lock, and type on the first line: [Private]
  5. Offline


    Hi everyone.

    im having issues with lockette and dont know of any real way to fix it. basically its not letting users place new signs. existing ones work and protect but new ones are working at all. oddly the signs can still be places on chests but it give no option to fill it in. if i place signs in front its stays in ground and doesnt turn into a sign.

    additionally perms are off
  6. Offline


    It's because of Towny which includes the changed API, we have to wait for Acru to update Lockette for us. It's quite critical, no one in Towny servers can create new protected chests now.
  7. Offline


    Hey i'm having problems in-game with lockette, say i place a sign above a door and type [private] then next line my name, done. try and open door fine and it all works, but when trying to attach a sign to a chest it either wont attach via placing it adjacent to the chest with [private] , name. However when i hit the chest with the sign, the sign does attach to the chest however doesn't show up any sort of private message, the sing is blank. Been trying to fix this myself for about three hours now checking if it conflicts any of my plug-ins, i understand it supposedly doesn't like Chestshop plug-in yet a large server i play on runs both Chestshop and Lockette, anyway i removed chestshop to see if this was the problem but it still didn't fix it, i've had Dev's from the large server trying to fix it and we just can't understand why, your my last chance :9 here's a list of my plug-ins:
    my server runs: CraftBukkit version git-Bukkit-1.2.5-R1.0-b2149jnks
    Lockette loads fine, and in-game it gives the messaging telling me how to create a locked chest, i just can't seriously need your help, Cheers, Ben.
    p.s As i'm using PermissionEx do i need to turn allow-permissions to true on the lockette config?
    BTW i'm new to all this :p
  8. Offline


    If you are using the latest Towny, then their are various issues. Lockette has to update the code in order to fix this.
  9. Offline


    Is there a way to prevent zombies from breaking locked doors in hard mode?
  10. Offline


    So is there a way of getting the previous towny, in order for it to work properly?
  11. Offline


    superdupernova lockette cannot hold back the zombie horde. Use iron doors (lockette will open iron doors without redstone), fence gates, or some sort of piston thingy.
  12. Offline


    Very Nice Plugin GJ !
  13. Offline


    Yes. If you go to the bukkit dev, then click 'Files' at the top, it will show previous and present files. Just click an older version, and then download it.
  14. Offline


    Would love the ability for cluster locking, many of my players tend to have walls of furnaces and it would really help out.
  15. Offline


    Yeah, that's what people tend to be doing on my server. However, using a ton of iron doors gets costly and annoying, and it'd be nice if Acru added an option.
  16. Personally, I don't think it should stop zombies.

    Villagers 'lock' their doors at night, otherwise zombies wouldn't be trying to break them down, right?

    If this ability is added, I hope that's it's something that can be turned on and off. Lockette was designed to keep honest players honest (and help prevent theft), I don't think it should be able to block part of the game, there are other plugins for that. :)
    nunber1_Master likes this.
  17. Offline


    whenever i try to lock a chest this comes up
    13:48:55 [SEVERE] Could not pass event SignChangeEvent to Lockette
    at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:303)
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:459)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:1265)
    at net.minecraft.server.Packet130UpdateSign.handle(SourceFile:41)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
    at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    Caused by: java.lang.IncompatibleClassChangeError: Expecting non-static method com.palmergames.bukkit.towny.object.TownyUniverse.isWilderness(Lorg/bukkit/block/Block;)Z
    at org.yi.acru.bukkit.PluginCore.canBuild(PluginCore.java:614)
    at org.yi.acru.bukkit.Lockette.LocketteBlockListener.onSignChange(LocketteBlockListener.java:614)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:301)
    ... 10 more
    13:49:06 [INFO] [Lockette] patrick_is_kool has released a container.
    do you know how to fix it?
  18. Offline


    If you are running Towny, it is because the developers of Towny changed some code. In order for Lockette to work, they have to update their code.
    I explained that to my players, and they are living with the bug (for now). If it is a big issue, then downgrade Towny.
  19. Offline


    Hi, I love lockette and I have been using it since I started my server (which is old) and one of my players on my server can't lock doors because his name is too long. He can with chests (right clicking chest with a sign that will automatically place & lock it) but not on doors. I am hoping there is a possible fix for this! (like you could right click on a door with a sign and it would automatically lock it as with chests) this would be amazing if you could fix it, thanks!
    nunber1_Master likes this.
  20. Offline


    adding to this, what you should be able to do is (if the name is too long) have
    Line1: [Private]
    Line2: Partoflongname-
    Line3: -isrighthere
  21. Plugin Approved With ------> craftbukkit-1.2.5-R1.2... :D
  22. Offline


    Slightly late considering R2.0 came out today. :p
    nunber1_Master likes this.
  23. Offline


    Please make it so that we can disable the plugin in certain worlds! Thanks!
  24. Offline


    You could just remove the permission nodes from people on the worlds you don't want it used on.
  25. I Have create the alternate language Italian :D ... Next i post the link of Download...

    Have you got a plugin Towny? mhm this is a problem..

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


    Hey, I'm learning a Italian. Here is a tip on the English language (did you use google translate? I think you did :p). Anyway, instead of link of download, we say download link. Instead of Menu of Kitchen, we say Kitchen Menu. :)
    Yes, this is a Towny issue. It is because Towny changed it's code. There are now incompatible code between Lockette and Towny. Downgrading Towny fixes this issue.
  27. Offline


    Thing is, per-world-permissions doesn't work for me. :/
  28. Offline


    I have the same problem with towny the signs just keep blank
    but they said you need to wait till lockette updates to 1.2.5 for it to work
    Or download deadbolt ????? i am not so glad if i need to do that i know how lockette works now and i think its one of the best plugins ever made!
    nunber1_Master likes this.
  29. Offline


    What permissions system are you using that it doesn't support multiworld perms?
  30. Offline


    You have the use-permissions set to true in config?
  31. [quote uid=90420 name="nunber1_Master" post=1125702]Hey, I'm learning a Italian. Here is a tip on the English language (did you use google translate? I think you did :p). Anyway, instead of link of download, we say download link. Instead of Menu of Kitchen, we say Kitchen Menu. :)

    Yes, this is a Towny issue. It is because Towny changed it's code. There are now incompatible code between Lockette and Towny. Downgrading Towny fixes this issue.[/quote]
    Thanks =).. apologize I'm Italian ... this is the download link : <Edit by Moderator: Redacted mediafire url>
    Last edited by a moderator: Dec 15, 2016

Share This Page