[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

    BioBG

    Download link pls ....
     
  3. Offline

    WoAyumi

    Acru!
    You don't need mysql to limit chests!
    All you have to do is to create permission nodes, then configuration for them
    lockette.limit.1 = [ set your chest limit here, in config.yml]
    lockette.limit.5 = [set your chest limit here, in config.yml]
    then, put it on flatfile database.
    If to use this feature wise enough and allow creating chests only to vips, then this database may be pretty thin.
    You could make this feature optional in config.yml and satisfy everyone's needs.

    towny uses awfully big ugly flatfile database and still everyone is happy with it, everyone downloads their plugin.

    My point is - give users what they ask for, make them happy and leave feature off by default, to leave satisfied those, who hate database and love your plugin, because it is not using databases.
    Everyone will be happy then.
     
    Pr4w likes this.
  4. Offline

    Acru

    As it is a beta, when it comes out of beta I will list the full change log since 1.4.4.
    It is easier for me that way, and plan to get it out asap, during the holiday break.
    Also move over to bukkitdev fully.
     
  5. Offline

    King_KYl3

    Is thier a link for new vers Lastest RB the one i got now bugged in 1.0+ can't open other users chests
    thanks alot :)
     
  6. Offline

    Zidkon

    Acru, I would like to see if I can modify some things for my server, you can provide the Source? or you want it private?


    That is a good idea, if he finishes the LOGGING system the system can check the Logs to see how many have how much people and stuff like this, or he can make the flatfile for every player like most plugin does and put the "number" of active chests he have, this thing is not so hard to make.
     
  7. Offline

    Greylocke

    One of the nice things about Lockette is its simplicity. Because all the necessary information is on a sign in the world, there is NO NEED for an external database. Elegant simplicity.
     
  8. Offline

    Pr4w

    +1, that is one feature I'd REALLY like to see ! :D
     
  9. Offline

    Greylocke

    Your assumptions are unfounded and your sarcasm is misguided.

    Considering that a server of any size would be equipped with a logging tool like HawkEye, LogBlock or something similar, then there already exists a database of all chests. Adding it to Lockette would be redundant. From my experience, it takes less than a minute to remove every chest a griefer or inactive player has ever placed. And a quick SQL query will show exactly how many chests a player has locked and exactly where they are; if I need to know.

    I don't have a use for limiting the number of locked chests, but it does seem like an incrementing lock counter would be a fairly simple feature to add to a flat file and be well within the scope of this plugin.

    What Acru decides to do with Lockette is entirely up to him of course, but I appreciate the elegant simplicity of Lockette. It locks containers and doors, and it does the job very well. I already have tools to do the other stuff.
     
  10. Offline

    MatrixJ21

    I get this when [/lockette reload]'ing, so I thought I'd be a good person and report it. Running on CB #1597. Command ran from console and in-game.

    2011-12-21 22:55:44 [INFO] [Lockette] Reloading plugin configuration files.
    2011-12-21 22:55:44 [WARNING] Unexpected exception while parsing console command
    org.bukkit.command.CommandException: Unhandled exception executing command 'lockette' in plugin Lockette v1.4.9 beta
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:165)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:378)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:374)
    at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:564)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:541)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)
    Caused by: 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.PluginCore.selectiveBroadcast(PluginCore.java:689)
    at org.yi.acru.bukkit.Lockette.Lockette.localizedMessage(Lockette.java:857)
    at org.yi.acru.bukkit.Lockette.Lockette.localizedMessage(Lockette.java:816)
    at org.yi.acru.bukkit.Lockette.Lockette.onCommand(Lockette.java:154)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 7 more

    :)
     
  11. Offline

    Acru

    Mmm, thanks, it looks like something might have changed in Factions? What version of factions are you using?

    This is one thing I wanted to do, connect to an existing logger, though @oliverw92 suggested I wait for a Guardian release.

    I'm looking forward to seeing how that project comes together. :3

    I was planning on releasing the source along with Lockette 1.5, though I seem to keep putting it off wanting to get things 'perfect'.

    But I'll probably have to settle for less than that, heh. Mind the mess.

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

    MatrixJ21

    v1.6.2, released 4 days ago.
     
  13. Offline

    Zidkon

    Well actually you know there is a lot of developers that can help you out with this plugin with the features people want, of course I'm not saying you should do but they could give you solutions/ideas that you could use to make the plugin better for everybody, with options for everything, who doesn't like just go in config file and disable it :), or enable it can be, as you say functionality of Lockette is perfect but some players want it a little edited, so just think about it ^^, nobody is perfect and nothing will be perfect at the end, the most bigger plugins like Essentials, Spout, and some others are just a bunch of unorganized code that is a mess to understand because so many developers has come in, so you can probably divide your plugin into 2 and manage both but you keep you ideal with the official one.

    Well is up to you, I just want to make an option to disable or add a TnT chance to explode sings, since my server is PvP server :p, thanks bro.
     
  14. Offline

    DesertHawk978_2

    Does this work with Minecraft version 1.0.1?
     
    LarsMaehlum likes this.
  15. Offline

    Austin

    That terrible fencegate glitch fixed? Im a lockette fanboy, not deadbolt. But I cant use lockette when that glitch is there.
     
  16. Offline

    agubelu

    I could translate the plugin into Spanish, if you want
     
  17. Offline

    Fishfish0001

    I get this on 1.4.9:
    Spams the console quite terribly

    Code:
    00:38:50 [SEVERE] Could not pass event PLAYER_INTERACT 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:335)
     at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
     at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:339)
     at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:178)
     at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:266)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:593)
     at net.minecraft.server.Packet15Place.a(SourceFile:39)
     at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:93)
     at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
     at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:527)
     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
     at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)
    
     
  18. Offline

    Acru

    Yeah I squashed that with the 1.4.9 update, specifically.

    I could send the new strings file to you in a conversation? There are a few new ones now~

    Also, what I did today instead of working on Lockette:

    http://na.leagueoflegends.com/board/showthread.php?t=1636569

    Forgive me for the added delay! ;.;

    PS: You probably won't get it if you don't play LoL, but still~

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

    agubelu

    Sure
     
  20. Offline

    Acru

    It has something to do with the new version of Factions, though I haven't pinned down why I'm getting a "com.massivecraft.factions.P", yet.
     
  21. Offline

    Austin

    Weeeeeeeee!

    *switches*
     
  22. Offline

    Zidkon

    Are groups for Lockette signs working on new versions? I just changed to 1.4.9 and the group's signs Didn't work :/

    Only [Everyone] works, the other groups just cannot open double doors (It doesn't say any message like "no permissions")
     
  23. Offline

    Acru

    What groups plugin are you having trouble with?
     
  24. Offline

    Zidkon

    bPermissions
     
  25. Offline

    Austin

    Not sure what set this off. I got 2 of them, this is one.

    Code:
    02:58:44 [SEVERE] Could not pass event PLAYER_INTERACT 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.PluginCore.selectiveBroadcast(PluginCore.java:689)
            at org.yi.acru.bukkit.Lockette.Lockette.localizedMessage(Lockette.java:857)
            at org.yi.acru.bukkit.Lockette.Lockette.localizedMessage(Lockette.java:819)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.canInteract(LocketteBlockListener.java:1365)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.interactContainer(LocketteBlockListener.java:1275)
            at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(LockettePlayerListener.java:243)
            at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.java:335)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:339)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:178)
            at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:266)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:593)
            at net.minecraft.server.Packet15Place.a(SourceFile:39)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:93)
            at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:550)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
            at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:527)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)
    
     
  26. Offline

    sajjad

    How to make it that users can only make like 5 protected chests each?
     
  27. Offline

    Zidkon

    Developer is trying to add a kind of database system for this, atm there is no option for this feature in the plugin.
     
  28. hi is there a link to the new version for 1.0 bukkit. Also does the new permissionsEX 1.17 work properly with this.
     
  29. Offline

    Sharpy310

    I am getting the same problem as Austin is getting. When someone interacts with a chest, for example when an admin opens someones chest it causes a Serverwide restart. Is the plugin updated for 1.0? And also is there anywhere that I can submit a bug report?
     
  30. Offline

    Zidkon

    Can it be related to the same problem I'm having with the permissions group not being readed correctly? So everytime an admin try open it (if you didn't set any group is by default the OP's) it try identify smthing and crash.

    Just saying, not sure exaclty about this system or thing.
     
  31. Offline

    Cruxsky

    @Acru there is a MAJOR exploit with this plugin. If you dig under a chest and place a fence gate under the part of the chest with the private sign, itll say Conflicting door removed and that part of the chest will break making it not private anymore!
     
    WillemSV likes this.

Share This Page