[SEC] Lockette v1.6 - Simple chest and door lock, no databases! [1848-2060]

Discussion in 'Plugin Releases' started by Acru, Feb 14, 2011.

     
  1. Offline

    Acru

    Lockette v1.6 - The sign-based container and door lock for Bukkit! - by Acru Jovian

    Download it at BukkitDev! (JAR), also view the Change Log on BukkitDev.
    Recommended Craftbukkit Builds: 1.1-R3, 1.1-R4, 1.1-R6, and the 1.2.3 beta builds.


    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
    • 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:
    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 UTF-8 format. 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:

    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:

    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, start a private conversation if you need the details now~

    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]

    This post has been edited 49 times. It was last edited by Acru Mar 17, 2012.
  2.  
  3. 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.
  4. Offline

    Hackers5955

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

    MiHo

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

    Greylocke

    if you would like some help. you need to provide some details regarding the issue. Error messages, plugin versions, etc.
  7. 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
  8. Offline

    Hackers5955

  9. Offline

    TrickXI

    it wont let me open other peoples chest
  10. Offline

    Acru

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

    MiHo

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

    globox44t

    Doors do not lock. Even iron doors are openable by other players.
  13. 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.
  14. Offline

    aritturlt


    This post has been edited 1 times. It was last edited by aritturlt Feb 19, 2012.
  15. Offline

    omgipown

    Hey, I saw iConomy was on your list of things to do. Will you ever implant an iConomy fee?
  16. Offline

    Viperdream

    I keep getting this error:

    Code:
    2012-02-19 10:48:33 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEvent 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(LocketteBlockListener.java:1320)
     
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(LocketteBlockListener.java:1153)
     
        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:61)
     
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460)
     
        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:609)
     
        at lishid.orebfuscator.hook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:75)
     
        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 lishid.orebfuscator.hook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:44)
     
        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)
    The problem apparently lies with Lockette. Is there any way to fix this?

    Thanks
  17. Offline

    nate302

    com.massivecraft.factions.P cannot be cast to com.massivecraft.factions.Factions

    does not look like a lockette problem, may be a conflict with another plugin you are running. I've not had any issues so far.
  18. Offline

    Viperdream

    I just asked at the Factions plugin thread whether this is related to Factions or not.

    I am currently using the latest version (1.4.9)

    It would be great if there's a way to fix this, since it creates lag.

    Thanks
    Greylocke likes this.
  19. Offline

    killuer2

    will you guys have lockette updated for 1.2 build?
  20. Offline

    nate302

    A bit premature isn't it? Plugin authors should update for recommended builds, not dev versions. Until there's an RB available, it can be dicey for the update. Why update for R5 dev #xxxx when xxxy breaks it? There's not even a dev build for 1.2 yet! Just be patient!
  21. Offline

    Greylocke

    I think this is what @killuer2 is asking about, a notice from the bukkit team:

    so the question still stands: @Acru is Lockette ready for R5?
  22. Offline

    nate302

    What I'm pointing out is.. until there IS an R5, he shouldn't have to provide the update. Until the dependency AND api's are both updated, there may need to be changes before he can push out an update. Asking before those api and code changes are even done yet is a waste of everyone's time.

    This post has been edited 1 times. It was last edited by nate302 Feb 20, 2012.
  23. Offline

    Greylocke

    @nate302
    historically,your point would be valid. But with this release things are a little different.Consider:
    • the bukkit team is asking admins to check with their plugin devs to confirm that theit plugins will be R5 compatible.
    • R5 has been available in a dev build for almost a week.
    • plugin devs are adding "R5 compatible" notes to forums and change logs
    so it really isn't unreasonable to ask @Acru if Lockette is going to be compatible with R5. Other devs seem to be able to answer the question.
  24. Offline

    rickky

    how to fix it?
    [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEvent to Lockette
    java.lang.IllegalArgumentException: Cannot measure distance between world_nether and world
    at org.bukkit.Location.distanceSquared(Location.java:380)
    at org.bukkit.craftbukkit.CraftWorld.playEffect(CraftWorld.java:687)
    at org.bukkit.craftbukkit.CraftWorld.playEffect(CraftWorld.java:677)
    at org.yi.acru.bukkit.Lockette.Lockette.toggleDoors(Lockette.java:1451)
    at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(LocketteBlockListener.java:1187)
    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:61)
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460)
    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)
  25. Offline

    Greylocke

    @rickky oooOOOoooo... that's one I haven't seen before! Neat! What version craftbukkit are you using? Did you change CBs recently?
  26. Offline

    rickky

    Craftbukkit++79
    Maybe cb++ problem
  27. Offline

    Chrisski3

    You should also make it so that levers, buttons, and pressure plates can be locked too!
  28. I am a admin on my server. and I just put in lockette and I am makeing a tutorial room for lockette at my spawn point. I can get into a door with someone else's name on it. But I can not get into Chest's or Furnace's why???? Im the the admin. al though it's really not that important for getting into chest's and furnace's

    This post has been edited 1 times. It was last edited by CentralMinecraft Feb 23, 2012.
  29. Offline

    Greylocke

    There's a config setting and permission setting for that. You'll need both for 'snooping' to work.
  30. Offline

    Viperdream

    Code:
    2012-02-19 10:48:33 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEvent 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(LocketteBlockListener.java:1320)
     
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactDoor(LocketteBlockListener.java:1153)
     
        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:61)
     
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460)
     
        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:609)
     
        at lishid.orebfuscator.hook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:75)
     
        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 lishid.orebfuscator.hook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:44)
     
        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)
    I'm still getting this error : / And apparently it's not with factions
  31. Offline

    Greylocke

    You're not running Factions?
  32. Offline

    Viperdream

    I am running Factions, but I've asked them there whether it's related to their plugin.

    This is what they said:

    Apperantly it's a known bug with Lockette and Factions. Because after a quick search I found this:

    http://dev.bukkit.org/server-mods/factions/tickets/53-lockette-faction-problem/

    It'd be great if there's a way to fix this, because it's lagging my server : /

    And yes, I am using the latest version of both plugins

    This post has been edited 1 times. It was last edited by Viperdream Feb 23, 2012.

Share This Page