ВЕРСИИ (26)

# 1.1.2 - Minecraft 26.3 support - Trims now use the game's paletted textures: each greyscale trim texture needs a `.png.mcmeta` with `{"palette": {"base_palette": "minecraft:trim_base"}}`, and `atlases/armor_trims.json` can be deleted - `TrimLayer.spriteId` renamed to `textureId` (no trim material suffix) - `ArmorRenderContext#submit` takes a `UvMapping`; added `glintPending()` / `submitPendingGlint()` - Glow and radiant layers work with Improved Transparency - Geo armor follows Entity Model Features player animations again (Fresh Animations Player, Entity Player Compat) - Geo armor no longer shows in first person during Better Combat animations

# 1.1.2 - Minecraft 26.3 support - Trims now use the game's paletted textures: each greyscale trim texture needs a `.png.mcmeta` with `{"palette": {"base_palette": "minecraft:trim_base"}}`, and `atlases/armor_trims.json` can be deleted - `TrimLayer.spriteId` renamed to `textureId` (no trim material suffix) - `ArmorRenderContext#submit` takes a `UvMapping`; added `glintPending()` / `submitPendingGlint()` - Glow and radiant layers work with Improved Transparency - Geo armor follows Entity Model Features player animations again (Fresh Animations Player, Entity Player Compat) - Geo armor no longer shows in first person during Better Combat animations

# 1.1.2 - Geo armor follows Entity Model Features player animations again (Fresh Animations Player, Entity Player Compat) - Geo armor no longer shows in first person during Better Combat animations

# 1.1.2 - Geo armor follows Entity Model Features player animations again (Fresh Animations Player, Entity Player Compat) - Geo armor no longer shows in first person during Better Combat animations

# 1.1.2 - Geo armor follows Entity Model Features player animations again (Fresh Animations Player, Entity Player Compat) - Geo armor no longer shows in first person during Better Combat animations

# 1.1.2 - Geo armor follows Entity Model Features player animations again (Fresh Animations Player, Entity Player Compat) - Geo armor no longer shows in first person during Better Combat animations

# 1.1.1 - Geo armor is now posed from the entity's own body model: armor on armor stands no longer sways with the idle animation, and baby mobs get properly fitted armor (no trims on babies, like vanilla)

# 1.1.1 - Geo armor is now posed from the entity's own body model: armor on armor stands no longer sways with the idle animation, and baby mobs get properly fitted armor (no trims on babies, like vanilla)

# 1.1.1 - Geo armor is now posed from the entity's own body model: armor on armor stands no longer sways with the idle animation, and baby mobs get properly fitted armor (no trims on babies, like vanilla)

# 1.1.1 - Geo armor is now posed from the entity's own body model: armor on armor stands no longer sways with the idle animation, and baby mobs get properly fitted armor (no trims on babies, like vanilla)

# 1.0.0 Port of 1.0.0 to Minecraft 1.20.1 (Fabric + Forge 47). Same feature set; no functional changes. - Forge replaces NeoForge: the armor hook is a mixin on `ArmorFeatureRenderer#renderArmor` - Dye color read through `DyeableItem`, trims through the stack's `Trim` NBT - Shader awareness gates on Iris (Fabric) or Oculus (Forge) Initial release. - Renders Bedrock/GeckoLib geo armor models through the vanilla armor pipeline - Armor bone convention with boot bones and a chest-anchored waist bone - Armor trims with per-set trim textures, with greyscale fallback for third-party trim materials - Emissive glowmasks (AzureLib `_glowmask` convention) and a radiant glow mode that feeds shader-pack bloom

# 1.0.0 Port of 1.0.0 to Minecraft 1.20.1 (Fabric + Forge 47). Same feature set; no functional changes. - Forge replaces NeoForge: the armor hook is a mixin on `ArmorFeatureRenderer#renderArmor` - Dye color read through `DyeableItem`, trims through the stack's `Trim` NBT - Shader awareness gates on Iris (Fabric) or Oculus (Forge) Initial release. - Renders Bedrock/GeckoLib geo armor models through the vanilla armor pipeline - Armor bone convention with boot bones and a chest-anchored waist bone - Armor trims with per-set trim textures, with greyscale fallback for third-party trim materials - Emissive glowmasks (AzureLib `_glowmask` convention) and a radiant glow mode that feeds shader-pack bloom

# 1.1.0 - Minecraft 26.2 support - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Minecraft 26.2 support - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.1.0 - Per-item model and texture overrides through the vanilla `minecraft:custom_data` component (`{armor_model_api:{model, texture, glowmask, trim}}`), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both `model` and `texture` takes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack - `ArmorRenderContext` carries the base texture in effect (`texture()`) and the stack's `overrides()`; layers deriving assets from the base texture should read it from there

# 1.0.2 - 1.21.11 support - Player armor uses a `PlayerEntityModel`-based geo model, so player animation libraries (PAL) pose it - Fix `GeoArmorModel` construction (missing biped parts)

# 1.0.2 - 1.21.11 support - Player armor uses a `PlayerEntityModel`-based geo model, so player animation libraries (PAL) pose it - Fix `GeoArmorModel` construction (missing biped parts)

# 1.0.0 Initial release. - Renders Bedrock/GeckoLib geo armor models through the vanilla armor pipeline - Armor bone convention with boot bones and a chest-anchored waist bone - Armor trims with per-set trim textures, with greyscale fallback for third-party trim materials - Emissive glowmasks (AzureLib `_glowmask` convention) and a radiant glow mode that feeds shader-pack bloom

# 1.0.0 Initial release. - Renders Bedrock/GeckoLib geo armor models through the vanilla armor pipeline - Armor bone convention with boot bones and a chest-anchored waist bone - Armor trims with per-set trim textures, with greyscale fallback for third-party trim materials - Emissive glowmasks (AzureLib `_glowmask` convention) and a radiant glow mode that feeds shader-pack bloom