Custom Armors
How to create custom armors without replacing existing stuff?
Just like other items, armor have a texture for when it is held or in your inventory, but also a texture for when a player equips it. Oraxen comes with two ways to add custom armor: Trims & Shaders. Trims is designed around the Armor-Trim system added in Minecraft 1.20, and will not work on earlier versions. Shaders utilizes core-shaders, which were added in 1.17.
Armor-Trim method is recommended if your server is 1.20+ and only allows 1.20+ players. It has the benefit of not breaking with shaders / requiring extra mods to work. It also is not locked to only LEATHER armor-materials, by default using CHAINMAIL.
Core-Shader method is recommended if your server is below 1.20 or allow players on older versions. Compared to armor-trims this method breaks with shaders in Optifine & Iris mods. To fix this Oraxen generates CIT-textures into the pack. This works out-of-the-box with Optifine, but players using Iris will also need CIT Resewn.
Custom Armor - Armor Trims
If using trims as your custom-armor type, most things is handled automatically for you. Unlike with Core Shader method, trims aren't limited to just using LEATHER-materials.
By default, Oraxen is set to use CHAINMAIL, but this can be changed in settings.yml.
Oraxen 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?
Make sure that the itemID of your OraxenItem follows the pattern armorname_armortype.
For the rest of the above set it would be ruby_chestplate, ruby_leggings and ruby_boots.
Make sure your armor-layer files follow the format of armorname_armor_layer_1/2.png. In the example below, we would need a ruby_armor_layer_1.png & ruby_armor_layer_2.png
Simply set the material and specify the texture-icon twice
A trim-pattern is also necessary for the armor to display correctly.
Oraxen 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 oraxen:armorname, so in our example;
Custom Armor - Core Shaders
Oraxen alters this second texture by using colored leather armor and shaders. Armor has like every item a texture in the inventory and in the hand, but it also has a second texture when worn on the body This second appearance has some limitations and requires some practice. We will use a trick with leather armor and colors.
If you are using shaders via either the Optifine or Iris mod, you will need some additional steps. For Optifine, everything is handled automatically. For Iris, you also need CIT Resewn, everything else is handled for you.
You must be careful when naming your armors to get the textures detected correctly.
If you want to create an amethyst armor set, then your item sections must be: - amethyst_helmet - amethyst_chestplate - amethyst_leggings - amethyst_boots And in step 2 you'll be able to create the textures: - amethyst_armor_layer_1.png - amethyst_armor_layer_2.png
How to configure your armor?
For this we will be using the below config example for reference:
Make sure that the items ID, or the first line in the above example, follows the pattern armorname_armortype.
For the rest of the above set it would be ruby_chestplate, ruby_leggings and ruby_boots.
This is also why LEATHER is the only material that works. Custom Armor can not be made with Diamond as the base material. To get custom armor amounts, simply add Attribute Modifiers.\
How to change the equipped appearance?
Now the fun begins. We're going to use a vanilla shader to associate an armor style with a specific color. Thanks to Ancientkingg for developing the shader used by Oraxen.
1) Create your textures
You'll have to create two textures for your armor. You can download the ruby example here: https://oraxen.com/resources/armor_rest.png https://oraxen.com/resources/armor_leggings.png
Make sure your armors resolution fits the value set in settings.yml. By default armor_resolution is set to 16. This means that your textures must be 64x32 pixels. If you want to use a higher resolution, you'll have to change the value in settings.yml. For example armor_layer files with 128x64 pixels must have a resolution of 32 in settings.yml. You cannot have some at 64x32 and some at 128x64, it is either or.
Also make sure that the bit-depth of your textures is 32 bits. Anything else means not fully transparent, and the pixels the shader uses will be black. This will not break Optifine/Iris versions but will break all vanilla versions.
You can make your texture emissive (no optifine required) by adding another file with the same name ending in _e.png. For example ruby_armor_layer_1_e.png
This texture will be treated as an emissivity map, where the alpha of the pixel will be treated as the amount of emissivity.
2) Name your textures correctly
To get your textures registered correctly, their name need to contain armor_layer_X.
For example: ruby_armor_layer_1.png andruby_armor_layer_2.png You can put them in any folder of the pack textures, ~/textures/default/armors is suggested.
Last updated
