[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

    zanew8

    How do I make it so only a certain rank can lock chests? I use groupmanager for permissions and I put the lockette.user.create.* permission node in the rank I want it in and no where else, but default players can lock chests? and i dont want it like that! how can I fix it? Please Help!
     
  3. Offline

    rockxz2135

    Use PermissionsEx it is a lot better than group manager and has more features and essentials is compatible.
     
  4. Offline

    wdow117

    I was wondering if you can add a "lockpick" feature. type /lockpick while looking at a lockette sign, and it will remove X from your inventory (whatever item is set as the lockpick) and will have X% chance to break the sign.
     
  5. Offline

    wolnavi

    can you please fix this to work with PEX please thanks
     
  6. Offline

    Ewe Loon

    I also thought it would be usefull if the sign could be underneith or above the chest, this way you can almost compleatly hide the sign
     
  7. Offline

    prizna

    Is there a way that I can stop players from editing their signs?
     
  8. Offline

    MrEminemFan

    I'm having problems eddeting already placed signs? I don't know what the line number is supposed to be? Beacuse I have to edit the sign so 2 peapole can open the chest? Can anybody help?
     
  9. Offline

    NoMansLand

    Will you be able to add in MultiWorld support? we have several worlds and we cant lock our chests in these worlds
     
  10. Offline

    lazy_architect

    I have a request that may be a little strange to some people but I wanted to know if you could add a [exclude] tag. So everyone but the people on the list would be able to use a door or take from a chest. I upkeep free food and free gear chest and would love to be able to cut some players that abuse this off.
     
  11. Offline

    Greylocke

    How about just making a new group called "freeloaders" and move the appropriate players into it?
     
    Inscrutable likes this.
  12. Offline

    simuciokas

    Code:
    [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: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:284)
    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:536)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:434)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
    
    Help? Using 1.1 recommended build

    Mod Edit (TnT): Use
    Code:
    [code]
    tags please.
     
  13. Offline

    KryptonIC

    I think you should make admins able to open ANY chests made by users.
     
  14. Offline

    Greylocke

    You can. Check the top of the forum for the proper config and permissions settings.
     
  15. Offline

    tassox33

    Is there a way to only allow players to open others chest when they are online? So disable chest lock for online players?
     
  16. Offline

    re4397

    how to admin bypass?
     
  17. Offline

    Gimlao

    Is it possible to hide the "Bypassed a door owned by..." messages ?

    Code:
    broadcast-snoop-target: '[]'
    Like this, it will only hide the messages about chests...
     
  18. Offline

    Greylocke

    read the instructions in the original post, above. It has very clear documentation of the config settings and permissions nodes.
     
  19. Offline

    Cha0sPudd1ng

    Hi Acru,

    when you Update this Plugin for CB 1818? :)
     
  20. Offline

    Factknowhow

    Hmm... how do you make it so that admins and ops can look in any chest?​
     
    Greylocke likes this.
  21. Offline

    orchidee

    I really love this plugin, but I experience a problem on mac os x.
    I can't enter the [] in minecraft ....

    Is there a way to change this symbols to something else?
    I tried several things, copy / paste etc, but they won't come up....

    never mind, using a different keyboard layout solved the problem ^^

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

    Asterdom

    Wow what a list of responses, first off thank you for making this plugin to where it is, feels right in the minecraft world using a sign and now that the fence bug got worked out i as a server player am loving it!

    However i am playing on a Tekkit sever which means a lot of iron/electric furnaces everywhere with non-protectable resources in them. I was hoping to ask if an option could be added (and coded i suppose) to add block IDs to this plugins protectable list? That would really solve a consistant amount of issues here ty!

    Thank you again tho for supporting your plugin so well!
     
  23. Offline

    Odell00

    I am having trouble with this. Can you make it so that you can LOCK doors not just have it say who its owned by and ask to shut it?

    My bad sorry, you can just set the timer to 0.

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

    blackhawk185

    Can you please change the way you download it? I can't download it with that temporary file stuff:( .
     
  25. Offline

    tassox33

    Is there a way to only allow players to open others chest when they are online? So disable chest lock for online players?

    I'm just trying to make sure you can only steal from online members.
     
  26. Offline

    NEREVAR117

    Can you please add an option to have locks consume money from iConomy?
     
  27. Offline

    Vorsath

    In config.yml:
    allow-admin-bypass: <true/false> (admins/OPs can/cannot open locked doors)
    allow-admin-snoop: <true/false> (admins/OPs can/cannot open locked chests)
    ---
    And add these permissions (if enable-permissions is set to true and you use permissions):
    lockette.admin.bypass
    lockette.admin.snoop
     
  28. Offline

    rudedoggx

    Great plugin! I hope you add the '[Protected] tag for viewing only' feature to the plugin. It'd be really cool to be able to showcase your stuff without having it stolen.
     
  29. Offline

    Greylocke

    rudedoggx I had the same need. Unfortunately, bukkit doesn't expose anything that can do that. Tickleman1 picked up the project and made a plugin that works with Spout to make chests ViewOnly. Works great!
     
  30. Offline

    zydar

    sources are visible? What license?
     
  31. Offline

    simuciokas

    [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: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:284)
    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:536)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:434)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)

    Help? Using 1.1 recommended build​
    BUMP​
     

Share This Page