[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

    WoAyumi

    Removed the "Lockette" dir. Error still occurs.

    Code:
     [SEVERE] Error occurred while enabling Lockette v1.7 (Is it up to date?)
    java.lang.NullPointerException
            at org.yi.acru.bukkit.PluginCore.setLink(PluginCore.java:198)
            at org.yi.acru.bukkit.PluginCore.linkExternalPlugin(PluginCore.java:172)
            at org.yi.acru.bukkit.PluginCore.onEnable(PluginCore.java:81)
            at org.yi.acru.bukkit.Lockette.Lockette.onEnable(Lockette.java:110)
            at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:215)
            at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:337)
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381)
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:257)
            at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:239)
            at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:383)
            at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:370)
            at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:199)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:434)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    
     
  3. Offline

    Drew1080

    I honestly dont know why its doing that as i have tested it on 4 different servers now and it works fine.
    Ill have a look at what is causing this error tomorow.

    BTW is that the version downloaded from the bukkit-dev page?

    If you could pm me with the following:

    • The craftbukkit version your using
    • The full server log when you get this error
    • & A list of plugins that your are currently using
     
  4. Offline

    WoAyumi

    Okay.
     
  5. Offline

    Drew1080

    So is it the most recent version from the bukkit-dev page as I deleted the original 1.7 and uploaded a more recent one?
     
  6. Offline

    WoAyumi

    When exactly did you re-upload it? Did it happen after my report?
     
  7. Offline

    LlmDl

    Drew1080

    The Lockette 1.7 that someone was using before your 1.7 was approved on the dev.bukkit page was written by Elgarl. He put in pull requests on Acru's github and when Acru did not respond for a week, we made it public.

    Has your version of 1.7 used these pull requests? Have you spoken with Acru at all?
     
  8. Offline

    Speedrookie

    Lockette would not place signs on my chest they just put a plain sign on the chest i thought it was because of chest-shop but no i removed it and reloaded and still locket wont work and the same with doors i have also tried re installing lockette multiple time please help!
     
  9. Offline

    ohjays

    Im getting a fail as well
    Code:
    09:22:16 [SEVERE] Error occurred while enabling Lockette v1.7 (Is it up to date?)
    java.lang.NullPointerException
            at org.yi.acru.bukkit.PluginCore.setLink(PluginCore.java:198)
            at org.yi.acru.bukkit.PluginCore.linkExternalPlugin(PluginCore.java:172)
            at org.yi.acru.bukkit.PluginCore.onEnable(PluginCore.java:82)
            at org.yi.acru.bukkit.Lockette.Lockette.onEnable(Lockette.java:110)
            at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217)
            at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:337)
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381)
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:257)
            at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:239)
            at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:383)
            at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:370)
            at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:199)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:434)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    
    running bukkit 2247 1.6 loads ok though

    Just moved all plugins aside and it load without errors, will poke around with a long stick :)

    It bails when im running it with either the permissionbukkit-1.6, or superpermsbridge-1.2 plugins ( all other plugins are back in ), also tried removing the permissionsbukkit config.yml (permissions file). no change

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

    Drew1080

    No I hvant spoken with Acru and neither as anyone else for the last 3+months.

    & Yes the version on the dev.bukkit.org site as fixed the error with the plugin core.

    I have removed the version 1.7 from the bukkit dev and fixing all these errors with the plugin core then I will release it again.

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

    Speedrookie

    Lockette is not compadiable with Towny it does not work when towny is installed!
     
  12. Offline

    LlmDl

    http://goo.gl/2TCHr - This link will download Elgarl's Lockette 1.7 it has updated dependencies for towny (amongst everything else)
     
  13. Offline

    Drew1080

    Yeah, Im currently updating Lockette again to give more support for towny users & to fix the error people keep having with it.
     
  14. Offline

    LlmDl

    If you're on Github, you should just fork elgarl's fork of lockette.
     
  15. Offline

    Drew1080

    Ok ill do that then. Thx I didnt think of that.

    Good news everyone I've sorted out the issue people have been having with Towny.
    Just wait for the BukkitDev staff to approve the new file.

    Hope this helps.

    Its also compatible with CraftBukkit 1.2.5 R.04 Build#2222

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

    LlmDl

    I see that you forked Elgarl's work but it looks like you scrubbed Elgarl's name from the README, not sure if that's cool or not.

    Edit: Or maybe you forked Acru's and then put in Elgarl's updates.
     
  17. Offline

    Sonar

    good luck guys, I will never use a magic spell/password on chests those damn things are annoying!! - will try out 1.7 :)

    Edit
    After updating to 1.7 -> My first sign I tried on a door gave me "Read Error".
    I didn't get chance to edit the sign - as soon as i placed the sign "Read Error".

    I went back into the server and no matter how many times I tried to get that same error I couldn't lol maybe it was just a 1-off from updating?.

    Ive never had this "Read Error" on 1.6 never ever seen it before since the server started.

    If it does it again at some point I will be going back to 1.6.

    Thanks for the updates/bug fixes. keep up the good work.


    I have no crash log or anything generated anywhere.
     
  18. Offline

    ThePreston159

    I would love a tag like [Redstone] to be able to open the door with a redstone current, because it currently cannot be
     
  19. Offline

    Speedrookie

    Thank you very much
     
  20. Offline

    Drew1080

    I forked Acru's lockette, I'll add Elgars name in the plugincore readme file. Saying that I use some of his code for Towny Integration.

    Lockette v1.7 has now been approved by BukkitDev staff, Enjoy :D

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

    ElgarL

    Drew, taking someone elses code and not giving credit or abiding by the OS license is not only extremely bad manners, it's illegal.
    You have done this without Acru's or my permission. You are welcome to begin your own fork by all means, BUT you MUST abide by the licensing terms, which means giving credit to all authors or the original code.

    Lockette itself is already being maintained, by myself, as you already know when you took my code and claimed it as your own. 1.7 has been out for over a month at http://palmergames.com/downloads/Lockette.jar
     
  22. Offline

    Drew1080

    Im very sorry about this ill delete, the fork of git-hub and start from scratch again.

    ElgarL I sent you a pm.

    ElgarL

    I askedmd_5 to remove the version 1.7 from the bukkit dev page and I have removed all the code from my forked version on git-hub.

    md_5 also said that Acru is going to be updating the project soon himself

    Im very sorry about what I have done to you ElgarL.

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

    Sonar

    Your version never crashed me. Thank you. Now running 1.7 *again*.

    Edit
    Request: Possible to edit every sign with line command instead of only [private] tagged signs.
    but ofc you will only be able to edit your own signs you placed.
     
  24. Offline

    asofold


    So if now "random people" without access to Lockette at bukkitdev start bringing out "random versions" of Lockette, is it just to assume that Lockette is "dead" ?

    I would tend to make my own version for internal use in such case...
     
  25. Offline

    Inscrutable

    Lockette (1.6 and 1.7) doesn't like mcMMO version 1.3.09-b945. (MC1.25, CB RB4.0, PEx 1.19.2)
    Any sign using [example] lets everyone access it, and it throws this error:
    Code:
    2012-07-05 17:52:49 [SEVERE] Could not pass event PlayerInteractEvent to Lockette
    org.bukkit.event.EventException
        at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:304)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460)
        at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:177)
        at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:287)
        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 org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:172)
        at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:567)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:459)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    Caused by: java.lang.NoSuchMethodError: com.gmail.nossr50.datatypes.PlayerProfile.getParty()Ljava/lang/String;
    
    It seems mcMMO have changed their getParty method. Acru are you still around? :confused:
    Thankfully it still works OK with mcMMO v1.3.08, so stick with that to keep things secure for now
     
  26. Offline

    Buckethead

    i just downloaded a lockette170 from craftbukkituptodate but dont see anything about it here or on dev??????
     
  27. Offline

    LlmDl

    You might have downloaded the one that Drew made, its said to not be working very well. Scroll back through the last few pages, Elgarl forked Lockette and put out a .jar with 1.7 as the version number.
     
  28. Offline

    Buckethead

    yeah but cbutd shouldnt have downloaded it right? Thats how i got it
     
  29. Offline

    superdupernova

    Please add a [Deposit] tag, so people can drop things off, if it's possible!
    It would just have to be like this:
    [Private]
    superdupernova
    [Deposit]

    Then, everyone could put stuff in, but only I could take it out.
     
  30. Offline

    draigle

    thank you for this awsome plugin these are for you[cake][diamond][gold]
     
  31. Offline

    kcmartz

    Could you add support for Essentials? The Essentials economy feature I like using. Could you add support for that? Thanks in advance! *topic watched*
     

Share This Page