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