Deadbolt
Features
- No databases. In-game signs only.
- Super permissions support ONLY.
- Protects any type of furnace, dispenser, chest, door, trapdoor, cauldron, enchantment table, or brewing stand.
- Broadcast specific admin actions to those with "deadbolt.broadcast.xxx"
- Denies explosions, pistons, and redstone from circumventing protection
- Timed doors, [Timer:#], that toggle after a certain delay
- Server-wide protected blocks, use [Everyone] on line 3 or 4
- Modular plugin hooking system, add your own easily
- Compatible with Lockette
- Optional sign coloring
- Localization support
Notes
As this is a Lockette-type plugin, also similar to Alerter or BlockLock, things may seem similar. This plugin was originally created as a continuation of Lockette by Acru to add trapdoor support and other recent developments. Portions of this project were reverse engineered from Lockette and the original idea for a sign-based locking system still belongs with Acru. Credit where credit is due. As this only supports super permissions, if you need a plugin that is more backwards compatible with older configurations, you may want to look at Lockette.
If you have another plugin such as Cenotaph or ChestShop3 that you have integrated with Lockette and would rather use Deadbolt instead, I have created a LocketteSimulator that will allow you to use Deadbolt.
Check GitHub for the most recent files, there is a slight delay in getting files posted here authorized by the staff.
Usage
Place a sign next to the item you want to protect and type in the following
- Line 1: [Private]
- Line 2: Your name will be automatically filled, users with "deadbolt.admin.create" can specify someone else.
- Lines 3 and 4: You have a couple options for these lines
- Another player's name
- Unrestricted access via [Everyone] while preventing breaking
- Create an automatic timed door using [Timer:1] through [Timer:9]
Not enough room for all the names you need? Make another sign with the [More Users] on line 1
For ease of use in maintaining your signs without having to break them:
- Right click the sign to select it.
- Use "/deadbolt <line number> <text>" to directly modify that line.
When placing signs, valid locations are to the NORTH, SOUTH, EAST, and WEST of the target block.
Other valid blocks include:
- Doors: The blocks above and below.
- Trapdoors: The block that it is attached to (hinge-block) and directly above/below the trapdoor itself.
- Fence gates: Any block horizontally adjacent to the gate itself.
Use your imagination and hide those unsightly signs under walls.
Also, color is now available! Just add "deadbolt.user.color" and use &1-9,a-f in your sign.
Permissions
Configuration
Developer's Corner
DeadboltListener is a new system designed to incorporate your favorite plugin directly into Deadbolt.
To create your own or to view Deadbolt's static API, head over to the Developer's Corner
Currently available for download
- PermissionsBukkit, PermissionsEx, bPermissions, GroupManager
[GroupName]
- SimpleClans
[ClanName] [ClanTag]
- Towny
[TownName] [NationName] (All residents) +TownName+ +NationName+ (Assistant/Mayor only) 4 Config options: mayor,assistant,wilderness overrides.
Localizations
Have a completed localization? Drop me a link to it and Ill add it to the repository.
Once added, it is available for automatic downloading by changing the "language" setting in config.yml.
Available:
Issues?
The following issues are known:
- Double timer doors are broken
- Force coloring of Signs placed directly onto walls is broken.
- Vertical trapdoor chaining has been removed because it was only half implemented
Visit github and open an new issue.
Alternatively, try and find me at play.arkcraft.net.
+1 requesting an update. The furnace cluster feature is great, and lockette lacks that. Please md5.
Any chance for multiworld support so we can enable/disable in certain worlds?
Will there be an update for this? There are many known errors with this in 1.3.2
is there a way to get into a locked chest like use a piston???
Hey, md_5, love your work !
Just asking, does the Towny listener still work ? The last update to that was in 2011.
Where can a find a bPermissions listener these days?
@md_5
But vertical chest stacking still doesn't work and fix seems to be really easy (but I might be wrong..) I think you could just change searchChest(block, true, false); to searchChest(block, true, true); in Deadbolted.java and it would work again...
Good good
@Greennou99
It works
Does deadbolt work with 1.3? It is at least the 2nd most important plugin on my server only next to logblock.
Explosion Issue
I set the configuration in the config.yml to both TRUE and FALSE for "deny_explosions", yet the chest does not explode! Can someone please explain why?
Is the bPermissions integration automatically installed (people can open based on group)?
@andfRe
I made a listener for Deadbolt that does this (checks WorldGuard canBuild before putting the sign on). If I can remember later, I'll put the GitHub link for it up.
Can you throw a BlockPlaceEvent before Deadbolt privatises a chest when you right click it?
The problem is when a plugin stops people from building in a certain area by canceling BlockPlaceEvents. It is still possible to privatise chests in that area. The problem can be solved on the plugins side, but imo it's Deadbolts responsibility, becase it is the one editing the world.
Is there a way to apply a user limit to the amount of deadbolt's you can have?
Any chance that this could support iconomy for renting access to a protected space?
I want to build area's and have doors that are protected, but be able to "rent" access to the door to my players.
How do you get towny support to work?
[TownName] and [ActualTownName]
neither work for me... am i doing something wrong? what is missing?
Feature Suggestion?
If it's possible, there should be a permission node you can add to certain players that allow COMPLETE privacy, even from the admin's or op's themselves. Say for example PlayerA is an admin and PlayerB is an admin both of which have the deadbolt.admin.* perm. node. Now lets say PlayerA doesn't want PlayerB to be able to access ANYTHING of theirs (such as a chest with the sign on it L1 - "[Private]" L2 - "PlayerA") they get the permission node "deadbolt.noaccess" or something along those line... and PlayerB can no longer open anything that only PlayerA's name is on. But PlayerA can still access PlayerB's stuff. (I need something like this for my server) (PlayerA, Me, and PlayerB, my Head Admin are both op's but Im adding most permission nodes to him so he won't be op anymore)
I found a bug: Deadbolt have conflict with the plugin "Grief Prevention". If you hit with right click of mouse with a sign on your hand, the iron door of grief protection<sub> this door open. Other is that if the player are /trust from other it can access the chests of the player if he offline 1 day.</sub>
Hi, can you make it were you can place a [private] sign above a fencegate like for example [privatesign] (fencegate)