Trims Based (1.20+)
If using trims as your custom-armor type, most things is handled automatically for you. TRIMS method requires using CHAINMAIL as the base-item.
Nexo then generates a datapack based on your configured custom armors. Due to it requiring a datapack, the server needs to do a full restart any time you add/remove an armor-set.
After changing CustomArmor.armor_type
to TRIMS
you need to:
Start your server to let datapack be generated
Stop your server
Start it again to enable the previously generated datapack
How to configure your armor?
ruby_helmet:
displayname: "<gradient:#FA7CBB:#F14658>Ruby Helmet"
material: CHAINMAIL_HELMET
Pack:
parent_model: "item/generated"
# Optional, if not specified, Nexo searches for any texture
# with the filename armorname_armor_layer_X.png
#CustomArmor:
# layer1: default/armors/ruby_armor_layer_1.png
# layer2: default/armors/ruby_armor_layer_2.png
texture: default/armors/ruby_helmet
A trim-pattern 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 trim_pattern
if you want to.
The value should be nexo:armorname
, so in our example;
ruby_helmet:
trim_pattern: nexo:ruby
Last updated