Exporting your currently held item, will generate a file.
Inside this file, is a big string of text; we use this text inside the recipe.
This string contains all information about the item, and will be converted into an item by the recipe system.

Using CustomModelData and a server resourcepack to apply textures, we can create new types of items, such as copper.
Default copper cannot be used for anything but decorations, and lightning rods.
So doing this, allows us to create Armor and Tools from Copper.
(Or other materials like Crying Obsidian)


I've created an example of how to make this.
Download: https://github.com/Valorless/HavenRecipes/tree/main/CustomItemExamples/HavenRecipes%20-%20Copper%20Items

Since we cannot change durability on items by any means, I'm using Unbreaking 2 to give the Gold base additional durability, while still remaining below Iron.

Disclaimer: Due to Minecraft limitations, we cannot change Armor textures without using mods such as Optifine or other CIT mods.

I created ValorlessUtils with the purpose of making my plugin development shorter and easier.
In the case of HavenRecipes, HR sets up the recipes from the recipe files, and feeds it to ValorlessUtils, which does the rest of the work.
In addition, VU also does most of the job with utilities and config files. (Which also include the recipe files)

Why not just have it all in HavenRecipes?
Simple: size, updates, and time.
The size of all my plugins would skyrocket, especially if you use multiple of my plugins.
I'd have to update all my plugins, when I make changes or fixes to a function.
And the time it would take to add and implement these functions, is greater than just implementing them.

While I do have some functions such as my Lang class. (The one fetching and parsing values from lang.yml)
Most of my commonly, and sometimes niche used functions, become a part of ValorlessUtils, to be used now or later, by myself and potentially others.