[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

    Minwar

    Hm, is permissionsex working with this yet? I saw it on the front saying it isn't, is there a way to get it working on this?
     
  3. Offline

    KollegahDerBoss

    WHY DID YOU FIX THE FENCE GATE EXPLOIT, IT WAS AWESOME FOR US GRIEFERS, PLEASE MAKE A NEW BUG <333
     
    clingon082 likes this.
  4. Offline

    clingon082

    Bug report: When I put My sign on a chest on my server the sign is blank and other users can open it please fix this bug :)
     
  5. Offline

    Creepz21

    i had found a bug with lockette on doors, to reproduce the bug do the following:
    First, place 2 doors and protect it with lockette
    Second, get a sticky piston and make sure that it can take away the block under the door, and if you turn it on and off then the door will pop off and/or the sign
     
  6. Offline

    BoorMachine

    Hey, Im Having a Problem with Permissions. Lockette plugin works fine except my admins cant open chests or doors claimed by someone else. Me as Owner with OP permissions can open doors and chests.

    this is the console log.
    Code:
    05.02 20:10:55 [Server] INFO [Lockette] Ready to protect your containers.
    05.02 20:10:55 [Server] INFO [Lockette] Using ops file for admin permissions.
    05.02 20:10:55 [Server] INFO [Lockette] Enabled link to plugin GroupManager for Groups, version 1.9 (2.8.1) (Phoenix)
    05.02 20:10:55 [Server] INFO [Lockette] Detected craftbukkit build [1846] ok.
    05.02 20:10:55 [Server] INFO [Lockette] Version 1.4.9 beta is being enabled!  Yay!  (Core version 1.3)
    05.02 20:10:55 [Server] INFO [Lockette] Loading Lockette v1.4.9 beta.
    and ive added these permissions to my admin rank
    Code:
    lockette.admin.create.*
    lockette.admin.break
    lockette.admin.bypass
    lockette.admin.snoop
    lockette.admin.reload
    
    Please help me, It worked fine before.
     
  7. Offline

    nate302

    This is how our server is running lockette, works fine. We're running permissionsbukkit btw.

    Code:
    Member:
        permissions:
            lockette.user.create.trapdoor: true
            lockette.user.create.chest: true
            lockette.user.create.dispenser: true
            lockette.user.create.door: true
            lockette.user.create.furnace: true
    Moderator:
        permissions:
            lockette.admin.break: true
            lockette.admin.bypass: true
            lockette.admin.create.chest: true
            lockette.admin.create.dispenser: true
            lockette.admin.create.door: true
            lockette.admin.create.furnace: true
            lockette.admin.create.trapdoor: true
            lockette.admin.snoop: true
     
  8. Offline

    Buckethead

    Feature request: i used to use deadbolt which was a older continuation of this however it is falling out of date and support. would it be possible to make it so that furnaces and other directly next to each other objects could all be protected under 1 sign. ty

    what about the "more users" sign

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

    BoorMachine

    Lol, im stupid xD forgot to enable this on lockette config file:
    Code:
    enable-permissions: true
    
     
  10. Offline

    MagikarpLOL123

    Does this support permissionsbukkit?
     
  11. Offline

    Greylocke

    I have used it with both PermissionsBukkit and bPermissions. (and Yeti permissions, but that doesn't count anymore!)
     
  12. Offline

    MiHo

    Please make it possible to destroy Lockette locked chests by explosions.
     
  13. Offline

    Edpon

    Noob question right here.

    Is it possible to remove the broadcast "snoop" thing as admins? Thanks.
     
    KollegahDerBoss and DerekZil like this.
  14. Offline

    DerekZil

    Same question lol...
     
  15. Offline

    nate302

    We use the latest permissions bukkit on 1.1-R4 Dev. Here's our Lockette config file as well :) We run it with towny, and that works as well.

    http://pastie.org/3352081

    It's in the config file, just change:
    Code:
    broadcast-snoop-target: '[Disabled]'
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 18, 2016
  16. Offline

    winter4w

    Some way people are breaking the chest will it be fixed
     
  17. Offline

    MiHo

    Please make it OpenSource.
     
  18. Offline

    winter4w

    I get this

    Code:
    12:43:37 [INFO] [Server] Ill fix the maze thing
    12:43:41 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEve
    nt to Lockette
    java.lang.ClassCastException: com.massivecraft.factions.P cannot be cast to com.
    massivecraft.factions.Factions
            at org.yi.acru.bukkit.PluginCoreLink.getFactions(PluginCoreLink.java:72)
     
            at org.yi.acru.bukkit.PluginCore.inGroup(PluginCore.java:539)
            at org.yi.acru.bukkit.PluginCore.inGroup(PluginCore.java:441)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.canInteract(Lockett
    eBlockListener.java:1310)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(Locket
    teBlockListener.java:1153)
            at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(L
    ockettePlayerListener.java:193)
            at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.j
    ava:340)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:57)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:453)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEven
    t(CraftEventFactory.java:187)
            at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.j
    ava:283)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:602)
            at net.minecraft.server.Packet15Place.handle(SourceFile:39)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100)
            at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:7
    8)
            at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
    12:43:42 [INFO] [AutoAnnouncer]  If you want diamond type /warp diamond
    >say WHen i get my new pc
    12:43:43 [INFO] [Server] WHen i get my new pc
    12:43:58 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEve
    nt to Lockette
    java.lang.ClassCastException: com.massivecraft.factions.P cannot be cast to com.
    massivecraft.factions.Factions
            at org.yi.acru.bukkit.PluginCoreLink.getFactions(PluginCoreLink.java:72)
     
            at org.yi.acru.bukkit.PluginCore.inGroup(PluginCore.java:539)
            at org.yi.acru.bukkit.PluginCore.inGroup(PluginCore.java:441)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.canInteract(Lockett
    eBlockListener.java:1310)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(Locket
    teBlockListener.java:1153)
            at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(L
    ockettePlayerListener.java:193)
            at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.j
    ava:340)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:57)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:453)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEven
    t(CraftEventFactory.java:187)
            at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.j
    ava:283)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:602)
            at net.minecraft.server.Packet15Place.handle(SourceFile:39)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100)
            at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:7
    8)
            at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
     
  19. Offline

    wdow117

    someone on my server found out that Sticky pistons can pull the block trap doors are placed on, breaking the lockette
     
  20. Offline

    phanaticd

    i get this error with lockette

    04:51:27 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEvent to Lockette
    java.lang.NullPointerException
    at org.bukkit.craftbukkit.block.CraftSign.getLine(CraftSign.java:24)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwnerBase(Lockette.java:1115)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwnerBase(Lockette.java:1089)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:977)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:865)
    at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(LocketteBlockListener.java:1135)
    at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(LockettePlayerListener.java:193)
    at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.java:340)
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:57)
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:453)
    at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:187)
    at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:283)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:602)
    at net.minecraft.server.Packet15Place.handle(SourceFile:39)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100)
    at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
     
  21. Offline

    jump

    I'd like to get this plugin to work with RepairChest. Is it possible to do and if so, could you make the source available? Or... could you change the plugin such that is the first line entered isn't recognized as a valid line for Lockette that you disregard so that other plugins operate??? Thanks.
     
  22. Offline

    Hackers5955

    Acru From The Bigining This Plugin Worked For Me But Not Now:( Plzz Help
     
  23. Offline

    MiHo

    I still would love do see going this project OpenSource :)
     
  24. Offline

    Greylocke

    if you would like some help. you need to provide some details regarding the issue. Error messages, plugin versions, etc.
     
  25. Offline

    Reko

    i put a sign down and right click it..... type /lockette 3 test and it says i need to select the sign first.......... and wont let me edit signs
     
  26. Offline

    Hackers5955

  27. Offline

    TrickXI

    it wont let me open other peoples chest
     
  28. Offline

    Acru

    That is on the to-do list, yeah.
    I set aside this weekend for the project.
     
  29. Offline

    MiHo

    Great to hear and thanks for that great plugin.
     
  30. Offline

    globox44t

    Doors do not lock. Even iron doors are openable by other players.
     
  31. Offline

    Greylocke

    if you have groups on your signs, then check your group settings. If you get a message in chat when you open doors, then you've got everyone set with admin powers. It works. Check your settings. If you still can't figure it out, make a pastebin with your Lockette config and the pertinent parts of your permissions, then post the link.
     

Share This Page