- Native Minecraft Version:
- Tested Minecraft Versions:
- Source Code:
- Languages Supported:
Join the discord for support! https://discord.gg/8xYEbft All detailed update info is also posted there first.
More up-to-date and detailed info about the plugin is written in the wiki.
Any donations are really helping. Donate here if you like this plugin: give me a nice cup of coffee
The plugin allows you to create and disable any recipe in-game through gui's. It's very easy and intuitive. Here's a quick (pretty outdated but functional) video where everything is explained:
And another showcase by SoulStriker:
Craft with your custom items.This means you can add recipes with enchantments, custom names, a durability, potions or anything you can think of that exists in the game.
Editing recipes, creating recipes, viewing recipes and ordering the recipes in the viewer GUI are all possible through inventory GUIs.
Full GUI support.
Opening the editor for a recipe is not done through a command, but done through a simple middlemouseclick on a recipe in the recipe viewer. This does require a permission.
Middle click to edit.
In order to completely let server owners be owners of their server, permissions for the custom recipes exist. People that don't have the permission for a custom recipe, can't craft or see it. The 'seeing' part can be configured.
Set permissions for a recipe.
There's a gui which you can use to disable all the vanilla recipes you want. No more over-powered, cheap diamond/netherite armor! (that's how I use it)
Hide recipes but still make them craftable.
You can simply hide recipes for the players that don't have the 'bypass' permission for it. They'll still be able to craft the recipes if they have permissions for the recipe.
Disable vanilla recipes
To make cool recipes an item editor is needed. This item editor allows users to set colored lore, set colored names, set the durability, add enchantments, add itemflags or even set the localizedname of items. And for the record: itemflags are the things that allow you to hide enchantments or attributes on items!
Edit items in-game.
Tab completion support!
I personally think this is an obligated feature to have since the 1.13 update of Minecraft. No more remembering all commands, just the first few letters of a few basic ones.
These are the commands related to custom recipe creation and viewing.
Use tabcompletion on this!
Open the recipe viewer GUI.
Open the recipe viewer GUI.
/ceh createrecipe [key] [perms]
Create a recipe with the specified key and permission. If no arguments are given it'll generate a key for you and let the recipe require not permission.
/ceh specs [key]
Show the specs of the recipe with the specified key. The specs only include the permission currently.
/ceh setpermission [key] [perms]
Change the permission of the recipe with the specified key to new_permission.
/ceh changekey [key] [newKey]
This command allows users to change the key of the recipe with the specified key.
When creating recipes, your custom items get saved to an "items.yml" file. When recipes get altered, the items don't get removed. Use this command to remove unused items.
Reloads the whole plugin!
These are the commands related to item editing.
This is the basic command for editing items. Please use tab completion on this.
/edititem name [name]
Edit the name of the item in your main hand.
/edititem durability [1-100]
Set the durability of the item in your main hand to [1-100]% of it's max durability.
/edititem enchant [enchantment] [level] [... etc.]
Set your specified enchantments to your held item. It removes all enchants and then adds the specified ones. Please let me know if this is weird and needs modification.
/edititem itemflag [itemflag] [itemflag] [... etc.]
Toggle the specified itemflags on your held item.
/edititem lore [line_number] [lore]
Set the specified line of the lore of your held item to be the specified tekst. The tekst section can be left empty if an empty line needs to be added.
The permissions are configurable!
However, these are the default permissions. You can also look these up in the config.yml file.
/ceh createrecipe, /ceh cleanitemfile, /ceh reload, /ceh setpermission, /ceh specs, /ceh changekey. This is also the permission required to middleclick recipes to open the editor.
/ceh viewer, /recipes
All commands that start with /edititem.
Alongside the config.yml, 3 other files will be created: guitemplates.yml, recipes.yml and items.yml.
You can fully customize all the gui's that you see using this file. I think they're faily self-explanatory given the preset files, so I'll only go over the basics. "fill-space" is a range of slot indexes where items can get filled, like the recipes in the recipes viewer. "template" specifies the items that are put into the inventory. Make sure that those don't overlap with fill-space. In template the buttons are also made.
"buttons" specifies where the buttons are located, where the value is the type of the button. Please refer to the preset file to see your options.
You can manually make or edit all your recipes in here. The recipes use item keys of items in the items.yml file. However, because all recipes can be created through gui's, I'll not go over this more in-depth.
Items are stored here with a unique key. This is also managed by the plugin, so there's no real need to touch this.
Some of the messages and permissions are stored in here. One of the important settings is whether you want people to see a recipe that they don't have permissions to.
[1.9-1.16] Custom Recipes and Crafting (CraftEnhance) 18.104.22.168
Make custom recipes through GUI's only - the only plugin that supports itemmeta, like enchantments.