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
ive found a very big issue at least on my server... when using antibuild and the person does not have permission to use an anvil if they hold a torch in hand they can still open the anvil and use it. does anyone else have this issue?
whenever I use antibuild bypass it overrides my blacklist same with when I use antibuild place it still overrides the blacklist and yes the blacklist is set to true other question is can yu use wildcards like -antibuild.place.* and then - -antibuild.place.39 for being an exception?
@MutinyCraft
It should work. What exactly are you trying to do?
antibuild.blacklist.[ID] don't work with GroupManager... :S
I have :
And :
But my players can't add itemframe... why?
@TheFirstCastlecrafter
No at the moment.
@Blabla72
I would have thought adding \n would work for a newline. Let me look into that.
This plugin is amazing! EssentialsAntiBuild is a very shit So, how can I go to newline for messages? "\n" don't work... :S
This plugin is lighter than EssentialsAntiBuild (less lag)?
does it work with potions and food cause it doesn't seem to on my server maybe im missing something
There is a bug: You can rotate items in ItemFrames without permissions. Please fix it :D thx^^
@TheFirstCastlecrafter
It works great with 1.6.2.
@Mr_Wired
What do you mean? Like for armor and weapons? Or what?
When are you updating to 1.6.2 and putting in the new update for antibuild with new items and such?
Can you please add in 'antibuild.interact.ID' and 'antibuild.interact.ID.[metadata]'?
@MutinyCraft
thank you that worked
@TonyVS
In the config.yml just delete the messages and leave the two single quotes. So it should just be like this:
Awesome plugin, one question (noob question) how do I turn off the notifications? like - essentials.protect.alerts.notrigger (doesnt work for antibuild) :( I want the protection just don't want people getting spammed with notifications thanks and keep up the good work
@jnoshima
Can you private message me your permissions file? It sounds like you might have setup the permission wrong. I will admit that this plugin can be a little difficult to setup if you want to customize it very much, but I will be glad to help you get it working. Just send me a PM with those things and I will see what I can do.
@MutinyCraft
sure :)
http://pastebin.com/r22aM541
only thing I changed in it though is setting the per-block-permission to true
@jnoshima
Can you Pastebin your config.yml?
I'm a little lost...
I've up the permissions file like so for this one group:
Member: default: true permissions: - essentials.tpa - essentials.tpaccept - essentials.tpdeny - essentials.rules - antibuild.interact - antibuild.place.323 - antibuild.pickupitems - antibuild.dropitems inheritance: [] info: prefix: '&f' build: false suffix: ''
and I've ensured that my world isn't locked and that I'm set to be apart of this group and that I'm deoped, but it still won't let me access chests
I've changed it to antibuild.chest and used both antibuild.chest and antibuild.interest but none of them seem to work to allow me to open chests... Edit: I can't seem to place signs either (block:232)
Other than this little thing I can't work out, this an awesome plugin :D
@donsavage1
This will be added in the future.
@Blue_Mountain
You can't lock a world and then let them do certain things. If you wish to do what you are saying you will need to give them only the permissions for what you want them to do and not antibuild.bypass. If you want them to only be able to open chests you should only give them antibuild.chest and no other permissions.