BanRecipe
BanRecipe
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.
Dependencies
A BukkitPerms Manager (e.g. PermissionsEx or PermissionsBukkit) - Not required, but greatly improves functionality
Features
- 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!
Mods
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:
- Tekkit
How to use the Plugin
Make sure to read up on how to use the plugin before you download!
Server Owners:
- Config...
- Permissions...
- 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.)
Planned Features
- Potion support (only possibly).
Changelog
Version 2.0
- 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!
Version 1.0
- Big overhaul of code and config.
- Spout support dropped
- Enchantment blocking
- New method of recipe blocking
- BanRecipeHook API merged into code.
Version 0.4
- Changed from Permissions 3 to SuperPerms
Special Thanks
@Afforess and the rest of the @SpoutDev - Greatly helped with this project. Everyone else who helped in the thread I posted regarding help :p
Could you update to R6?
@gawelium
Yeah, that Permissions tutorial is assuming you have PermissionsBukkit, not PermissionsEX. Glad you got it figured out :)
Hi, great plugin ,thank's ! But I use PermissionsEX and i've got severe errors in console. For testing my config in banrecipe is :
and in PermissionsEX permissions.yml, for a group :
When I login to the server, more spaces are create in the permissions.yml and i've got this message in chatbox : java.util.regex.PatternSyntaxException: Illegal repetition.
It's strange.
Do you see the probleme ? why more spaces were creating ?
EDIT : I fix it like this :
Works very well, for the moment, in 1.1 !!
@rellac
You should be able to restrict it, yes. What permissions system are you using?
Are we supposed to not be able to restrict Bread? It's quite useful to restrict it with the setup I have, but I can't seem to restrict it, AT ALL.
@Phibedy
No, not at the moment.
Is it possible to add item like 44:2 (wooden slabs) and so on?
best reg. Phib
Indeed, that's work with 1.1!
Really nice, thanks Zantom for this plugin!
@Phibedy
Really? Awesome! Thanks for letting me know.
Furnace and brewing support is impossible (I lie - the idea behind this plugin is permission support, and it is impossible with permission support) :(. Since it occurs over time, and the menu can be closed it is very difficult to get the person who did it, and therefore difficult to apply the correct permissions.
Still works with 1.1. Could you add furnance and brewing support in the next update? Would be amazing.
best reg. Phib
@Phealoon
Sorry that it confuses you :(. At the moment, it doesn't even work with the latest builds of spout and bukkit because I don't want to update until I can remove spout dependency.
However, I'll explain anyway. In PEX, you could ban tnt like this:
The first node tells BanRecipe that this person can't craft tnt. The second node tells BanRecipe that they can craft everything else.
Since PEX works in a top-down fashion, the banning node (- -) must come before the allowing node (- ...... .*).
Let me know if you need any more info.
This plugin seems very interesting but the explanation of how to set permissions up with PEX was not clear. I read something about adding - or
before the node, but this breaks everything. So can someone show me an example of how to set up a basic permission node for a player to be blocked from crafting a certain item.-Phea
@Drakisban
Yes, it even works with custom items added with spout. However, as mentioned in about the last 10 comments it does not work with the latest RB and won't until a specific feature is added to Bukkit.
Is it possible to block recipes, created with http://dev.bukkit.org/server-mods/recipemanager/ for some groups? For example i want one group to craft Obsidian. My idea is to create a recipe with RecipeManager and ban it with BanRecipe for the other groups.
Any idea when the furnace support will be added?
RecipeManager already has furnace support which also uses Spout. It doesn't support permissions so I couldn't use it.
@SydMontague
INVENTORY_TRANSACTION. It's in the enum but InventoryTransactionEvent does not exist.
The very build they put it in I'll release an update.
@Zantom07
What means you wait until bukkit implements a crafting Event? x_X
@SydMontague
@kozzy68
It will be updated when I no longer require Spout.
Good plugin but too bad its using that damn spout it just adds another layer that can break things or get inactive.
@Zantom07
How long will it take until it's updated?