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
@saimon13
Let it craft. So, -259=banrecipe.259 would block it, and anyone with the permission banrecipe.259 would be allowed to craft it.
I dont get it with the permissions on 1.0 so if i do -46=banrecipe.tnt so in permissions i need to put in banrecipe.tnt: true to ban or let it craft?
@pandapipino
The newest version (1.0) hides it from the table, but as with any server side operation it will still appear for a split second. NoCraft uses a different method entirely that sets it on the server permanently. If NoCraft is a good option for you, I can try and update it to 1.2 for you.
I was a previous "NoCraft" plugin user and it works well for me.
I noticed that the banned item in banrecipe still appears on the crafting table while placing the recipe, is there a way not to display the banned items being crafted? because in my past experience my players was able to abuse it while the server is lagging badly, I think it is much better when the items being crafted has no delay at all. Thanks
@Yamakaky
In that case, by all means have a look at my code. :)
Don't worry, it's for learning. I'm bukkit dev on a serv. We use a lot of mods, and sport make it bug. I tried to create events, but it wasn't a succes...
@Yamakaky
If it's purely for learning, I'm don't mind you using a decompiler to look at my code (search: jd-gui). However, if you intend to steal my plugin, please don't. I've got an 'All Rights Reserved' license there for a good reason.
Hi Is it possible to have the sources ? I really want to know how you did that.
@Pandamatak
You're using the wrong version.
Version 1.0 only blocks what you set in the config.
Could I request to make it so that BanRecipe doesn't ban all recipes for a player by default? Because whenever a new person logs in I have to give them the banrecipe.* permission.
@eaglezeyez
In your permissions file, give the Tree group the permission node: permission.to.allow.crafting
I have a question.
IF I have a Tree group in my PEX file. I disabled all the diamond tools and equips by using permission.to.allow.crafting
How can I allow Trees to use it?
Awesome!
@SydMontague
@Pandamatak
@Phibedy
Updated :D
@SydMontague
There is a possibility, yes :)
Are you removing the spout dependency with the next version?
@Pandamatak
Sometime next week, I hope. I'm happy to send you a PM, that's no problem :)
It will have:
Got an ETA on when you might be able to release the R6 update?
This is an amazing plugin I can't live without.
Oh, and could you send me a PM when it's available?
Thanks a bunch.
@SydMontague
@Phibedy
Yes. I'm planning on updating for R6 and the new event system, I'll also include the source with this update.
However, SydMontague, I'm happy for you to update it whenever, use a decompiler if you like. As long as you don't claim the plugin as your own I really don't mind at all.
Will you release the source for this at any time?
I don't like to use closed source plugins, as they can't be fixed when the author gets inactive and the plugin broken.