Fixed
- Config being naughty
You thought 1.2 runtime textures were my final form?
Added
Config
useBannerTextures- Use banner textures on the elytra instead of shield. No more need to install Vanilla Tweaks. (default: false)
cropTrims- Crop the trims to fit elytra. (default: true)
useDarkerTrim- Use a darker variation of the trim when possible. (default: false)
showBannerIcon- Show the banner icon on the elytra icon. (default: true)
Patterns
- Now generates models for all banners, including modded ones.
Fixed
- Trims not showing up on servers without the mod.
Uuuh
- Maybe some other stuff, idr all the changes.
Changed
- Internal patches (DO NOT look up) for 23w31a support
WHY does Mojang have to change rendering code every single update?! Can I please live in peace? You know, touch grass, read books, socialize. Not inspecting code on 2 screens to figure out preprocessor patches I need to add.
Fixed
- Elytra Slot & Elytra Trinket compat
Added
- Color and pattern preview:
- Support for modded banners (such as AdditionalBanners and Archeology Banners)
Changed
- Elytra textures are now written in their own atlas texture (mostly). This will break any addons (including ET extensions 1.1.x)
Fixed
- Log spam for leggings textures in the runtime trim generation
Removed
- Lock resourcepack config - it's now built-in
- Runtime trim generation - now always enabled
Known issues
I can't believe this shit
- Color/pattern preview may be rendered too high on the first creation. Restart MC to fix it.
Added
- Stackable Trims compat
Added
- Elytra Trinket support (literally the same as Elytra Slot).
Fixed
- Soft conflict with Entity Texture Features mod. (This doesn't provide full support).
- Mod config utterly shitting itself whenever a new option is added.
Added
- Runtime trim generation
This is an experimental feature. Please report any issues with it on the GitHub page!
Like, really. I don't know how it will behave in many possible combinations of other mods and datapacks
Explanation:
This feature listens for every registered armor trim and attempts to register it again, but for elytra's path. As the result, you don't need to specify armor_trims.json atlas source.
A specialised resourcepack is still needed to provide textures for trim patterns, but it works well for datapacks or mods adding new materials.
Fixed
- Server-side recipes again
Fixed
- Elytra Slot compatibility