Custom Recipes and Crafting (CraftEnhance)

To download the plugin, pick a compatible version below or go to the files page.

 


Bukkit/Spigot 1.13.X, 1.14.X: CraftEnhance-2.3.4

Bukkit/Spigot 1.12.X: CraftEnhance-2.3.4

Bukkit/Spigot 1.9.X, 1.10.X, 1.11.X: CraftEnhance-2.3.4


 

CraftEnhance is the first plugin that allows crafting with all custom items. It's very unique. Try and see how awesome it is! It's compatible with basically every bukkit or spigot version.

 

Banner image

Creating recipes is easy and done through GUI's. Here's a quick video where everything is explained.

 

featuresBanner

Craft with all 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.

 

Full GUI support. 

Editing recipes, creating recipes, viewing recipes and ordering the recipes in the viewer GUI are all possible through inventory GUIs.

 

Middle click to edit. 

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. 

 

Set permissions for a recipe.

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.

 

Edit items in-game. 

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!

 

Full tab completion support! 

I personally think this is an obligated feature to have in the 1.13 update of Minecraft. No more remembering all commands, just the first few letters of a few basic ones.

banner of commands

These are the commands related to custom recipe creation and viewing.

===============Command===============  
/ceh This is the base command that you can use tabcompletion on.
/ceh viewer or /recipes Open the recipe viewer GUI.
/ceh createrecipe [key] [perms] Create a recipe with the specified key and permission. It'll open a GUI to edit it. The recipe only gets saved to the server when the save button is pressed in the GUI.
/ceh orderrecipes Open a GUI to change the order of the recipes in the recipe viewer.
/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.
/ceh cleanitemfile 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.

 


A quick sidenote!

I know, it's a long list. However, there are some more commands that need to be documented regarding editing items. Like stated before, please use the tabcompletion instead of learning this documentation. However, a quick scan won't hurt ;).

Also, this video covers the next part of the documentation:


These are the commands related to item editing.

/edititem

This is the basic command for editing items. Please use tab completion on this.

/edititem name [name (supports &3&lcolorcodes&r)]

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] [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. This are the available itemflags:

HIDE_ATTRIBUTES
Setting to show/hide Attributes like Damage
HIDE_DESTROYS
Setting to show/hide what the ItemStack can break/destroy
HIDE_ENCHANTS
Setting to show/hide enchants
HIDE_PLACED_ON
Setting to show/hide where this ItemStack can be build/placed on
HIDE_POTION_EFFECTS
Setting to show/hide potion effects on this ItemStack
HIDE_UNBREAKABLE
Setting to show/hide the unbreakable State

 

 

/edititem lore [line_number] [&4&l&3&r&3lore (this supports colorcodes :O)]

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.

/edititem localizedname [name]

Set the localizedname of your held item. This is stored server-sided. I'm not sure if any plugins use it, but it's a property of ItemMeta in the Bukkit API, so why not also include this!

Banner of config header

The permissions are configurable!

However, these are the default permissions. You can also look these up in the config.yml file.

craftenhance.edit: /ceh createrecipe,  /ceh cleanitemfile,  /ceh orderrecipes, /ceh setpermission, /ceh specs, /ceh changekey. This is also the permission required to middleclick recipes to open the editor. 

craftenhance.view: /ceh viewer, /recipes. 

craftenhance.edititems: All commands that start with /edititem. 

Banner of config header

Alongside the config.yml, 2 other files will be created: recipes.yml and items.yml. I'd suggest you don't touch those as there are GUI's that allow you to edit everything in-game. But, if you really do want to use those files, be my guest! You can easaly copy+paste recipes and change them using itemkeys.

The config file looks like this:

<span style="font-family: verdana, geneva, sans-serif;">########################################################################
#                                                                      #
# This is the config file of CraftEnhance. Created by DutchJelly.      #
#                                                                      #
########################################################################

enable-debug: false
enable-recipes: true

#If this option is enabled, people can only see recipes that they have permissions to.
only-show-available: false

debug-prefix: "[DEBUG] "
global-prefix: "&amp;7[&amp;bCraft&amp;dEnhance&amp;7] &amp;r"

perms:
  recipe-editor: "craftenhance.edit"
  recipe-viewer: "craftenhance.view"
  item-editor: "craftenhance.edititems"

messages:
  global:
    no-perms: "You don't have permission to do that."
  commands:
    show-options: "You entered an unfinished command. It can be completed by adding one of the following arguments: &amp;e[PLACEHOLDER]&amp;r."
    few-arguments: "Expected [PLACEHOLDER] arguments for the command." 
    only-for-players: "This command is only for players."</span>

 I think the config path names are self-explanatory. However, if you do have questions, please let me know.

 

 

FAQ

I can't enchant my item, what am I doing wrong?

When using the plugin version that supports versions below 1.13, you'll have to use enum enchantment names. Therefor I'd suggest to use the version that supports 1.13 and up because that version uses a newer version of the bukkit api. That way you can use easy-to-remember enchantment names like 'sharpness' or 'protection'.

 

My recipe isn't shown in the /recipes GUI, could you help me?

The recipes won't be shown if there's no 'result item' when saved. With the result item I mean the item that you can actually craft with the recipe. If you forget to add one, you will unfortunately have to solve this issue in the yaml files manually currently. Or you could just make a new recipe.

Another thing that could cause the issue of recipes not showing in the /recipes overview, is forgetting to save the recipe in the editor. In the recipe editor (that pops up when performing the "/ceh createrecipe [key] [permission]" command) there's an option to save the recipe you created to the righthand side. This has to be clicked for it to actually save to the server!

 

The plugin is not working and throwing exceptions, why is this happening?

What you should do is check if you're using the correct version of the plugin that supports your bukkit/spigot version. If you're really using the correct one, please copy paste your error into a pastebin or hastebin and send that link in the comment section. Also include what server and plugin version you're using.

 

 


Comments

  • To post a comment, please or register a new account.
Posts Quoted:
Reply
Clear All Quotes

About This Project

  • Project ID
    289509
  • Created
    Mar 4, 2018
  • Last Released File
    Aug 18, 2019
  • Total Downloads
    4,409
  • License

Categories

Members

Recent Files