[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

    Acru

    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.



    Overview:

    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.)

    [​IMG]

    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.


    Features:
    • 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

    Lunthus

    Sounds like a bad server, they should have some protection like ownblocks or something, but why would everyone on the server be OPs?
     
  3. Offline

    Xordaii

    He mentioned already that he and a few friends combined their money to buy the server, so he can't really deop them... If your friends aren't very honest, and you can't buy them out, try installing PermissionsBukkit and SuperPerms, and take away all of the lockette.admin.* modes.
     
  4. Offline

    DragonMasterNYC

    Now what can I use to replace this that has the same exact features and can transfer all containers to.

    We have over 100 signs I don't think my users will be to happy that their stuff is up for grabs wile they're away when I switch plugins.
     
  5. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı

    Is the plugin actually broken, though? I doubt it will break anytime soon. If it does break, I'd probably update it because my server currently uses it.
     
    Kane likes this.
  6. Offline

    Teraku

    Lockette doesn't work anymore. It doesn't even show up as plugin when I type /plugins.
     
  7. Offline

    DragonMasterNYC

    If you do, mind posting it for those that still want to use it.

    It still works for me and has been for a wile. It's just I'm worried about future Bukkit updates that might break it.
     
  8. Offline

    Asaky

    Not working for me, my users cannot access there own chests it tells them "Locked" There are no other good lock plugins out there its really a shame.
     
  9. Offline

    Lunthus

    Currently, there is a decent one that allows you to use a stick to lock it, but seems to have issues and not stay there permanently, but Lockette is the best and my favorite! Currently it seems to be broken when my players try to make it. Says they do not have the permissions, yet I've been checking for hours, permissions are perfectly fine. Also note that, yes I have permissions set to true.
     
  10. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı

    I'd post it here :)
     
  11. Offline

    iExTaCYZz

    ANYONE

    Why cannot my builders an up, even me, access private doors and chests! Here is my group manager:

    Code:
    groups:
      Default:
        default: true
        permissions:
        - choptree.chop
        - choptree.command.check
        - choptree.command.chunk
        - choptree.command.toggle
        - commandbook.msg
        - craftbook.mech.bridge
        - craftbook.mech.bridge.use
        - craftbook.mech.cauldron
        - craftbook.mech.cauldron.use
        - craftbook.mech.elevator.use
        - craftbook.mech.gate
        - essentials.afk
        - essentials.back.ondeath
        - essentials.balance
        - essentials.clearinventory
        - essentials.eco.*
        - essentials.help
        - essentials.helpop
        - essentials.home
        - essentials.list
        - essentials.mail
        - essentials.motd
        - essentials.msg
        - essentials.pay
        - essentials.rules
        - essentials.sethome
        - essentials.sign.buy.use
        - essentials.sign.sell.use
        - essentials.sign.shop.use
        - essentials.sign.trade.use
        - essentials.signs.buy.use
        - essentials.signs.sell.use
        - essentials.signs.shop.use
        - essentials.signs.trade.use
        - essentials.spawn
        - essentials.suicide
        - essentials.warp
        - essentials.worth
        - essentialseco.*
        - signs.break.protection
        - signs.break.trade
        - signs.create.protection
        - signs.create.trade
        - signs.use.balance
        - signs.use.buy
        - signs.use.disposal
        - signs.use.free
        - signs.use.heal
        - signs.use.mail
        - signs.use.protection
        - signs.use.sell
        - signs.use.time
        - signs.use.trade
        - signs.use.warp
        - signs.use.weather
        - connectfour.play
        - connectfour.start
        - tictactoe.play
        - tictactoe.start
        - lockette.user.create.*
        inheritance: []
        info:
          prefix: '&e'
          build: true
          suffix: ''
      Owner:
        default: false
        permissions:
        - -essentials.protect.damage.*
        - '*'
        inheritance:
        - admin/irl
        info:
          prefix: '&6[Owner]&f'
          build: true
          suffix: ''
      SemiAdmin:
        default: false
        permissions:
        - '*'
        inheritance:
        - moderator
        info:
          prefix: '&2[SemiAdmin]&f'
          build: true
          suffix: ''
      Sister:
        default: false
        permissions:
        - '*'
        inheritance:
        - irl
        info:
          prefix: '&d[Sister]&f'
          build: true
          suffix: ''
      Builder:
        default: false
        permissions:
        - commandbook.*
        - essentials.*
        - essentials.item
        - essentials.itemspawn.item-all
        - essentials.time
        - essentials.time.world
        - kiwiadmin,*
        - nocheat.all
        - nocheat.*
        - lockette.admin.bypass
        - lockette.admin.snoop
        inheritance:
        - default
        info:
          prefix: '&5[Builder]&f'
          build: true
          suffix: ''
      Moderator:
        default: false
        permissions:
        - '*'
        inheritance:
        - builder
        info:
          prefix: '&b[Moderator]&f'
          build: true
          suffix: ''
      Admin/IRL:
        default: false
        permissions:
        - '*'
        inheritance:
        - irl
        info:
          prefix: '&4[Admin]&e[IRL]&f'
          build: true
          suffix: ''
      Admin:
        default: false
        permissions:
        - '*'
        inheritance:
        - semiadmin
        info:
          prefix: '&4[Admin]&f'
          build: true
          suffix: ''
      IRL:
        default: false
        permissions:
        - '*'
        inheritance:
        - admin
        info:
          prefix: '&e[IRL]&f'
          build: true
          suffix: ''
      SemiAdmin/IRL:
        default: false
        permissions:
        - '*'
        inheritance:
        - irl
        info:
          prefix: '&2[SemiAdmin]&e[IRL]&f'
          build: true
          suffix: ''
    
     
  12. Offline

    sole10

    nice plugin... why is it inactive? it works on 1060 :)
     
  13. Please, activate this Mod. As for when Bukkit updates along with Minecraft, I will want this to be available.

    I know Plug Ins take a lot of work, but htis Plug In is truly exceptional.
    I really like this, it stops all the people bitching and moaning, I really appreciate it.

    So if you can, please try your best to keep this Plug In up! I love it!
     
  14. Offline

    khamseen_air

    Because the guy who made it hasn't been on since the 17th of July. Apparently that one last update we were going to get, went out the window. :(
     
  15. Offline

    DragonMasterNYC

    I think it's because the dev hasn't been around to update it, but it won't stop those that know java from updating it. If the time comes, and mbaxter has the time, he might just update it. If not then someone else will since so many use this plugin.
     
  16. Offline

    crazyish

    Please Please Please Please Please dont stop the work on this plugin! It's one of the best plugins out there, it survives the plots being moved without save info being corrupted. It is usable for Guest builders on a server without permissions. It gives visible owner and users info on the outside of the box.. It shows if a box is locked at the glance of an eye.. People can learn to use it in a matter of seconds...
    I rly dont want to lose this one :/
     
  17. Offline

    khamseen_air

    Is it just me or does this not support the groups in permissionsbukkit? I'm trying to get all my plugins set up with it and it appears I can no longer access doors with the group name I'm in listed on them.
     
  18. Offline

    HockeyMike24

    Someone please pick up this plugin! I would love to keep using it in 1.8.
     
  19. Offline

    iExTaCYZz

    It is the same for me, I can not access doors or chests, or anything with a private sign for that matter. Nor can I make a private sign for others.
     
  20. Offline

    oliverw92

    Erm... it works fine. Why is it in the inactive section?

    If it actually breaks I'll happily fork it and fix it up.

    I've sent the dev a message. At the moment the source isn't on github or anything so I would have to decompile the jar file which is a bit annoying and messy.

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

    khamseen_air

    I can get it to work with permissionsbukkit and superpermbridge by using the nodes;
    superpermbridge.lockette.user.create.*: true (for users)
    superpermbridge.lockette.*: true (for admins)
    It just wont recognise groups, so if someone is in say a group called 'Trusted' it wont let them open doors or chests with [Trusted] on the sign.

    He hasn't been on in over a month, so I wouldn't hold my breathe for a reply I'm afraid to say.
     
  22. Offline

    oliverw92

    Just had a look at the source - it really is a mess in my opinion :\
     
  23. Offline

    1hacker

    It works fine with PermissionsEX v1.13
     
  24. Offline

    oliverw92

    If it actually breaks at some point then I will definitely step up and fix it. At the moment I don't have time.
     
  25. Offline

    khamseen_air

    Perhaps, but I'm using PermissionsBukkit and SuperPermBridge, not PermissionsEX. I don't particularly like PermissionsEX. :)
     
  26. Offline

    RROD

    Inactive, eh? Is it just me, or does it look like LWC is the victor?
     
  27. Offline

    oliverw92

    It should work with SuperPermBridge. Don't see why it wouldn't.
     
  28. Offline

    panda100123

    which permission lets people open a chest THEY make not anybody elses?
     
  29. Offline

    oliverw92

    I'm using PermissionsEx and it works perfectly.
     
  30. Offline

    Kane

    victor I would say not. LWC I would never recommend for large servers. The loss is all of ours who love Lockette. It does still work though bugs here and there are slowly going to popup.
     
  31. Offline

    Monstertke

    Can I ask why you wouldn't recommend it for large servers?

    I think LWC blows away everything else, The admin tools alone make it spectacular. Especially with the addition of the ability to physically remove protections.
     

Share This Page