Block that Recipe!
Now with 100% more furnace support!
This plugin does NOT support Tekkit!
BanRecipe is a plugin designed to stop certain people from using certain recipes, stop certain people from enchanting certain things and stop people from smelting certain things. It is designed as an improvement over other plugins such as NoCraft, as this plugin allows you to block individuals using permissions.
A BukkitPerms Manager (e.g. PermissionsEx or PermissionsBukkit) - Not required, but greatly improves functionality
- Allows items listed in the config to to be blocked from crafting!
- Items can have permissions that allow users to still be able to craft blocked items. Items can share permissions (that means less clutter in your permissions.yml)!
- Does not affect the ability to have or spawn the item, only craft it. Very useful for RP servers with group specific traits.
- Customisable message sent to user trying to craft.
- Allows specific enchantments to be blocked from use with customisable message!
- Permissions allows for control of enchantments too.
- No need for Spout or any other external plugin!
- Allow certain items to be blocked from smelting - stop people ever making gold ingots again!
I would like to make it clear that I do not officially support mods. While my plugin should work with most mods, some mods don't, the mods this plugin are not compatible with are included in the list below:
How to use the Plugin
Make sure to read up on how to use the plugin before you download!
- Only command is /banrecipe reload in order to reload config file.
(Enchantments are based in permissions, Craft Items and Furnace Items are based in the config.)
- Potion support (only possibly).
- FURNACES! FURNACES! YEAH! You can now block smelting items.
- Data value blocking! Now you can block individual wool colours etc.
- New command - /banrecipe reload. This allows you to reload the config without restarting server!
- Added new option to enable/disable enchantment blocking (default=true).
- MAKE SURE TO DELETE CONFIG BEFORE UPGRADING!
- Big overhaul of code and config.
- Spout support dropped
- Enchantment blocking
- New method of recipe blocking
- BanRecipeHook API merged into code.
- Changed from Permissions 3 to SuperPerms
@Afforess and the rest of the @SpoutDev - Greatly helped with this project. Everyone else who helped in the thread I posted regarding help :p
Oh yeah !! Very nice, but v.1.0 of your plugin, not Minecraft 1.0 lol
It doesn't require spout since version 1.0 :D
Hi, wonderful plugin and very useful. But why spout server plugin is required ? You cannot make this plugin without Spout ? I ask you that because Spout doesn't like the command /reload... We have to stop the server and re-start it. This is unhappy ! Thank's
You ban an enchantment by NOT giving them the banrecipe.enchantment.insertenchantmentnamehere permission. No you cannot ban certain levels of it.
how do i ban a enchant and can i just ban certain levels of it?
It works based on the outcome of the recipe, not how the recipe was created. This means you can have custom IDs blocked and custom recipes.
Glad you got it working :D
Terribly sorry x) it didn't even have anything to do with your plugin. It was because of a default config for a custom recipe plugin I had installed a few days earlier. I hadn't paid any attention to that plugin beforehand though, so it was hard for me to realize that was causing the problem.
So... Yeah. Sorry about this. But it's nice to know that your plugin handles custom recipes as well! So many new possibilities!
That's really strange, it worked fine for me!
Try starting with a new config and adding each id one by one.
Plugin is easy to work with and it fits SO well with my rpg server :) I restrict recipes into races/classes, and my users really love it.
However, there's one thing that's bothering me, just slightly. It has probably something to do with the config.yml and will be fixed if I clear it... but apparently, users with permission to craft iron shovels, can craft 6 stacked iron shovels from a single iron ingot when they put it anywhere in a workbench. And users without that permission who tries the same, will get the message saying they can't craft iron shovels. Is this something you recognize?
I probably messed something up in the config file though :) added so many nodes in it, it's gonna be hard to find out which one's causing this.
For the next version, I'm adding in data value support and a * block id which allows you to block everything.
I never promised furnace support, but I did try and get it. I sent several requests to both bukkit and spout for a feature I needed to be added but they never got answered.
Actually, in the last version putting "banrecipe.*:false" would ban people from crafting anything which was the only reason I got this plugin.
Also, shame to see the promised feature of banning recipes on furnace will no longer be developed. I guess you are going in a completely different direction from what I thought it would go on this plugin.
I can add a reload command, yes.
Would there be any way you could add "on-the-fly" item banning via command ingame?
Perhaps even as simple as holding the item and using a command
And also a reload command ?
Delete your config and try again :D
I got a null ;(
In answer to the first question, it currently doesn't handle data values at all, unfortunately :(. I am working on it though.
It will work absolutely fine with custom blocks, as it is purely ID based. However, the auto crafting table will definitely NOT work.
How does your plugin handle data values such as wool?
Can I block all wool colors with
Or must I create a new ID for every color of wool?
A second question. How well does your plugin handle custom block IDs? If it is all simply ID value based I would expect it to be just fine. I am wanting to use this plugin for a tekkit server and I wanted to block some of the more, overpowered items, and a lot of them have data values attached to them.
I have a feeling you will not know the answer to this question and I will simply need to test it and get back to you, but Tekkit has an auto crafting table, capable of instantly crafting items and throwing them into a chest as long as the materials are fed into the table properly. Do you know if your plugins will deny even an auto crafting table to craft recipes?
The wildcard was not to ban all recipes, but allow their crafting.
Because the user creates the exemption permission themselves it is impossible to have a wildcard permission.
Your last version had wildcard (*) to ban all recipes. It was the main reason I got this plugin. Can you do this in 1.0 now?