I created a 1.20.1 resource package using the custom model data feature.
All paths of the model are normal and can run normally in the blockbench.
You can open the JSON file of the model and see that the texture and model are completely fine.
However, in the 1.20.1 environment (all modules have been removed, including openfine). There is no problem with the model,
But the texture completely turned into purple black squares (damaged by collision).
Interestingly, at 1.16.5, everything in this material bag was normal.
I don't know what problem caused it.
Interestingly, there is no problem with the blocks, it's just that the items has this issue.
What's even more interesting is that the 2D model is great, but the texture of the 3D model crashes in 1.20. x.
This is the material package: test.rar
Please enter the following code to obtain the Iron Sword with a custom model file:
/Give @ s minecraft: iron_sword {CustomiModelData: 8}
Attachments
Comments 4
All textures are normal. Please use blockbench to open the JSON file for model checking.
Surprisingly, it can run perfectly on 1.16.5.
My team and I suspect that something has changed at 1.20. x.
But we can't find a way at all.
Hi, this is caused by a change to atlasing. You need to either add your texture entries to a blocks.json atlas file, or put your textures in the item or block folder.
As an aside, I'd recommend not putting custom content in the minecraft namespace, use your own namespace!
Thank you for your answer. This material pack was originally loaded using Openloader, but no fatal issues were found on the 1.20.1 server.
We placed these models in different folders and texture paths to distinguish the types of each model, such as melee weapons, extra weapons, and magic weapons.
If the textures must be placed in the item folder now... what about the model? Can I still use the categorized folder?
purple black blocks are the missing texture block