General properties
model_id
indicates the file name of model and texture for this item in the resourcepack.
vanilla_type
indicates the original Minecraft item material we want our item to be based off. In this example I want this sword to be like a diamond sword, since it's an emerald sword and I want it to have an high durability like diamond swords have. As you can see I'll have to create the model and texture files in there paths:
Important
Not every custom item can have vanilla_type changed:
blocks.yml
bows.yml
drinks.yml
eatables.yml
armors.yml
fishing_rods.yml
furnitures.yml
hats.yml
items.yml
minerals.yml
seeds.yml
shields.yml
totems_of_undying.yml
vegetables_and_fruits.yml
Only in these configs you can specify the vanilla_type:
swords.yml (must be swords or tools)
tools.yml (must be tools or swords)
guns.yml (must be swords or tools)
enabled
Specify if the item is enabled or not
permission
Specify which permission a user needs to have in order to craft the current item, example:
User must have this permission ia.craft.mysword to craft the item
name
lore
enchants
You can set a default enchant for the item so when players craft this item it'll have the specified enchants. You can add more than one enchant (like lore lines).
You can get enchant names here
events
specific_properties
Each .yml file which contains a particular item type has its own special_properties structure. To see the available properties take a look at the various pages under "specific items" and search for "specific_properties". One specific_properties attribute is available to all .yml files, it's the luck attribute. Luck attribute is used to specify luck amount.
craft_recipe
Recipe to craft the current custom item
result_recipe
Recipe to craft any item with any ingredient, it's useful if you want to add multiple crafting recipes for the current custom item
Last updated