BlockProt
BlockProt is a easy-to-use block and chest protection plugin. Players can lock chests, furnaces, doors and much more. Unlike traditional chest lock plugins, this uses a simple GUI with buttons to click. This removes the struggle of crafting signs or remembering commands. Especially for beginners, this plugin is very easy to grasp and use.
Features
- Protect chests, furnaces, shulker boxes etc.
- The plugin stores all data inside the blocks themselves, therefore doesn't need any backing database.
- Players can add friends to individual blocks that they can then access.
- Full redstone protection, if the player enables it in the block's GUI.
- All protections are saved as UUIDs.
- Players can configure their blocks with an easy to use GUI.
- OP Users and players with the blockprot.admin permission can remove chests and manage them.
- Full compatibility with WorldGuard, Towny and PlaceholderAPI!
- Available in 9 languages!
Permissions
Permissions are a Bukkit feature and not a custom thing of this plugin! Please refer to the permissions.yml file in your server or find another plugin to manage permissions (these usually have a lot of features and functionality).
- blockprot.lock: Allows players to lock blocks and access them.
- blockprot.info: Allows players to see the owner and friends of a locked block.
- blockprot.admin: Allows players to unlock blocks that they do not own
- blockprot.bypass: Allows players to bypass any protections, but doesn't allow them to edit blocks.
Translating
If you know a language that isn't supported by this plugin (yet) we'd love if you could translate for us!
You can do so easily by going to gitlocalize.
Support
Please do not use reviews or my profile for support, instead use you can file an issue over at GitHub. If you require more support or want to ask questions, please use the Discord server for chatting.
Usage
Once in game, crouch and right click a lockable block with an empty hand and you will see the GUI to lock/unlock blocks. For this to work properly, give the default player group the blockprot.lock permission. By default the block gets locked upon placing it., though one can disable this for themselves with the command /blockprot settings. All settings in that command are per-player. To give yourself the permissions listed above, use Bukkit's permission.yml file or see to some permission management plugin.
This plugin requires at least Spigot. CraftBukkit is not supported and shouldn't be used for non-development purposes anyway.
In reply to ppnda:
I tried the link you sent, but it was meant for PermissionsEx and when I pasted it into the built-in permissions.yml bukkit had no idea what to do with it.
I got it to work though:
You need to create a group first and then add the permission as a child.
That being said I have tried and there's no way to restrict people from using the default stuff like whisper or placing blocks or whatever so I can understand why everyone uses things like LuckPerms.
In reply to Elecktrus:
I merely suggested looking at and replicating the structure from the PermissionsEx's permissions file. Though I can understand if some people are overwhelmed with data files such as YAML (.yml). I really suggest just looking at LuckPerms or similar to have a more general user friendly interface that any user should understand without issue. I personally don't even know how to properly write a permissions.yml file :D
Can I prevent blocks from being locked by default? i need those settings.
How can I protect blocks without OP? Block protection should be available to people without OP, but I don't know how.
They require, as stated in the description, the "blockprot.lock" permission. Use a plugin like LuckPerms to add that permission to the default group of players on your server.
It needs NBT API to function (you have to figure that out after a restart);and the only command that is running is /blockprot update.
Edit: Its SHIFT+Right-click.. next time write these 2 things in the description.
ㅁ
The dependency for NBT-API is shown at the bottom of the download page, but I will add this to the description of the plugin.