[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

    KevinEssence

    Can you make chestshop compatible with this, I have a huge shop area on my server and people payed big for spots, and now when they place sign to make chestshop above, lockette detects it and create a private chest instead..before it was fine not sure what happened when you updated.
     
  3. Offline

    Windlord

    Code:
    org.bukkit.event.EventException
            at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:303)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:459)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callBlockPlaceEvent(CraftEventFactory.java:99)
            at net.minecraft.server.ItemSign.interactWith(ItemSign.java:60)
            at net.minecraft.server.ItemStack.placeItem(ItemStack.java:83)
            at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:303)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:636)
            at net.minecraft.server.Packet15Place.handle(SourceFile:39)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
            at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
            at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    Caused by: java.lang.IncompatibleClassChangeError: Expecting non-static method com.palmergames.bukkit.towny.object.TownyUniverse.isWilderness(Lorg/bukkit/block/Block;)Z
            at org.yi.acru.bukkit.PluginCore.canBuild(PluginCore.java:614)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.onBlockPlace(LocketteBlockListener.java:309)
            at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:301)
            ... 14 more
    The above occurs with the latest dev build of Towny.
    ElgarL has told me that Lockette needs to be recompiled against the latest Towny for it to work.

    Thanks for all the work!
     
  4. Offline

    Kowak

    Ok but which is the permission node that allow use Lockette? Just put a sign and lock the chest?
     
  5. Offline

    Greylocke

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

    so try lockette.user.create.* first and if your permissions manager supports it, then you're done. Otherwise you'll need to provide individual permissions for lockette.user.create.door, lockette.user.create.chest, etc.
     
  6. Offline

    HockeyMike24

    I am getting the exact same thing.
     
  7. Offline

    RyGuy147

    Dangit. Incompatible with ChestShops. :mad:
     
  8. Offline

    LlmDl

    I don't know what you people are talking about, I've used Lockette and Chestshop together for a year+ now.
     
  9. Offline

    Buckethead

    I posted a ticket about these 2 things and
     
  10. Offline

    RyGuy147

    Then the thread is wrong.
     
  11. Offline

    Greylocke

    Buckethead the fence issue was a problem back in December that has been patched. The tilled-ground-block is a bug in either bukkit or MC.. not sure which. Trapdoors will not stick to tilled ground blocks -- not much Lockette can do about that.
     
  12. Offline

    UnpluggedDK

    I have a big problem,
    I do not want my users to be able to make[private] signs, only my OP's should be allowed to do that.
    and i thought it would be like that by default, but it isn't.

    I have no permission plugin on my server as i do not want to use it.

    What should i do? plzz help or make a suggestion
     
  13. Offline

    Buckethead

    Idk y u dont get permissions and y u only let ops do.

    But if you open lockette in some type of zip viewer like jzip or winrar open the plugin.yml and change the section that has all the true values to op.

    Code:
    permissions:
        lockette.*:
            description: Permission for a super admin who can do anything.
            children:
                lockette.user.create.*: true    <------------ change from true to op
                lockette.admin.create.*: true  <----------- same here for all of them all the way through
                lockette.admin.break: true
                lockette.admin.bypass: true
                lockette.admin.snoop: true
                lockette.admin.reload: true
                lockette.towny.wilds: true
        lockette.user.*:
            description: All the permissions a normal user normally needs.
            children:
                lockette.user.create.*: true
                lockette.towny.wilds: true
        lockette.user.create.*:
            description: Allows the normal method of locking containers.
            children:
                lockette.user.create.chest: true
                lockette.user.create.furnace: true
                lockette.user.create.dispenser: true
                lockette.user.create.brewingstand: true
                lockette.user.create.custom: true
                lockette.user.create.trapdoor: true
                lockette.user.create.door: true
        lockette.admin.*:
            description: All the permissions a normal admin normally needs.
            children:
                lockette.user.create.*: true
                lockette.admin.create.*: true
                lockette.admin.break: true
                lockette.admin.bypass: true
                lockette.towny.wilds: true
        lockette.admin.create.*:
            description: Allows the admin method of locking containers.
            children:
                lockette.admin.create.chest: true
                lockette.admin.create.furnace: true
                lockette.admin.create.dispenser: true
                lockette.admin.create.brewingstand: true
                lockette.admin.create.custom: true
                lockette.admin.create.trapdoor: true
                lockette.admin.create.door: true
    ok ty. i hope that gets patched 1 day. that a pretty big let down

    if u have chestshops if a person doesnt own that shop they cant open it anyway

    do u have pex + modifyworld? errors on screen? perms?

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

    gawelium

    Hi ! Does your plugin need to be update for CB 1.2.5 to work with SimpleSignEdit ?

    Because CelticMinstrel says that :
    "The same goes for Lockette support; if someone wants to update the plugin to make it honour Lockette.isOwner(), I'd probably pull it.
    It's theoretically possible that some of the issues people are having were fixed and not released; you could try building the latest source from github and see if that fixes anything."

    Sorry I don't understand very well !!
     
  15. Offline

    UnpluggedDK

    This didnt Work.. :/ i also tried making them all the true's to OP, same effect
    Then i tried deleting all the code, everyone can still make signs..

    Its really wierd.. :(

    HEEEELP.. :)
     
  16. Offline

    iforgot290

    idk why the hell it says that at the top of the page
    the only problem that i face with it is, when i put a shop sign on a diamond block, it turns it into a lockette sign instead
    i wouldn't really call that incompatible
     
  17. Offline

    Buckethead

    change true to false? idk ive seen this is several other plugins work that way mabey this is diffrent i only guessed. i would highly recomend permissions. its not hard i will personally help you with it if u want. the hardestpart is just getting started
     
  18. Offline

    DarkByte7

    Is there any way to disable the Admin has snooped around in a container owned by player broadcast?

    Another cool feature would be adding a limit of how many chests or so a player can lock. Let's say a total of 3.
     
  19. Offline

    HockeyMike24

    Please update this! I don't want to be forced to use Deadbolt.
     
  20. Offline

    mixxit

    Caused by: java.lang.IncompatibleClassChangeError: Expecting non-static method com.palmergames.bukkit.towny.object.TownyUniverse.isWilderness(Lorg/bukkit/block/Block;)Z

    This is broken with the latest dev build of towny
     
  21. Offline

    Buckethead

    On server restarts doors are stuck open. PLz fix

    it works fine for me except for ht i put but deadbolt does this to

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

    Jay98d

    On screen? It just says "You do not own this chest" But it only does this to normal members, not me (the owner) I'm not quite sure what you mean, But the permissions plugin I use is Group manager, Any ideas? I run a big server and this problem is pissing alot of people off haha
     
  23. Offline

    Buckethead

    did u put in the admin override permission in. conflicting plugins? check your config and i use pex which works fine for me.
     
  24. Offline

    HockeyMike24

    Do you have Towny or ChestShop? Because it's not working with the latest versions of those plugins.
     
  25. Offline

    Buckethead

    i have chestshop and im using the latest pex 1.2.5r2 bukkit latest chestshop and latest lockette and they all work 100%
     
  26. Offline

    jeppemannen10

    help it not work D: every is installing but it not working i have 1.2.5 bukkit is it updated? help
     
  27. Offline

    HockeyMike24

    The latest Dev build of Towny does not work with it, Lockette needs to be updated.
     
  28. Offline

    Buckethead

    ok idk y people keep sayin this. It works fine for me except for some people who use towny. If you have a correct setup with pex or another perms mod this should work fine. and what is not working? Startup error or you dont know what your doing?
     
  29. Offline

    QBcrusher

    i havent tested this yet, but what happens if someone tries to claim a container or door that isnt theirs? are they free to open it?
     
  30. Offline

    jeppemannen10

    update this plugin is old
     
  31. Offline

    trout1212

    PLEASE UPDATE TO 1.2.5!!
     

Share This Page