[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

    Daulton

    U forgot ur name
    It has to be
    [Private]
    Name here
     
  3. Offline

    Maxis010

    Not true, you only specific a name when you aren't claiming a container under your name
     
  4. Offline

    Daulton

    Did u try updating?
     
  5. Offline

    Mineaccount

    yes
     
  6. Offline

    Hyphe

    The config and strings no longer gets generated.

    CB 740.
     
  7. Offline

    Daulton

    Does any1 know to suffixs for ur name like if u want teams and team towns ex: [Mag]eGPliXzZ I just cant edit it if u can plz post a reply to this and connect to this server ip 67.222.157.191
     
  8. Offline

    troed

    If it fits with your vision for Lockette, I've gotten a request for "opening hours" (shops/passways etc). Protected doors should only be able to be opened during specified "hours" (I guess daylight would be obvious if the internal time system isn't granular enough).

    [Private]

    [Everyone]
    09:00-17:00

     
  9. Offline

    jaythorpe

    No idea if it is possible but would you be able to add a config for viewing the chest items but not able to take the items out of the chest?
     
  10. Offline

    pinacoladaxb

    I second this! Perhaps let players label signs with [Protected] if they want people to be able to view the chest but not take anything?
     
  11. Offline

    Mineaccount

    Hi! I got permissions and I put the permissions to lock chests in my permissions file like so:

    Code:
    plugin:
        permissions:
            system: default
            copies:
    groups:
        Default:
            default: true
            info:
                prefix: '&7'
                suffix: '&f'
                build: true
            inheritance:
            permissions:
                - essentials.helpop
                - essentials.help
                - essentials.motd
                - essentials.rules
                - essentials.spawn
                - essentials.sethome
                - essentials.home
                - essentials.afk
                - essentials.kit
                - essentials.kit.<tools>
                - lockette.user.create.*
                - essentials.mail
                - essentials.mail.send
                - essentials.tpa
                - essentials.tpaccept
                - essentials.tpdeny
                - essentials.signs.free.use
                - essentials.signs.disposal.use
                - essentials.signs.trade.use
                - essentials.signs.buy.use
                - essentials.signs.sell.use
                - creaturebox.creature.skeleton
                - creaturebox.creature.zombie
                - creaturebox.dropspawner
                - creaturebox.placespawner
        Griefer:
            default: false
            info:
                prefix: '&d'
                suffix: '&f'
                build: false
            inheritance:
            permissions:
                - essentials.ping
                - essentials.help
        Moderator:
            default: false
            info:
                prefix: '&9'
                suffix: '&f'
                build: true
            inheritance:
                - Default
                - Builder
            permissions:
                - essentials.tp
                - essentials.list
                - essentials.tphere
                - essentials.kick
                - essentials.banip
                - essentials.ban
                - jail.command.jail
                - jail.command.unjail
                - jail.usercmd.jailstatus
                - essentials.whois
                - jail.command.jailcheck
                - logblock.*
        Advanced Mod:
            default: false
            info:
                prefix: '&9'
                suffix: '&f'
                build: true
            inheritance:
                - Default
                - Builder
                - Moderator
            permissions:
                - essentials.item
                - essentials.setwarp
                - essentials.delwarp
                - essentials.warp
                - essentials.give
        Admin:
            default: false
            info:
                prefix: '&c'
                suffix: '&f'
                build: true
            inheritance:
            permissions:
                - '*'
                - jail.command.jailcreate
                - jail.command.jaildelete
                - jail.command.jail
                - jail.command.unjail
                - jail.command.jailtransfer
                - jail.command.jailtransferall
                - jail.command.jailcheck
                - jail.command.jailtelein
                - jail.command.jailteleout
                - jail.command.jaillist
                - jail.command.unjailforce
                - jail.command.jailclear
                - jail.command.jailclearforce
                - jail.command.jailmute
                - lockette.user.create.*
                - lockette.admin.create.*
                - lockette.admin.bypass
                - lockette.admin.snoop
                - lockette.admin.reload
        Builder:
            default: false
            permissions:
            - essentials.warp.stevencity
            - essentials.afk
            - essentials.kit.*
            - essentials.mail
            - essentials.mail.send
            - essentials.motd
            - essentials.tpa
            - essentials.tpaccept
            - essentials.tpdeny
            - essentials.home
            - essentials.sethome
            - essentials.spawn
            - essentials.compass
            - essentials.msg
            - essentials.warp
            - -essentials.warp.*
            inheritance:
            - default
            info:
              prefix: '&f'
              build: true
              suffix: '&f'
        Donator:
            default: false
            permissions:
            - essentials.setwarp
            - essentials.warp
            - simplereserve.kick.prevent
            - simplereserve.enter.kick
            inheritance:
            - default
            - builder
            info:
              prefix: '&e'
              build: true
              suffix: '&f'
    users:
        108ricky:
            group: Admin
            permissions: '*'
    users:
        marcushbk:
            group: Admin
            permissions: '*'
    
    And I get this:

    [​IMG]


    EDIT: found the problem here:

    Code:
    users:
        108ricky:
            group: Admin
            permissions: '*'
    users:
        marcushbk:
            group: Admin
            permissions: '*'
    
    Notice that I put two users: i deleted the second one and it works fine. Thank you for this amazing plugin!
     
  12. Offline

    Orcem12

    Getting: "You don't have permissions to access this chest" but players can still take stuff >.<
     
  13. Offline

    Acru

    Oh dear, lots of posts~
    I'll have to catch up when I have time later today. :3

    Edit: I'll get to replying tomorrow, actually, I'm so behind!
    I did put out an update, however.
     
  14. Offline

    sexy vampire

    confirmed saport with supply signs ^_^
     
  15. Offline

    KingPin

    using 766 and 1.38 anyone getting an issue not being able to protect doors and furnaces?
     
  16. Offline

    Splaat

    Got an issue when I updated both lockette and bukkit. Now, only one door will close if I have a double door. And if I try to close the one that's open, the other one opens itself .. Really frustrating to know that this security isn't so secure after all

    Using bukkit 766 and lockette 1.3.8. I will however try to revert back to 740 were I know lockette was working perfect.

    Edit: Reverting didn't work. How can I fix this? I'll add a screenie as well

    [​IMG]

    Edit 2: I located the problem. Since I have Self-Closing Doors also installed, a config line was creating trouble. If anyone here also uses Self-Closing Doors, edit this line and set it to false

    use-global-cd: false

    Now lockette is working perfect. Thanks for the awesome plugin
     
  17. Offline

    Phinary

    Problem. My map is huge. Over 1Gb. Whenever people try to lock in some areas it just says that it cant find a container and then does a [?]
     
  18. Offline

    pEteR_mEteR

    "No unclaimed container nearby to make Private!"

    my sign sand infront of a cheest or sign is over a door and all time i get this error

    anybody can help me?
     
  19. Offline

    Xenotropic

    Acru, first of all thank you for the very well made plugin.
    I do have a request, would it be possible for you to keep an updated static link of a Jar only version (no zip) so that we can automate updating Lockette in our server scripts?

    Thanks, and keep up the excellent work.

    Edit: I just tried some URL guessing and found http://members.shaw.ca/acru/Lockette.jar
    I figured I would post this here in case anyone else is looking for this.
     
  20. Offline

    Xuande08

    I cannot lock doors anymore, although i can lock them for other people, the game gives me the error message
    "Conflict with an existing protected door" I don't understand what I can do
    Permissions, Lockette and Craftbukkit are all on the newest version
     
  21. Offline

    Raspberry

    Our admins [Lord] can't break the locked chests of others...

    Can you point out what's wrong in the permissions?

    The ops.txt is empty.

    Code:
        Resident:
            default: true
            info:
                prefix: '&8'
                suffix: ''
                build: true
            inheritance:
            permissions:
                - 'jobs.job.*'
                - 'iJobs.user.*'
                - 'iConomy.list'
                - 'iConomy.rank'
                - 'iConomy.payment'
                - 'gs.use.*'
                - 'lightkill.self'
                - 'choptree.chop'
                - 'tomb.create'
                - 'tomb.tp'
                - 'tombstone.use'
                - 'tombstone.large'
                - 'tombstone.sign'
                - 'tombstone.quickloot'
                - 'tombstone.freesign'
                - 'lockette.user.create.*'
                - 'gills.user'
                - 'fishpeople.extendedair'
                - 'citizens.blacksmith.repair'
        Gentry:
            default: false
            info:
                prefix: '&7'
                suffix: ''
                build: true
            inheritance:
                - Resident
            permission:
                - 'advbans.kickk'
        Lord:
            default: false
            info:
                prefix: '&7'
                suffix: ''
                build: true
            inheritance:
                - Resident
                - Gentry
            permissions:
                - 'landmark.*'
                - 'iConomy.bank.*'
                - 'tomb.admin'
                - 'lightkill.kill'
                - 'lockette.admin.reload'
                - 'lockette.admin.break'
                - 'lockette.admin.create.*'
                - 'advbans.*'
                - 'citizens.*'
    
    Also... is there a way you could allow for inherited Permission [groups]?

    It'd be great if I put [Users] on a sign and all groups that inherit [Users] rights would get access to the chest.
    Config switch like 'allow-inherited-permissions' or something would acceptable :)

    Great Job!

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  22. Offline

    Maxis010

    As best as I can tell there is nothing wrong with this permission file, unless there is another plugin conflicting with the protection then I don't see where the problem is

    @ Acru
    Since when has Lockette been incompatible with FenceStack, I've been using Lockette and FenceStack on the same server with absolutely no problems for weeks

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  23. Offline

    GKenTN

    [SEVERE] Could not load 'plugins/Lockette.jar' in folder 'plugins':
    java.lang.UnsupportedClassVersionError: Bad version number in .class file

    i got this error...
     
  24. Offline

    Blackstorm72

    Really odd,

    No errors but Build #766, and no conflicting plugins mentioned in the OP;

    A few players are now just starting to get the [?] when placing signs right next to the chest and doors as well, and logging in and out doesn't fix the issue, and there are no errors, just [?] on the signs. And it just happens too, so I am rather confused.
     
  25. Offline

    Sorken

    Request: My users have started requestion a donation type mode on chests. So that anyone can put stuff in the chest, but only owner or permissioned people can withdraw.
    Example:
    [Private]
    MyName
    [Donate]
    Otherperson
     
  26. Offline

    40540057

    THANKS! the guys will love this! anything with signs is better than commands or certain blocks any day of the week and twice on sunday ... :p btw I think Sorken's donation box is a good idea ... my noobs would love that
     
  27. Offline

    crysis992

    I updated today my Essentials to the latest version and now i cant open any chests, cant claim new chests same for doors.
     
  28. Offline

    Maxis010

    Remove EssentialsProtect and try it again
     
  29. Offline

    crysis992

    Thanks, it works now. hmm worked fine with essentials protect before i updated to 2.2.18 :(
     
  30. Offline

    liquidthex

    I'm having a similar issue, I can place signs on doors but not above doors.. placing above the door results in "Lockette: Conflict with an existing protected door." and the sign will read [?] There are no other existing protected doors, so.. pretty sure that's not it.

    I'm not looking for a solution I'm just trying to provide some information that may help narrow down the cause of this problem, because I've seen it on a public server (www.minecraftserver.com) as well!! the admins there have no idea and just tell you to put the sign on your door.

    Mods installed on my server, all latest versions as of this post:
    bColoredChat, BigBrother, CommandBook, ControllerBlock, Dynmap, iConomy, Lockette, mcMMO, ObserverCube, Permissions, SpyerAdmin, Stargate, WorldEdit, WorldGuard, WormholeXTremeWorlds.

    I'm sure there's numerous things to point at and say remove that that's probably it! But I'm not going to, like I said just providing a list so maybe someone can find a correlation to solve their own problem, or something.

    Thank you for the excellent mod!
     
  31. Offline

    Raspberry

    heh -- figured it out... one of the admins thought it'd be funny if he'd /op himself from my computer when I wasn't in the room...
     

Share This Page