[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


    @Acru thanks for updating :)
  3. Offline


    Hmm, I can see how this might be useful, though may only be implementable with new signs. Eg, with the quick-protect method enabled, you could touch a sign as if you were editing, and the next quick-protect would copy the sign in full, rather than just the default [Private]/<yourname>?

    I'm far from an expert in how permissions.yml should be laid out. I would normally use the console commands /permission add etc, but one bit in that seems wrong to me.

    Where you have the permission;
    with the child;
    lockette.user.create.*: true​
    though it is not a child permission.

    Yer welcome, more to come too~

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


    Having the option in the configuration files to make it where people can break chests with tnt or their hands would be great. I really wanted to use this plugin for a factions pvp server and have it set up where people can only break chests with tnt to raid a factions chest storage. This would allow people to lock chests from the general public but someone with intentions of stealing would have to work to do it and couldn't see whats inside beforehand . Maybe in the future we will see these handy options! :)
  5. Offline


    Perhaps only with a special permission instead?

    Perhaps one that both the aggressor and victim will need to have, like lockette.pvp.tnt or something.

    Though, now that I think of it, there isn't really a way to tell who set off a tnt...
  6. Offline


    1214. WorldEdit, WorldGuard, and PEX are the major ones.

    What we're currently running. I'll wait for it to happen again and find out who triggerd it, and check out the pistons.
  7. Offline


    Is there a way to forbid OPs destroying any foreign sign protected by lockette?
    Currently a red message appears that a sign was broken by an admin.
  8. Offline


    Foreign sign?

    In any case , you can use permissions to better specify who can do what.
  9. Offline


    That would be nice too, but the "copy stick" (lets call it that for now) would also work for [More Users] signs, at least that's what i intended to suggest.

    Also would it be possible to allow quick protect on furnaces/doors/trapsdoors?

    Disable the allow admin break option.

    (Or when permissions are enabled and you have a permissions plugin that supports negative flags remove "lockette.admin.break" from them.)

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


    my config file:
    where is the "allow admin break option"?

    A sign not owned by a player.

    someone else's

    A permission system is the last thing i would install. Before this happens iam deleting the server.
  11. Offline


    @Arcu I am having the same problem except i am using GM for my permissions and it wont allow my users to do anything with this plugin. This needs to be fix asap. This isn't a problem with permissions i was using lockette on 1.7 and 1.8 pre 2. but now that it has updated it doesn't work at all!
  12. Offline


    Quick protect also does [More Users] signs, yaknow, no reason why you couldn't copy them too. :3

    Quick protect already works for furnace and dispenser, but is planned for doors. I'm not sure how it'd work for trapdoors though, but I'll see what I can do.

    Well, if you don't want them breaking open chests, should they be op in the first place?
    You could deop them.
    Or did they need op for some other reason?

    There was no allow-admin-break as this is one thing admins needed to be able to do, for cases when players abuse locks in some way. Though the red message announces it to try and limit abuse.

    I doubt it is the 'same problem', best explain in more detail.
    Last I checked GM was working just fine, what versions are you using of GM/Bukkit/etc?
    Also, 1.8 pre 2? There was no bukkit for that, they went from 1.7.3 directly to 1.8. o3o

    What about minor ones? I checked WorldGuard to be sure and it isn't doing anything unusual.
    Still, it could be a bukkit bug that I just have to work around.

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


    Here's my complete list, but I've been talking about this on #permissionsex, and a lot of smarter people than me seem to think it's a minecraft (not bukkit) bug, as vanilla 1.8 servers are doing 'odd things' with teleport and spawn (which it appears are other symptoms of the problem)

    06:46:54 [INFO] Plugin List: "PlugMan" "Essentials" "Spout" "iConomy" "EssentialsSpawn" "EssentialsGeoIP" "LogBlockQuestioner" "EssentialsProtect" "DisableXP" "WorldGuard" "Lockette" "BorderGuard" "EssentialsChat" "RawcriticsOreObfuscationPluginSpout" "CommandHelper" "PermissionsEx" "ModTRS" "WorldEdit" "Modifyworld" "Permissions" "ChatManager" "LogBlock"
  14. Offline


    Thanks, though I looked into it further and I think I found the cause; http://leaky.bukkit.org/issues/1579
    I'll avoid using this function for now, and make my own, heh. (This is specific to bukkit piston events, though.)

    Edit: Out of curiosity, what odd things?
  15. Offline


    We noticed this back at 1.8pre - After a while, when people died, they'd spawn at the wrong location, because the area was occupied (said that in console). After bukkit started releasing 1.8 stuff, we could do more testing, and discovered more issues - random chunks are unable to be teleported to (/tphere, for example, on _one_ chunk of our spleef arena, sends people two chunks in the wrong direction - until a server restart). Unable to place signs on chests (eg, right click on a chest with a sign, the chest opens. Move two blocks over, right click, it works fine). Hole in the floor errors, etc.

    I... well, I thought I had. But I haven't. I was going to say that I logged a bug about this on leaky, but I can't seem to find it. I'll tell 'em.

    Unfortunately, I'm not a java guy, at all. And I'm not one of the inner circle anyway - so I can't do much to help.


    Edit: http://leaky.bukkit.org/issues/1581
  16. Offline


    hello, just wondering if you have had anyone with problems using bPermissions or alerter with lockette. The plugin was working fine but since i just installed the craftbukkit recommended build I am unable to use the [Private] on the signs, even as the OP. I can lock chests by right clicking with them. The permissions node's are not working as well for my players. Alerter tells me i cant use the Private when i try it on the sign.
  17. Offline


    Lockette was working with BukkitPerms, but SuperPermsBridge seemes to have done something to cause Lockette to ignore the permissions settings. If you need to run SuperPermsBridge, you'll need to set Permissions = false in the Lockette config so that Lockette will look to your ops list for admins.
  18. Offline


    Hey I don't know if this is answered already but could you elaborate a bit on how to prevent other users from breaking signs/chests to get in? Thanks, and great pulgin :)
  19. Offline


    @Acru They released a test build for 1.8 pre 1 and pre 2. Pre 1 was not openabe and pre 2 had some errors, which I modified to work properly.

    Right now I am using bukkit version 1185 with 1.81. and using the latest gm as of 10 minutes ago. I have even given all players lockette.admin.* just to get the damn thing to work but nothing. I have tried every setting including permmsions /on and off. There are no conflicting plugins. here is the builder stats I have tried all old and new permmisions and no luck.
    default: false
    - ChestShop.shop.buy
    - ChestShop.shop.create
    - ChestShop.shop.sell
    - essentials.back
    - essentials.back.ondeath
    - essentials.balance
    - essentials.balance.others
    - essentials.balancetop
    - essentials.chat.color
    - essentials.chat.question
    - essentials.chat.shout
    - essentials.compass
    - essentials.depth
    - essentials.home
    - essentials.ignore
    - essentials.kit
    - essentials.kit.tools
    - essentials.mail
    - essentials.mail.send
    - essentials.me
    - essentials.msg
    - essentials.nick
    - essentials.pay
    - essentials.ping
    - essentials.portal
    - essentials.powertool
    - essentials.protect
    - essentials.sethome
    - essentials.signs.break.disposal
    - essentials.signs.break.mail
    - essentials.signs.break.protection
    - essentials.signs.break.trade
    - essentials.signs.create.disposal
    - essentials.signs.create.mail
    - essentials.signs.create.protection
    - essentials.signs.create.trade
    - essentials.signs.use.*
    - essentials.suicide
    - essentials.time
    - essentials.tpa
    - essentials.tpaccept
    - essentials.tpahere
    - essentials.tpdeny
    - essentials.warp
    - essentials.warp.list
    - essentials.worth
    - iConomy.user
    - jail.usercmd.*
    - jobs.join.*
    - jobs.world.*
    - lockette.admin.create.*
    - lockette.create.all
    - lockette.user.*
    - lockette.user.create.*
    - mcmmo.ability.axes
    - mcmmo.ability.excavation
    - mcmmo.ability.herbalism
    - mcmmo.ability.mining
    - mcmmo.ability.swords
    - mcmmo.ability.unarmed
    - mcmmo.ability.woodcutting
    - mcmmo.chat.*
    - mcmmo.item.*
    - mcmmo.skills.*
    - mcmmo.tools.*
    - teleport.users
    - towny.town.*
    - towny.wild.*
    - uQuest.CanQuest.*
    - default
    prefix: '&2 Builder &f'
    build: true
    suffix: ''
  20. Offline


    I'm having a problem that is really irritating. I can't seem to find the bug that is causing it. Essentially, when I try to lock a chest, I get the following message:

    "Lockette: Permission to lock container denied."

    The following are my config files:

    Lockette Config.yml:

    enable-messages-help: true
    broadcast-snoop-target: '[Everyone]'
    enable-chest-rotation: false
    broadcast-reload-target: '[Operators]'
    broadcast-break-target: '[Everyone]'
    enable-messages-error: true
    enable-quick-protect: true
    enable-messages-user: true
    enable-messages-owner: false
    default-door-timer: 10
    enable-messages-admin: true
    enable-protection-doors: true
    explosion-protection-all: false
    enable-permissions: true
    enable-protection-trapdoors: true
    strings-file-name: strings.yml
    allow-admin-bypass: true
    allow-admin-snoop: false
        description: Member towny commands
            towny.town.claim: true
            towny.town.delete: true
            towny.town.new: true
            towny.town.plot: true
            towny.town.rename: true
            towny.town.resident: true
            towny.town.toggle.*: true
            towny.nation.*: true
            towny.wild.*: true
        description: All users essentials commands
            essentials.help: true
            essentials.list: true
            essentials.mail: true
            essentials.mail.send: true
            essentials.me: true
            essentials.motd: true
            essentials.msg: true
            essentials.rules: true
            essentials.seen: true
            essentials.suicide: true
            essentials.whois: true
            essentials.back: true
            essentials.back.ondeath: true
            essentials.delhome: true
            essentials.home: true
            essentials.sethome: true
            essentials.sethome.multiple: true
            essentials.tpaccept: true
            essentials.tpdeny: true
        description: Other permissions such as Lockette, Chestshop, and iConomy
            lockette.user.create.*: true
            lockette.create.all: true
            iConomy.holdings: true
            iConomy.help: true
            iConomy.payment: true
            train.place.minecart: true
            train.command.properties: true
            ChestShop.shop.buy: true
            ChestShop.shop.sell: true
            ChestShop.shop.create: true
            creativegates.use: true
            ichat.color: true
            worldguard.region.addowner.own.*: true
            worldguard.region.removeowner.own.*: true
            worldguard.region.addmember.own.*: true
            worldguard.region.removemember.own.*: true
            worldguard.region.flag.regions.own.*: true
            worldguard.region.flag.flags.*: true
            worldguard.region.remove.own.*: true
            worldedit.extinguish: true
            worldedit.fixwater: true
    PermissionsBukkit Config.yml file:
            - member
                permissions.build: false
                permissions.*: true
                essentials.*: true
                worldedit.*: true
                worldguard.*: true
                towny.*: true
                traincarts.*: true
                iconomy.*: true
                lockette.*: true
            - member
                essentials.members: true
                other.members: true
                permissions.build: true
                towny.members: true
            - default
        build: '&cYou do not have permission to build here.'
    Any help would be appreciated. I'm just trying to get "member" working, I know my admin permissions are a bit messed up.

    EDIT: It seems it is a glitch with SuperpermsBridge, from what I can see. Is there a workaround or a temporary fix?

    EDIT2: Seems that even without the superpermbridge it still doesn't want to grant access to Lockette to anyone.
  21. Offline


    For me:
    > admins = people with SSH access ( user minecraft or root )
    > OP != admins
    > OP = member / player / no guests
    > Not OP = all guests

    On my server all members are OPs.
    To restrict their rights iam using Essentials - disabling 80% of OP commands for them.
    I also disabled the /help command, so they cant figure out what commands are available.

    If a player is abusing a sign, iam going to advise him/her.
    Theres no need for being an asshole as admin. ;)

    Could you add the possibility to restrict even ops?
  22. Offline


    All: I'll have to look into a solution for permissions that doesn't involve trying to keep up with changes in five different permissions managers.

    I'll get back to replying to the individual permissions issues a bit later.

    I'll put it on the list.
    Simanova likes this.
  23. Offline


    Thanks. I am looking forward to it already :)
  24. Offline


    Amongst my wishes for Christmas, is that this plugin wont stop developing.

    Proud user since 766ish, loving it - Don't stop, Acru!

    Thank you.
  25. Offline


    Im not using SuperPermsBridge or BukkitPerms. I need my players to be able to use the lockette commands as well. So is there a way around turning the perms off.
  26. Offline


    Hi guys, I think I found what is causing the problems with permissions.

    I have the same problems like the users described above me. I am using the latest version of GroupManager, and my users can't create protections despite having the permission to do so. ("Lockette: Permission to lock container denied.")

    I tried around for a while and nothing worked. Then I removed Towny and everything was working fine! Users with the lockette.user.create.* permission were finally able to create protections.

    I hope this helps...
  27. Offline


    Hmm, thanks! This may be the clue I was looking for~
    Just so I know, what version of Towny?
    Edit: Also, try re-adding Towny again and giving out the lockette.towny.wilds permission?

    Query, do you use the Towny plugin?

    If so, what version? Also if so, try giving yourself the permission lockette.towny.wilds

    If this is the cause, I may need to give it a different error message to distinguish the 'can't build in wilds' permission error from the regular one, so it is clear.

    The plugin itself stops others from breaking the signs and chests, etc. So no worries. :3

    Thanks for the support~

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


    I am using the latest version of towny (0.76.1).
    I did what you said, and it works fine with the lockette.towny.wilds permission!
    Thank you :)
  29. Offline


    That node worked. Different error message would be great for troubleshooting purposes if anything. Thanks my good sir!
  30. Offline


    Alright, its working now.. I just had to reinstall the plugin. :)
  31. Offline


    [Everyone], or a "nicknamed" [Public] isn't working (for doors, setting it manually).
    Has it possibly been changed?

Share This Page