Component Based (1.21.2+)
If using COMPONENT as your custom-armor type, you are not limited in any way, unlike with TRIMS It also has the benefit of not needing to be based on an armor-item at all, use PAPER if you want to. Every downside there has been to earlier methods is now gone, no restrictions.
How to configure your armor?
forest_helmet:
material: PAPER # Can be any material, armor-item or anything else
Pack:
# Optional, if not specified, Nexo searches for any texture
# with the filename armorname_armor_layer_X.png
#CustomArmor:
# layer1: nexo:item/nexo_armors/forest_armor_layer_1
# layer2: nexo:item/nexo_armors/forest_armor_layer_2
texture: nexo:item/nexo_armors/forest_helmet
An Equippable-Component is also necessary for the armor to display correctly.
Nexo will automatically assign it if it has not been manually specified.
You can optionally manually assign the component if you want to.
The value should be nexo:armorname
, so in our example;
forest_helmet:
Components:
equippable:
slot: HEAD
model: nexo:forest
If using a 3D model for your helmet, do not specify Components.equippable.model

Last updated