Blueprint config
Guide how to crate custom recipes.
Inside the blueprints/aurora
folder, you can create unlimited files that can contain a list of recipes.
If you create multiple recipes that have the same shape with the same ingredients and only ingredient amounts are different, only the recipe registered at the end will work. Changing just the amount of ingredients can't create a unique recipe.
This is how one file should look like:
Let's go through each option one by one:
id: This is used to look up recipes using the /recipe <id> command.
permission: Required permission to unlock the recipe. Optional.
workbench: Specify what workbench this recipe should be assigned to. If you omit this field, it will be assigned to the
default
workbench if exists.display-options -> locked-lore: Here, you can define the menu item lore in the recipe book while the recipe is locked. Optional.
shapeless: if it is true, then the recipe will act as a shapeless recipe. Optional. By default, everything is a shaped recipe.
result: This defines what should be the result of the recipe. Required. It can't be air.
Ingredients: This is the list of ingredients for the recipe. If the recipe is shaped, you need to define a list that has the same amount of items as your crafting matrix slots (otherwise it fill be filled with air). If you want an empty slot, just use an empty string like
- ""
.
Format of the items
In the ingredients and result configs, you might have already noticed the strange format of the items. Every item has a namespace. This can be either minecraft for vanilla materials or usually the name of the plugin which provides the item you are trying to use.
So the format is namespace:item_id
.
You always need to set the amount of the items. This is done by appending /number
at the end of the item ID. If you don't add the number, it will default to 1.
So the final format is namespace:item_id/amount
Supported item plugins with examples
MythicMobs (and Crucible) -
mythicmobs:item_id
MMOItems -
mmoitems:type:id
ExecutableItems -
ei:item_id
ExecutableBlocks -
eb:item_id
Nexo -
nexo:item_id
Oraxen -
oraxen:item_id
ItemsAdder -
ia:ia_namespace:item_id
HeadDatabase -
hdb:id
CustomFishing -
customfishing:id
EcoItems -
eco:ecoitems:item_id
EcoArmor -
eco:ecoarmor:armor_id
Talismans -
eco:talismans:talisman_id
EcoScrolls -
eco:ecoscrolls:scoll_scrollid
Other eco plugins are also supported, the item lookup works the same way as they describe in their wiki. They are just prefixed once more with
eco:
here.
Last updated