Permissions
Permissions
Items and Furnace Items
There are no hard coded permissions for item blocking. They are user defined, in the config.
There is also no banrecipe.* permission node as it is impossible to tell what nodes the user will define.
If an ID is added to the config list, then it will be blocked. If a user is given the permission beside the id (separated by an '='), then they will be able to craft it even though it is blocked.
Enchantments
banrecipe.enchantment.*
This allows access to every enchantment. The following permission nodes allow access to individual enchantments:
banrecipe.enchantment.power banrecipe.enchantment.flame banrecipe.enchantment.infinite banrecipe.enchantment.punch banrecipe.enchantment.sharpness banrecipe.enchantment.baneofarthropods banrecipe.enchantment.smite banrecipe.enchantment.efficiency banrecipe.enchantment.unbreaking banrecipe.enchantment.fireaspect banrecipe.enchantment.knockback banrecipe.enchantment.fortune banrecipe.enchantment.looting banrecipe.enchantment.respiration banrecipe.enchantment.protection banrecipe.enchantment.blastprotection banrecipe.enchantment.featherfalling banrecipe.enchantment.fireprotection banrecipe.enchantment.projectileprotection banrecipe.enchantment.silktouch banrecipe.enchantment.aquaaffinity
If a player does not have the topmost permission node, or (for example, silktouch) any of the individual permissions they won't be able to use that enchantment (such as if a pickaxe is going to be enchanted with EFFICIENCY V + SILK TOUCH I, it will be denied because they only have the silktouch permission).
Reload
banrecipe.reload
Allows you to use the '/banrecipe reload' command which reloads the config.
How do you make specific permissions
"There are no hard coded permissions for item blocking. They are user defined, in the config."
The default config has some example permission nodes next to some of the banned items.