To create smithing recipes, you need to put yml files with recipes in them into the blueprints/vanilla/smithing_table folder.
Many item plugins can and will prevent Vanilla smithing recipes using their items. You should disable those checks in your item plugins or ask them for support. Notable examples for this behavior is ItemsAdder which completely fucks up custom vanilla recipes by default. MythicCrucible/MythicMobs also applies PreventSmithing: true for all items that has custom model data on it!
Here is how should on of these yml files look like:
recipes:
- id: enchanted_netherite_helmet
# Result of the recipe
result: "mythicmobs:enchanted_netherite_helmet/1"
# First slot
template: "minecraft:netherite_upgrade_smithing_template/1"
# Second slot
base: "mythicmobs:enchanted_diamond_helmet/1"
# Third slot
addition: "mythicmobs:enchanted_netherite/1"
# Optional
vanilla-options:
# Used in the recipebook to group together recipes with the same result and type.
# Optional
group: my_group
# Can be either item_type for dynamic matching or exact.
# Like 99.9% of the time, you should use item_type here, which is the default.
# Optional
choice-type: item_type
# Specifying this will do the same as the vanilla smithing upgrade recipes.
merge-options:
# From the 2nd ingredient (which is "base" here) copy the following things:
2:
# Copy/Merge the enchants to the result
enchants: true
# Copy the trim from the ingredient
trim: true
# Copy the durability loss from the ingredient
copy-durability: true
# Additionally, you can copy PersistentDataContainer values as well
# by specifying their paths. (use /paper dumpitem to figure it out)
pdc:
- "ecoscrolls:scrolls"
- "reforges:reforge"
