[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


    GameFreakWithPower no, it was not updated for use with minecraft 1.2.4.

    In fact, I don't know of any plugins that needed to be updated to work with 1.2.4. All the ones that I use or have read about just worked with 1.2.4. No updating required.
  3. Greylocke
    Well some of them do, Im guessing, Like worldedit and such. So what you are saying is that all of my stuff should work normally? Hmm Il have to try this thankyou
  4. Offline


    GameFreakWithPower even WorldEdit seemed to work OK, you just needed to use the codes for the new blocks. There was an issue with spawning jungle-style trees, but that was a bukkit issue, not WorldEdit. And there was a duping issue with protected blocks... but again it was a bukkit problem that has since been resolved with a newer craftbukkit dev build.

    Of course, if you do find a 1.2.4 issue, please post it! :)
  5. Offline


    I was not aware~

    I'll have to look into it, to see if Bukkit provides a way to block npc from opening doors.
  6. Offline



    How can i make it so tnt CAN blow open the chests?

    If it can't which plugins will allow me to do this?

    Thanks jack.
  7. Offline


    Could you try to add a feature where anyone can enter your doors, but for a fee, that would be cool
  8. Offline


    Can you change the Default "[Operators]" To just "[Ops]"?
  9. Offline


    aaronfranke check the strings file (default is strings-en.yml). Look for the "alternate-operators-tag: " item. Change the value from Operators to Ops.
  10. Offline


    Hi, are you aware of an item duplication bug with this?
  11. Offline


    petern if you're referring to an issue with protected blocks still dropping an item, that was an issue with craftbukkit, and it was fixed with CB2117. If you've found some other exploitable bug, please PM Acru with the details to help prevent abuse.
  12. Offline


    any ideas how to lock a chest for someone who's name is too long for the sign?
  13. Offline


    I did that but i thought it would be nifty if it was the default for lockette. Or at least [Ops] and [Operators] could both work by default

    Get him a shorter name.

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


    I am noticing when players break their signs in 2117, they seem to get more then 1 sign back. Not sure if has to do with the duplicate bug, but no other player is getting a duplicate bug but this one mentioned.
  15. Offline


    Here you are, a french tutorial made in 1.1 that you can put in your post :
  16. Offline


    Lockette your version has some big mistakes in the German language! I have written abetter German version and would be happy if she performs it on your site.
    Here it is:
    alternate-private-tag: Private
    alternate-moreusers-tag: More Users
    alternate-everyone-tag: Everyone
    alternate-operators-tag: Operators
    alternate-timer-tag: Timer
    alternate-fee-tag: Fee
    msg-user-conflict-door: Widersprüchliche Tuer entfernt!
    msg-user-illegal: Verbotene Kiste entfernt!
    msg-user-resize-owned: Du kannst die Breite der Kiste von *** nicht veraendern.
    msg-help-chest: Bitte setze [Private] neben eine Kiste, um sie zu schuetzen.
    msg-owner-release: Du hast ein Objekt freigegeben!
    msg-admin-release: (Admin) @@@ hat ein Schild von einer Kiste von *** genommen!
    msg-user-release-owned: Du kannst das Objekt von *** nicht freigeben.
    msg-owner-remove: Du hast erfolgreich einen Spieler vom Schild genommen!
    msg-user-remove-owned: Du kannst keine Spieler vom Schild von *** entfernen.
    msg-user-break-owned: Du kannst kein Objekt von *** zerstoeren.
    msg-user-denied-door: Du darfst diese Tuer nicht benutzen.
    msg-user-touch-fee: 'Ein Betrag von ### wird an *** bezahlt, wenn du dieses Objekt benutzt.'
    msg-user-touch-owned: Dieses Objekt wurde für *** freigegeben.
    msg-help-select: Schild wurde ausgewaehlt, benutze /lockette <line number> <text> um es zu bearbeiten.
    msg-admin-bypass: Tuerschutz von *** wurde umgangen!
    msg-admin-snoop: (Admin) @@@ hat in eine Kiste von *** hineingeschaut!
    msg-user-denied: Du hast keine Rechte dieses Objekt zu oeffnen.
    msg-error-zone: Diese Zone ist von *** geschuetzt.
    msg-error-permission: Du darfst dieses Objekt nicht sprengen!
    msg-error-claim: Hier ist kein Objekt um es zu schuetzen!
    msg-error-claim-conflict: Konflikt mit einer bereits geschuetzten Tür!
    msg-admin-claim-error: Spieler *** ist nicht online, sei sicher das *** der richtige Name ist.
    msg-admin-claim: Du hast ein Objekt von *** in Anspruch genommen!
    msg-owner-claim: Du hast ein Objekt in Anspruch genommen!
    msg-error-adduser-owned: Du kannst keine Spieler auf das Schild von *** Schild hinzufuegen!
    msg-error-adduser: Kein Objekt vorhanden um Spieler hinzuzufuegen!
    msg-owner-adduser: Du hast ein Spieler auf das Objekt hinzugefuegt!
    msg-help-command1: '&C/lockette <line number> <text> - Bearbeite geschuetzte Objekte.
        Rechtsklick auf das Schild um es zu bearbeiten.'
    msg-help-command2: '&C/lockette fix - Fixiere eine Tuer, die in einer falschen
        Stellung war. Schaue zum bearbeiten auf die Tuer.'
    msg-help-command3: '&C/lockette reload - Lade die Daten erneut. Nur fuer Operators.'
    msg-help-command4: '&C/lockette version - Zeigt Version von Lockette an.'
    msg-admin-reload: Lade Daten erneut.
    msg-error-fix: Keine Tuer gefunden.
    msg-error-edit: Erst musst du mit einem Rechtsklick ein Schild anklicken.
    msg-owner-edit: Schild wurde erfolgreich bearbeitet.
  17. Code:
    18:08:11 [SEVERE] Could not pass event PlayerInteractEvent 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 org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:175)
    at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:287)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:636)
    at lishid.orebfuscator.hook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:96)
    at net.minecraft.server.Packet15Place.handle(SourceFile:39)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
    at lishid.orebfuscator.hook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:60)
    at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:554)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:452)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)
    Caused by: java.lang.IncompatibleClassChangeError: Expecting non-static method com.gmail.nossr50.mcMMO.getPlayerProfile(Lorg/bukkit/entity/Player;)Lcom/gmail/nossr50/datatypes/PlayerProfile;
    at org.yi.acru.bukkit.PluginCore.inGroup(PluginCore.java:531)
    at org.yi.acru.bukkit.PluginCore.inGroup(PluginCore.java:441)
    at org.yi.acru.bukkit.Lockette.LocketteBlockListener.canInteract(LocketteBlockListener.java:1322)
    at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(LocketteBlockListener.java:1155)
    at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(LockettePlayerListener.java:203)
    at sun.reflect.GeneratedMethodAccessor62.invoke(Unknown Source)
    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)
    There appears to be a conflict between Lockette (latest) and mcMMO (latest) on Bukkit 1.2.4, any idea how to fix it?
  18. Offline


    Could you upgrade the plugin to 1.2.4-R1.0?
  19. Offline


    leitao85 please describe what problem you're having with Lockette. Be sure to include the CB release# and any pertinent parts of your server log.
  20. Offline


    I can confirm this, with the latest RB for mcMMO and newest Lockette. Appears to happen when players interact with doors that have timers. No problems with chests or other containers.
  21. Offline


    People on my server are having troubles accessing and locking chests and furnaces (they're not op). But I can do it just fine (I'm op). They get a permission denied error when they try. No errors spit out in the console. I'm running the Recommended build 1.2.4-R1, as well as mcMMO for 1.2.4-R1 and PhysicalShop. I get these problems with the regular Lockette, and NukerNL's Lockette also.
  22. Offline


    Is this 1.2.4 compatible? And thank you for such an awesome plugin
  23. Offline


    lavigha no one has reported any 1.2.4 issues, and it has been out over week now. So... yes.
  24. Offline


    I just downgraded to Lockette 1.5 with everything else the same, and people are still getting the permission denied errors on all their protected containers. However, it seems that ops do not experience these problems. I think this could be caused by craftbukkit, mcMMO, or PhysicalShop since I never had the problems in the earlier versions of those three. Can someone help narrow it down and fix the bug?
  25. Offline


    Acru So one of our only like few VIP features seem to have been owned by a plugin. I could not figure it out till I had removed yours. Where is the permissions to disable colors on signs :(

    That or somehow if your using any kind hook maybe into sign colours then your stripping or something is causing bypassing.

    Example it uses # not & like it use to. So when a person uses #atest it will not work because they don't have the signcolours permission but if you use &atest it will work and I have a feeling it's either you added colours or you had some kind hook ages ago for signcolours that now is outdated because they use # now :)
  26. Offline


    It is compatible
  27. Offline


    Request: Could you work/hook into factions so that if another faction is in control of land with someone else's lock, that the lock is nullified? Example: Faction A has a village with lots of People's houses (with locked chests and doors). Faction B conquers Faction A and takes control of the village. At this point now, They would have the village, but all doors and chests would be not accessible to Faction B. If they decide to take the materials of the village, Breaking it down, there would be floating chests and doors all over the place, and I'm pretty sure my players want booty from conquering. What I would like is a check to see if the Locked Door/Chest/Furnace/Ect. is in Claimed land, and the owner of the lock is not part of the faction. (if the owner is part of the faction that conquered, it should be ignored.) If the answer to these two are True, then the Lock Should be able to be destroyed by anyone inside the faction.

    You probably would have to work with the creator of Factions to do this :)

    and on a side note, my server runs both Lockette and Chestshop, and I don't have any issues...
  28. Offline


    Well I was able to fix the permission denied errors (since I was using permissions) but now I have another problem.
    For a while, the door timers would work. Now all of a sudden, the door timers fail to work. The doors have to be closed manually. I checked the server console, and no exceptions have occurred. I tested with NukerNL's Lockette 1.6. Also running PhysicalShop 1.2.4-R1 and mcMMO 1.2.4-R1 and craftbukkit 1.2.4-R1. Could someone help me with this issue?
  29. Offline


    I'm pretty sure that this version does work for 1.2.4.

    Yes, it is.

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


    It does work with 1.2.4, but there is one error that happens when a player interacts with a timed door. Look at the top of this page for that.

Share This Page