[SEC] Lockette - Simple chest and door lock, no databases! [Moved to BukkitDev]

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:

• French by Misa
• German by Efstajas
• Polish by Kamild1996
• Dutch by Tofun
• Danish by Dumle29
• Slovenian by LiqouRiiCe
• Spanish by Agubelu
• Norwegian by Tio1999
• Swedish by TheMineKraftor
• Italian by Nikkolo_DTU

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.)



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 (Permissions) (close)

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 (close)

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 (close)

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!

 

Turn them off completely, No, you can however set the messages to "" or '' in the config so it sends a blank message

 

Mhmm, you can do that, though I actually got around to adding an option for this in 1.3.5 too~
I just need to finish autodoors now...

 

Here:

 

fixed soon ? The prob is people can break sign with mcmmo ?

 

Thanks.

mcMMO problem has been worked around, and automatic doors are in and working nicely~

Though it currently effects all private doors, not just configured ones! I just have to make the timing on the doors configurable on the private signs, and I will put out the update.

Here is version 1.3.5, let me know how things go...

fix'd

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

The incompatibility will be fixed in .11 of WolfPound, my apologies. Thanks for discovering this! (and thanks to @Acru for the notification!)

 

Goodgood~ :3

 

good, i try it
edit: it works, nice work

 

Mcmmo compatible = wonderful
Close automaticaly : yes !!!

Thank you

 

It may be a tad premature, but lockette cant lock any objects on 689.
Existing locks seem to hold.

 

Yeah all the signs prior to the awesome weather change, (1.5) work fine, but you can't add anymore signs

/sadface. But I got teh patience to wait

 

Same with me. Looks like another update is necessary...

 

Same with me .

 

It looks like they mistranslated the sign event coordinates again.
This happened in the 1.3->1.4 transition too.
I'll try to call their attention to it... ;.;

 

hey, i keep on getting this message when trying to lock a door or sign:
Lockette: No unclaimed container nervy to make private!
Any ideas on how i can fix this!

 

It's the same problem as the 612-617 builds

You can't fix it in lockette as it's a problem for the bukkit team, I'm looking in to a dirty fix where you use 1 plugin to place a sign on a chest and another to changed that sign to a lockette sign

Lockette checks for signs with [Private] or the server specific alternative AFAIK so this SHOULD work (Untested)

 

work fine with Bukkit 705+ now!

 

Confirmed here as well. Tested doors, chests, and furnaces.

 

Now it seems that the autoclose doesnt work though.. atleast not on 705.
Edit: it works sometimes it seems, and sometimes it gets confused at to what position the door is in. So it ends up opening the door instead.

 

It was 605-612 before, and 685-703 this time. This problem is fixed in 704+ now though~ :3
See: http://leaky.bukkit.org/issues/696

I'll have to look into this once things become a bit more stable.
I had it working perfectly in build 684 too... :<

Edit: Incidentally, while yer at it, is there any diff between using wood and iron doors? As in, is one working fine but not the other?
Edit2: Actually, could you perhaps be using the door in conjunction with redstone and the [Everyone] tag? That might confuse things.

 

Wooden door with [Everyone] tag. It did correct itself after a while and since then its been fine.
Edit: its when you lock a open door that it gets a little out of whack. Also, if you have a timer on either door or global and bypass a door - does it really have to spam make sure you lock the door behind you thing?

 

Lockette 1.3.6 don't work with Bukkit#689 ;(
"No unclaimed container ..."

 

You should close the door before locking, yea, as it assumes the initial state is closed. As for the message, you can always disable it in the strings.yml. Though yea, I suppose its not really needed for automatic doors. :3

Its bukkit build 685-703 that doesn't work correctly. ;3
There is no recommended build yet for 1.5, but I would suggest the newest.
(I've tested with 705, and all seems ok.)

 

Thanks thanky thanks nice work

 

Hey,

Do you have any idea on when you'll be able to add iConomy support for a price on chest locking?

 

Hmm, if you open a door and teleport away it also seems to go out of whack, forgetting to close it and then it stays open, any attempt to close it will again open it. Do chunks unload that fast?

 

Thank you for updating this!

I have to say, I have run a Minecraft server for over 4 months, been through hmod and all that and this has to be the best chest protection plugin that there is.

 

I have a chain of groups like this: Guest > User > Mod > OP > Admin in the specified order. Problem is i really dont want to add all those groups to my signs. So what i would like is a recursive type of permission system. So if you add User group to the sign then User and ABOVE get access automagically. ofcourse poor Guests still wouldnt get access. Permissions plugin has the support for this with the inheritance tag and other plugins, like PermissionsPlus, use it well.
Second thing, I have started noticing that some doors tagged with [Everyone] has become bugged/jerky and unopenable for sometimes several minutes before they get their act together and start working. Server is not overloaded in any way. The doors in question are both wood doors, one being a double door and the other a single door type. No error messages in console or anything. Users dont get any errors either, it looks like lag kinda they say. Using CB714 and not using any other sign related plugins.
Edit: I may have been hasty, issue persist even after removing sign. Dont know if its really lockette, proximity to spawn or the new 1.5 crapbukkit... Could be either or a combo.

 

just saying but it doesnt work with my 1.5 server :/

 

Details would be nice