Seems like the fix for MC-263338 and MC-259982 caused most, if not all armor trims applied on chainmail armor to look very different to how they did in 1.20.1. This seems like a remarkable downgrade for a pretty minor fix for some floating pixels in the chainmail helmet, and makes this especially noticeable on the silence and vex armor trims.
[media][media]
[media]
[media]
For players that already have these trims in worlds made in 1.20.1 might find this very concerning, as these changes weren't stated in the 23w32a changelog.
Expected result
Armor trims changes would only account for those cases stated in MC-259982, and the rest would remain unchanged, as there weren't floating pixel issues there (unless you interpret overhanging pixels outside the base texture as floating even if they connect somehow, like in the vex trim texture).
Observed result
Several pixels on the chainmal armor trims have been removed, which seems like a notable downgrade from 1.20.1.
How to reproduce
Create a world in 1.20.1 or 23w31a and make a chainmail armor with the vex and silence armor trims.
Notice how the texture looks.
Exit the world and upgrade it to 23w32a.
Notice how the armor trims look significantly different now.
Linked issues
Attachments
Comments 4
If we follow your logic here, MC-264753 would have to be closed as well, as that report is either asking for a literal revert of the aforementioned fix, or an eye trim design change for the chainmail helmet which would be a feature request.
Also "by design per the fixed listed", the report listed there explicitly stated in the title there were floating pixels in the chainmail helmet on certain trims, so i fail to see how a change as drastic as this would be intentional if it isn't listed in the changelog apart from a listed bug report. I'm curious as to what makes you think this might be a design change and not a side effect of the method used to fix it.
That report is different as it notes how a trim has literally become invisible on that armor piece, rather than changed visuals, as you're reporting.
It's clearly a design change as it is unlike any other texture applying behavior (meaning newly written code) and applied globally to trim logic, not specific armor pieces/trim patterns. I agree it should have been communicated properly in the changelog though.
The fix was making the trim texture only change existing pixels, as the trim is supposed to only be a coloring of the armor, not creating new parts.
This is by design per the fixes listed, and asking to change it is a change request, not a bug. Those go to feedback.minecraft.net.