-
Bug
-
Resolution: Works As Intended
-
None
-
22w42a
-
None
-
RTX 3060 TI
I5 10400F
Windows 11 Dev 25211.1001
16Gb 3600mhz DDR4 Ram
Game Running From Sata III SSD
-
Community Consensus
-
(Unassigned)
In 1.19.3 and later, models can only access textures in the block and item texture folders by default. This is part of an optimization that makes resource loading faster!
If this broke your pack, you can fix it with one of these steps:
- For custom textures, simply move them to the block or item texture folders in your namespace, and update the references to them.
- To reference vanilla textures in other folders, create an atlas JSON file, following the steps in the 22w46a changelog.
Texture pack custom models cant read textures outside of textures/block
How to replicate :
1. Create a custom model
2. Use a texture in "textures/(Custom named folder)", you will get a missing texture model which did not happen in previous versions (Ie 1.19.2
more info :
If you use "textures/block" or "textures/block/(Custom named folder)" the issue won't happen
- is duplicated by
-
MC-256749 Fully transparent textures are missing from the texture atlas leading to errors in custom block models
- Resolved
-
MC-256959 Custom Texture Directory No Longer Works
- Resolved
-
MC-257407 Resource pack can't use textures under the custom paths
- Resolved
-
MC-260183 item models can no longer access textures in the entity folder
- Resolved