AntiBuild
About
Simple, efficient, and lightweight plugin that will prevent interaction with blocks until the proper permission is granted. This plugins stops all types of block interaction and it even stops bucket use and painting interaction. It also sends a customizable message to the player who is denied building rights. Before you say this already exists just look at how lightweight this plugin is compared to some of the others. This is for server owners who need a building prevention plugin that is as lightweight as possible.
What is the advantage of this?
- As a server owner myself I have been looking for a long time to find a plugin that just stops my guests from building until they are promoted to the next rank. The only thing I found for this had so many other options that I did not want or need that it forced me to make my own. For comparison the plugin I was previously using was 400 times larger in file size than AntiBuild. Sure, it did a lot more, but I didn't want any of that other stuff.
Main Features
- Prevents breaking of blocks
- Only allow player to place certain blocks without having to blacklist a bunch of blocks
- Prevents placing of blocks
- Only allow player to break certain blocks without having to blacklist a bunch of blocks
- Prevents the use of flint and steel
- Prevents the use of lava and water buckets
- Prevents all interaction with paintings
- Prevents all interaction with item frames
- Prevents opening chests, furnaces, anvils, beacons, brewing stands, crafting tables, dispensers, enchanting tables, ender chests, and workbenches.
- Blacklist blocks
- Lock/unlock building in worlds with a command
- Simple to use
- Very efficient checks
- Extremely lightweight
Per-Block Permissions
AntiBuild allows you to give permissions to players that only allow them to place or break certain blocks. This is very handy when you only want a player to be able to place/break a few blocks. An example use would be an adventure map where a player is only allowed to break stone, log, coal ore, diamond ore, and iron ore. All you need to do is assign the player the permission node antibuild.break.[ID] and replace the [ID] with the block ID of the block you want them to be able to break. If you want them to be able to place only certain blocks you can give them antibuild.place.[ID] and replace [ID] with the block id of the block you want them to be able to place.
Blacklist
AntiBuild has a built in feature for blacklisting blocks by their Item ID. This is a 100% optional feature and it is disabled by default. To enable it open the config.yml and change the Blacklist-On value from false to true. Once it is enabled any block ID that is listed under Blacklisted-Blocks will be blocked from placing or breaking. If a player has the permission antibuild.blacklist they will be able to bypass the blacklist check completely. If a player has the permission antibuild.blacklist.[Item ID] (example: antibuild.blacklist.7) they will be able to bypass the check for that item ID only.
World Locking
AntiBuild also has a built in feature for locking worlds that you would normally allow players to build in. This is handy for adventure maps, special events, group builds, or any other reason you can think of to temporarily lock a world.
You can lock a world in game by typing /antibuild lock [world name]. Once this is done only people with antibuild.lock.bypass permission will be able to build. All others will be denied building rights. To unlock a world you would type /antibuild unlock [world name] and this will allow everyone to build that would normally have had access to build. To check and see what worlds are currently locked you can type /antibuilt list and this will display the currently locked worlds.
Commands
All commands will work from in game with the proper permission and from the console.
/antibuild reload | Reload the config. Requires permission: antibuild.reload |
/antibuild lock [world] | Lock the provided world. Requires permission antibuild.lock |
/antibuild unlock [world] | Unlock the provided world. Requires permission antibuild.lock |
/antibuild list | Display currently locked worlds. Requires permission antibuild.lock |
Permissions
Normal Permissions
Node | Usage |
---|---|
antibuild.bypass | Allows the bypass of AntiBuild checks. This is the main permission node that will allow/deny players from interacting. If you don't need any of the other features and just want to allow a player to build/interact give them this permission. |
antibuild.break | Allows the breaking of blocks |
antibuild.break.[ID] | Allows the breaking of block with the provided block ID |
antibuild.break.[ID].[metadata] | Allows the breaking of block with the provided block ID with specific metadata |
antibuild.place | Allows the placing of blocks |
antibuild.place.[ID] | Allows the placing of block with the provided block ID |
antibuild.place.[ID].[metadata] | Allows the placing of block with the provided block ID with specific metadata |
antibuild.fire | Allows the use of flint and steel |
antibuild.bucket | Allows the use of all buckets |
antibuild.bucket.lava | Allows the use of lava buckets ( fill and pour) |
antibuild.bucket.water | Allows the use of water buckets ( fill and pour) |
antibuild.painting | Allows interaction with paintings and item frames (break/place) |
antibuild.interact | Allows interaction with all inventory type blocks. |
antibuild.anvil | Allows interaction with anvils |
antibuild.beacon | Allows interaction with beacons |
antibuild.brewing | Allows interaction with brewing stands |
antibuild.chest | Allows interaction with chests (including storage minecarts) |
antibuild.dispenser | Allows interaction with dispensers |
antibuild.enchanting | Allows interaction with enchanting tables |
antibuild.enderchest | Allows interaction with ender chests |
antibuild.furnace | Allows the interaction with furnaces |
antibuild.hopper | Allows the interaction with hoppers |
antibuild.workbench | Allows the interaction with crafting benches |
antibuild.pickupitems | Allows the player to pickup items on the ground |
antibuild.dropitems | Allows the player to drop items from their inventory |
antibuild.blacklist.break | Allows the bypass of blacklisted blocks for breaking |
antibuild.blacklist.break.[ID] | Allows the bypass of blacklisted block with entered Item ID. Example: antibuild.blacklist.break.7 |
antibuild.blacklist.place | Allows the bypass of blacklisted blocks for placing |
antibuild.blacklist.place.[ID] | Allows the bypass of blacklisted block with entered Item ID. Example: antibuild.blacklist.place.7 |
Admin Permissions
Node | Usage |
---|---|
antibuild.lock | Allows user access to the lock/unlock/list commands |
antibuild.lock.bypass | Allows the bypass of locked worlds |
antibuild.lock.bypass.[world name] | Allows the bypass of locked world with specified name |
antibuild.reload | Allows access to the reload command |
Configuration
When you first run AntiBuild the plugin will generate a default config.yml and a lockedWorlds.yml. Do not touch the lockedWorlds.yml (lock worlds with in game commands). There are several options in the config.yml. You may not need to change any of them. See the comments in the config.yml file for information on them. The next option is whether or not you want the blacklist to be enabled. If you already have a plugin that blacklists blocks (or you just don't want to use it) leave it set to false and it will not do anything. If you set Blacklist-On to true you can now start to enter item IDs of the blocks you wish to block. This only supports item IDs because it saves a decent amount of time when checking block break/place events with just he ID instead of the name.
See the default config here.
Installation
- Put AntiBuild in your plugin folder
- Start server to generate default config.yml
- Use with the default settings or customize it to your liking and restart or reload the plugin.
Upcoming Features
- Feel free to make a request, but keep in mind this plugin will stay lightweight.
If you have a request please create a ticket here: https://github.com/MutinyCraft/AntiBuild/issues
Need help or just want to chat? Find me on EsperNet on #MutinyDev or #MutinyCraft
REALLY NEED HELP
Players get the message
YOU ARE NOT ALLOWED TO INTERACT WITH
How can i make it so the don't see the message?
Is there a permission node like -essentials.build.notify i can put it to make them not see any messages?
I don't want them to interact, but I don't want the spam for them.
Thanks in advance :)
Is their anyway to add player to build and destroy? And, can you make in R3? If so, it would be appreciate.
man after banging my head against a wall for a few hours trying to get all my modifyworld permissions to work, downloading and installing this was like a breath of fresh air. I literally only had to do the permissions once and it was working beautifully. Thanks so much.
Hey! Would it be possible to only allow building in a specified region with this plugin?
I could have sworn there was a value for hunger or am i thinking of another similar plugin?
For the blacklist, can we use metadata values in the nodes? Example:
The blacklist:
Permission nodes:
They would be able to break/place spruce and birch logs/leaves, but could not be able to break/place oak and jungle logs/leaves.
Is that possible?
How can I do to on a locked world player could open the chests?
Yeah, my awesome english. Sorry :s
thx man very nice plugin
When i download the file and put it into the plugins folder, it automatically downloads as a .jar file. I have a mac and please help me. No folder will appear and when i open my server and type /plugins, it doesnt list that its there. Please help!
can they interact with the jukebox
@ConquestServer
So I want the group "Level1" to not be able to break anything except for the items I put in the permissions. Did I do this correct?
Also, I set Per-Block-Permission in the AntiBuild config to True, and blacklist is on false.
@ConquestServer
I will look into that issue.
So. I want people to break Coal ore, iron ore, dark oak wood, and dark oak leaves. ONLY those items.
So I set Block Per Permission to true, and added the nodes.
- antibuild.break.161:1 - antibuild.break.162:1
^ Those are the permissions for dark oak wood & dark oak leaves.
Here's the problem. I set up Coal ore and Iron ore, and I can break them fine, but dark oak wood, and dark oak leaves don't work. I did them both exactly the same. Do I have to use the meta data one? I did -antibuild.break.162.1 and it still didnt work.
@haydenaa
It supports multi-world. You need to ensure that your permissions plugin is also able to support multi-worlds.
Is there possible there could be multi-world support? This would be the greatest anti-grief plugin out there if it could.
@haydenaa
This does work with multiple words. You just use world-specific permissions in your Permissions plugin, if it supports it.
Just an idea, I think you should make this for Multi-World use. I need a plugin like that really badly.
Hello, how do i change what they can/cant do? i want them to be able to drop items. Is there a way to do this?
@pvp100server
Yeah, PermissionsEx is a little buggy. Though keep trying! :)
@superzyr
My server uses Compass Navigation, too. Yes, in order to use the compass (or item), they need the perms compassnav.use or compassnav.use.[slot#]. Also, they need the anti build.interact permission to be able to interact with it. On top of all of that, the error message "This world is currently locked and cannot be built in" simply means that you have locked that world and cannot build/interact in it. Type /antibuild unlock [World ID] to unlock the world. All your problems should be fixed. :) Hope that helped, haydenaa P.S. Join my server @ 66.85.130.42:31686 for my Minigames / TF2 / QuakeCraft Hub! Were looking for a plugin dev! Also, tutorials on how to use plugins can be given at request! Join 66.85.13042:31686 Today!