I tested this new feature on a resource pack i created and after trying different names and combinations, i couldn't get mineraft to generate an atlas from a directory i created inside "textures".
I believe that minecraft is simply ignoring the "atlases" directory i created and the json files inside.
Attachments
Comments 8
Can reproduce, but only by placing atlas json under custom namespace.
When placed in minecraft namespace, all block and item textures would be erred, but when placed in custom namespace nothing happens.
That's because minecraft:blocks is not the same as custom:blocks, models get textures from minecraft:blocks. You need to modify the existing atlases, not create new ones.
Wait, so i can't create a new atlas? That doesn't make much sense to me. by looking at the assets on 1.19.3 i can see they have lots of atlases, each for a different directory under textures. What if I want to add a new directory?
This is my last atempt. i tried to put the atlases directory under the new namespace too but that didn't worked so i placed it under the minecraft directory.
minecraft:test is not an atlas models can refer to, models refer to minecraft:blocks. The name is not related to the texture folder name, it is is the name of the resulting stitched texture file(s). Creating any non-vanilla atlases has no use, as you cannot refer to them,nor change the atlas a texture reference looks at.
So regarding the ammount of custom directories i can create to put my textures in. Am i limited to the ammount of atlases that minecraft vanilla has? 10 for what i can see.
Cannot reproduce, my blocks.json atlas works fine.
Please attach your minimal setup to reproduce this issue.