The tabs.png which can be found in assets\minecraft\textures\gui\container\creative_inventory ensures by the texture change that older resourcepack can not be compatible with newer ones. Especially if a resourcepack supports multiple versions the whole 1.19 or even the 1.18. It would be a possibility to simply rename the tabs.png, as Mojang has already done with the villiger2.png. Or also in the 1.13 blocks to block was changed. I am here an extreme example, which makes a resourcepack, which should support all versions in a file from the 1.7. And even the missing support of pack version 3 and 4 can be worked around. But as it looks not the tabs.png, because atlases, models and blockstates does not address gui elements.
It would be nice if the tabs.png would be renamed e.g. to tab.png.
[media]Attachments
Comments 4
That's right. Any kind of community content is not the responsibility of Mojang. Still, it would be nice if mojang enabled community content creators a lot. This is what they are doing after all. Even on this topic, it's been done a lot. For example in 1.13 with renaming the folder blocks/items to block/item. And the same in the 1.14 with the villiger2.png in the container. Here the same would be now only again in the 1.19.4 with the tabs.png which one could rename for example in tab.png. Mojang has made it possible for me through these changes in the 1.13 and 1.14 and other updates to create a resource pack that supports all versions from Packformat 1 in one file. And maybe mojang can allow me to do that in the future. It would be just a simple renaming of a single .png.
1.19.4 literally removed one of these backward compatibility things for resource packs, they're no longer enabling incompatible packs to function as if nothing changed.
This is not a bug, but a change request.
The pack format field exists for the purpose of stating the pack is incompatible. Any pack that claims to be compatible, but isn't, is not mojang's responsibility to fix. Only the build-in packs.
It is not mojang's responsibility to keep community content (read resource/data packs, mods, plugins, custom maps) compatible.