[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

    sfmplayer

    So is it possible to remove lockette signs after a few days an chest or item isnt used ?
     
  3. Offline

    Carlos Fuentes

    Could someone possibly help me out with disabling the admin snooping message? I take a lot of looks through suspicious players' chests and I don't want them to know.
     
  4. Offline

    Greylocke

    Just change the broadcast targets in your config. Mine all go to the admin group, and it looks like this:
    Code:
    broadcast-snoop-target: '[admin]'
    broadcast-break-target: '[admin]'
    broadcast-reload-target: '[admin]'
    That way you can still see if Moderators or other groups are snooping.
     
  5. Offline

    xxkvatchxx

    Sounds like a great Plugin ,but is not working with the latest CraftBukkit Build.
     
  6. Offline

    LlmDl

    Use lockette 1.7.7 its on the dev.bukkit org page
     
  7. Offline

    apa0318

    Carlos Fuentes
    bukkit\plugins\Lockette\strings-en.yml
    msg-admin-release: ''
    msg-admin-snoop: ''
     
  8. Offline

    generalmek

    today see how player broke sight take items and make sight again. maybe new cheat or bag. dont know.

    logblock tell strange mesage, but show nick. its second player who hack lockette.

    i use 1.3.2 last recomended cb and last lockette
     
  9. Offline

    Wolf3141

    Can I get some help I haven't been able to right click on a chest and put a sign down. I have the sign in my hand it just opens the chest. This is with ops, nonops, admins, default (with the .create.* node)

    No config file is ever generated but the .jar is in the plugins folder and it loads in the server.cmd?
     
  10. Offline

    LlmDl

    no lockette version, no bukkit version, no startup from server.log
     
  11. Offline

    Wolf3141

    Thats because everything is up to date and i dont get errors.
     
  12. Offline

    Greylocke

    If all the features of Lockette are not working and the Lockette folder with a default config.yml is not created, then I'm guessing that Lockette is not loading. Check your server.log file for evidence that Lockette is (or isn't) loading. I don't know what "server.cmd" is, but all you should need to do is drop Lockette.jar in the plugins folder, which should be in the same location as your craftbukkit.jar.
     
  13. Offline

    Wolf3141

    Yep all my other plugins work fine. Sorry the server is opened using the cmd so i just called it the server.cmd. the server log DOES say lockette loaded and it DOES report lockette under the console command /plugins.

    EDIT: Ok I'm really confused. I just downloaded the CB:R:1 '1.4.5' and it worked, but that version of bukkit broke all my other plugins terribly. But going back to Craftbukkit RO2 (which this version of lockette is supposed to work with) [Info]Lockette tells me "detected craftbukkit build [2488], but requires build [2502 or greater]. Aborting enabled"

    Why the rest of my plugins break with the recommended build when they worked with the RO build I have no idea also....
     
  14. Offline

    BioSmasher

    This plugin needs to be updated to 1.4.6. Chests are no longer locked and can be stolen from.
     
  15. Offline

    LlmDl

    Please supply your bukkit version, lockette version and your full server startup on pastebin.com
     
  16. Offline

    jhonwds

    I get the same thing.. this needs an update asap..
     
  17. Offline

    Greylocke

  18. Offline

    BioSmasher

    Not exactly possible (CB is updating too fast) or necessary. It affects all lockette versions and all CB versions 1.4.5 R1.0-14.6 R0.1


    There are new references that refer to the specific version. That is the most likely break with the plugin. The startup log is completely normal.

    That's my ticket :). Temp but crude workaround is to disable all chest opening through Worldguard blacklists until it's fixed.

    Smack that vote button! We need a fix!
     
  19. Offline

    Greylocke

    should be able to recompile against the 1.4.6 craftbukkit to pickup the proper references. But the ultimate solution is not to compile against craftbukkit at all. (Assuming that the new path is the problem)
     
  20. Offline

    MoseMister

    yer, quick question
    when will you be updating to 1.4.6,
    the code has changed since 1.4.5 beta build 0.2

    so if you could say a date, or idk or something like that plz
    thx
     
  21. Offline

    LlmDl

    Anyone experiencing trouble should be posting the following:

    Craftbukkit version:
    Lockette version:
    Full server startup and any errors on pastebin.com or pastie.org:

    Without the following we cannot tell what you're using/if what you're using is causing your trouble.

    I have tested Lockette 1.7.7 with the 1.4.5-R1.0 Recommended Build and it works. As for whether Lockette works with 1.4.6 I have not tested this, but the people who say it is not working for them have not said which lockette version they are using.
     
  22. Offline

    ibab

    Craftbukkit version: 1.4.6-R0.1 (Beta)
    Lockette version: 1.7.7

    No errors from Lockette whatsoever. The protection just does not work. Anyone can open anyone's chests and protections can not be created.
     
  23. Offline

    chopstick121

    my friend said the server lagg when i added Lockette

    Craftbukkit :1.4.6-R.02
    Lockette 1.7.7

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

    LlmDl

    Elgarl has just tested Lockette 1.7.7 and 1.4.6, it works fine.

    If you are having trouble still then pastebin.com your full server startup and I will respond. No startup? No service.

    I present Lockette 1.7.9, compiled against CB 1.4.6 r0.1. All thanks go to ElgarL.

    This fixes trapdoors not locking/detecting locks properly.

    Added Anvils to the default custom block protection list.

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

    ElgarL

    Github was down.
     
  26. Offline

    [qwerty]

    I keep getting this crap spammed in my log ever since I updated......

    Code:
    2012-12-24 13:59:26 [INFO] face = 0
    2012-12-24 13:59:27 [INFO] TrapDoor
    2012-12-24 13:59:27 [INFO] face = 0
    2012-12-24 13:59:27 [INFO] SenpaiSakura[/--] logged in with entity id 15588 at ([Players] -1484.300000011921, 63.0, 400.6023351925161)
    2012-12-24 13:59:27 [INFO] [ChatSuite] [Global] SenpaiSakura was allowed entry.
    2012-12-24 13:59:29 [INFO] Master_Cheez issued server command: /home
    2012-12-24 13:59:34 [INFO] [DonorUltimate]nicholasmmm: That's a slow washer.
    2012-12-24 13:59:37 [INFO] [Player]Master_Cheez: Ya
    2012-12-24 13:59:38 [INFO] [Donor]LEGOultra: Yes it is
    2012-12-24 13:59:41 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:42 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:42 [INFO] [Lockette] jamesfox429 has claimed a container.
    2012-12-24 13:59:43 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:44 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:44 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:45 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:46 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:47 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 13:59:48 [INFO] [DonorUltimate]nicholasmmm: Takes about, what, 20 days?
    2012-12-24 13:59:51 [INFO] face = 0
    2012-12-24 13:59:54 [INFO] [Donor]LEGOultra: I dunno.
    2012-12-24 13:59:56 [INFO] [Player]Master_Cheez: 42 is my guess
    2012-12-24 13:59:59 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:00 [INFO] [DonorUltimate]nicholasmmm: Lol.
    2012-12-24 14:00:01 [INFO] [Donor]LU_HelixDrago: I know I made it 5 years
    2012-12-24 14:00:03 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:04 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:06 [INFO] [DonorUltimate]nicholasmmm: Lol.
    2012-12-24 14:00:07 [INFO] [Donor]LEGOultra: :O
    2012-12-24 14:00:10 [INFO] [Donor]LU_HelixDrago: :O
    2012-12-24 14:00:11 [INFO] [Player]Master_Cheez: 9999999999 eons
    2012-12-24 14:00:19 [INFO] [DonorUltimate]nicholasmmm: Good timing then, LU.
    2012-12-24 14:00:19 [INFO] [Donor]LU_HelixDrago: what are eons?
    2012-12-24 14:00:21 [INFO] puppy10605 drowned
    2012-12-24 14:00:24 [INFO] [Player]Denver_497: Infinite eons!
    2012-12-24 14:00:26 [INFO] Z1ggie[/--] logged in with entity id 22642 at ([Players] 909.623124918873, 64.0, 859.7037345479108)
    2012-12-24 14:00:26 [INFO] [ChatSuite] [Global] Z1ggie was allowed entry.
    2012-12-24 14:00:27 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:28 [INFO] [Player]Master_Cheez: like a thousand years
    2012-12-24 14:00:30 [INFO] [DonorUltimate]nicholasmmm: Eons are long.
    2012-12-24 14:00:38 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:38 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:38 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:39 [INFO] Door clicked: allow = true : isProtected = true
    2012-12-24 14:00:50 [INFO] Door clicked: allow = true : isProtected = true
    
     
  27. Offline

    stuntajai

    My real question here is with the new updating of the code, and the new ability to place items on chests will lockette be able to work the same as it did before. I have no errors but am having issues with the sign placement and find a way for doors to with the sign being placed outside on block next to the door(since placing above isn't work)
    I am using CB 1.4.6 Ro.1
    lockette 1.7.9
     
  28. Offline

    WoodenAxe

    Code:
    2012-12-25 16:09:24 [SEVERE] Could not pass event PlayerInteractEvent to Lockette v1.7.7
    org.bukkit.event.EventException
    at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:427)
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
    at org.bukkit.plugin.TimedRegisteredListener.callEvent(TimedRegisteredListener.java:35)
    at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477)
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462)
    at org.bukkit.craftbukkit.v1_4_6.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:178)
    at net.minecraft.server.v1_4_6.PlayerInteractManager.dig(PlayerInteractManager.java:114)
    at net.minecraft.server.v1_4_6.PlayerConnection.a(PlayerConnection.java:564)
    at net.minecraft.server.v1_4_6.Packet14BlockDig.handle(SourceFile:46)
    at net.minecraft.server.v1_4_6.NetworkManager.b(NetworkManager.java:290)
    at net.minecraft.server.v1_4_6.PlayerConnection.d(PlayerConnection.java:112)
    at net.minecraft.server.v1_4_6.ServerConnection.b(SourceFile:39)
    at net.minecraft.server.v1_4_6.DedicatedServerConnection.b(SourceFile:30)
    at net.minecraft.server.v1_4_6.MinecraftServer.r(MinecraftServer.java:585)
    at net.minecraft.server.v1_4_6.DedicatedServer.r(DedicatedServer.java:224)
    at net.minecraft.server.v1_4_6.MinecraftServer.q(MinecraftServer.java:481)
    at net.minecraft.server.v1_4_6.MinecraftServer.run(MinecraftServer.java:416)
    at net.minecraft.server.v1_4_6.ThreadServerApplication.run(SourceFile:849)
    Caused by: java.lang.StackOverflowError
    at net.minecraft.server.v1_4_6.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:89)
    at net.minecraft.server.v1_4_6.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:85)
    at org.bukkit.craftbukkit.v1_4_6.CraftWorld.getChunkAt(CraftWorld.java:187)
    at org.bukkit.craftbukkit.v1_4_6.CraftWorld.getBlockAt(CraftWorld.java:151)
    at org.bukkit.craftbukkit.v1_4_6.block.CraftBlock.getRelative(CraftBlock.java:160)
    at org.bukkit.craftbukkit.v1_4_6.block.CraftBlock.getRelative(CraftBlock.java:168)
    at org.bukkit.craftbukkit.v1_4_6.block.CraftBlock.getRelative(CraftBlock.java:164)
    at org.yi.acru.bukkit.PluginCore.getTrapDoorAttachedBlock(PluginCore.java:849)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:1046)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:1046)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:1046)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:1046)
    at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:1046)
     
  29. Offline

    ElgarL

    Works fine above here.
     
  30. Offline

    WoodenAxe

    updated to 1.7.9 and also getting spammed in console with:

    Code:
    13:29:18 [INFO] TrapDoor
    13:29:18 [INFO] TrapDoor
    13:29:19 [INFO] TrapDoor
    13:29:19 [INFO] TrapDoor
    13:29:19 [INFO] TrapDoor
    13:29:20 [INFO] TrapDoor
     
  31. Offline

    Maxetto

Share This Page