[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

    deadlock989

    Yes of course it's ok, whatever.
     
  3. Offline

    bfanboy

    ? Problem in 531. Server restart fixes it until the next time. Just letting you know.

    K Thx
     
  4. Offline

    Acru

    Aw, I woulda hoped that they fixed by now. Of course, I'm currently working under the assumption that it is a craftbukkit problem, but perhaps I can find out exactly why it is happening and work around it. Maybe it is a block cache issue... Hmmmm~ Thanks though.
     
  5. Offline

    RyanTheLeach

    Does this work with the new permission plugins after nijo stopped developing it?
    I can't seem to make group restricted chests./
    [MERGETIME="1299908808"][/MERGETIME]
    double post because i forgot to subscribe to thread
     
  6. Offline

    Redbyte

    Hey thanks this works great. [​IMG]
     
  7. Offline

    Scyfi

    Thanx for the reply, not a game stopping problem. The mod is awesome and my players love it.
     
  8. How do you add more signs to the chests to add more names. i tried putting [private] on a sign for the same chest and it doesn't work. it didn't say in the description above how to do it, it just says you can
     
  9. Offline

    RyanTheLeach

    it does say in the description above...
     
  10. Offline

    Acru

    Tell me which one you use and I'll try to support it?
    Edit: Do you mean the Phoenix one? I'll have to look into it.

    Yer welcome~

    As RyanTheLeach said, it is in the desc :3
    The first line should be [More Users]
     
  11. Offline

    RyanTheLeach

    Yes, i mean the phoenix one.
     
  12. Offline

    newtekie1

    If it helps any, it seems like when I experience the problem on my server, the area near the original spawn point for the map is not affected, just areas a good distances away.
     
  13. Offline

    riuthamus

    I dont know if anybody else is getting this, but once the server has been on for a bit, or... maybe when somebody does something, not sure on either yet. You cant place shit unless you restart. Restart works and then everything goes back to normal until its triggered again. I am using 544 craft, fyi!
     
  14. Offline

    Graham

    mine's not working for build 531 it says somthing like 20:25:06 [INFO] Lockette version 1.2.2 is being enabled! Yay!
    20:25:06 [INFO] Lockette: Detected craftbukkit jenkins build [531] ok.
    20:25:06 [SEVERE] PLAYER_COMMAND loading Lockette v1.2.2 (Is it up to date?)
    java.lang.NoSuchFieldError: PLAYER_COMMAND
    at com.nijikokun.bukkit.Permissions.Permissions.registerEvents(Permissi
    ns.java:118)
    at com.nijikokun.bukkit.Permissions.Permissions.onEnable(Permissions.ja
    a:111)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:118)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoade
    .java:451)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManag
    r.java:217)
    at org.yi.acru.bukkit.Lockette.Lockette.setupPermissions(Lockette.java:
    37)
    at org.yi.acru.bukkit.Lockette.Lockette.onEnable(Lockette.java:95)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:118)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoade
    .java:451)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManag
    r.java:217)
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:83)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:61)
    at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:204)
    at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:191)
    at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:131)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:246)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)

    help?
     
  15. Offline

    Acru

    The trace show its failing when loading the permissions plugin.
    (at com.nijikokun.bukkit.Permissions.Permissions.registerEvents)
    Remove or update your Permissions.jar
    I'll have to add a catch for this, maybe.
     
  16. Offline

    Kane

    @Acru damn I wish you did not have a life :p
     
  17. Offline

    Acru

    If I wasn't distracted by other things, I'd have caught this sooner;
    http://leaky.bukkit.org/issues/565

    I can work around the problem partly but not fully.
    Hopefully the bug report gets some attention~
     
  18. Offline

    elpacco

    Hey is there any way you can extend this to crafting tables? Would be excellent.

    Thanks!
     
  19. Offline

    Acru

  20. Offline

    Myx0x3

    Bug:
    Cant remove a chest after ill remove the sign!

    Fix this bug!
     
  21. Offline

    PPowerHouseK

    This works perfectly for me close to spawn, but for some reason a good distance from spawn it just stops working entirely. There are no errors in the console either. Any ideas or suggestions?
     
  22. Offline

    Acru

    Try restarting the server and see if it still happens.
    There is currently an issue within CraftBukkit that MAY be fixed in CB build 552;
    http://ci.bukkit.org/job/dev-CraftBukkit/552/
    I have yet to test this new build myself, though.

    If the issue still happens after restarting and/or updating, provide more details.
     
  23. Offline

    Roy8102

    Tnx man it works perfect! Everything is thinken of! w000t ( Sorry for bad english)
     
  24. Offline

    mutiny

    just installed 552 to test your plugin, seems to work better when locking chests, lots of other plugins appear to work fine with that build too
     
  25. Offline

    Acru

    Ah, that is good to hear~
    That chunk ghosting bug was causing all sorts of issues, that disappear for a while with a server restart...
     
  26. Offline

    Mew2468

    Great plugin, works fine and I love the simplicity behind it. Thank you for developing such a wonderful plugin!
     
  27. Offline

    Acru

    Thanks for the positive feedback~ :3
    [MERGETIME="1300166493"][/MERGETIME]
    Incidentally, I put in a fix for this for the upcoming version, but it seems the CraftBukkit people also put in a catch for this in build 523. :3
     
  28. Offline

    g00tch

    Getting anywhere with the door locks?
     
  29. Offline

    Acru

    Was poking at this a little last night, and continuing in my free time today.
    I'm trying to decide how to handle doors, as to where to support putting the sign.

    The easiest way would be to put the sign right on the door, though that would mean walking through the sign when you go through the door, so trying some alternatives.

    Any thoughts on this?
     
  30. Offline

    M1nurThr3t

    possibly placing directly in front of the door while closed, create sign, and boom protected like a chest.
     
  31. Offline

    Acru

    You don't have any issues with walking through the sign then?

    At the moment, I'm experimenting with placing a sign on the block directly below the door.
     

Share This Page