In prior versions, block/item models could access a texture directory outside of the default directories in the texture folder (block, item) if it existed.
in a working resource pack in 1.19.2, all my custom textures were stored under textures/custom/_, I assume because "custom" is not a native member of the textures folder, the game no longer recognizes it.
on a side note as well, I have a model that overrides the minecart item texture and uses the texture under textures/entity/minecart. this also no longer works either but does in 1.19.2
Linked issues
duplicates 1
Comments 5
that directory that you listed is not where my textures are stored, can you give an example of what you mean by "own namespace"?
assets/custom/textures/item/example
the texture reference would then be "custom:item/example"; "custom" is a namespace.
why isnt this change to the texture packs made public on the change logs? I realize that the reason for the change is some performance issue but they should still mention it.
Duplicate of MC-256668
Please do not put any custom assets in
assets/minecraft/textures/custom
, put them in your own namespace. This has always been the recommendation, and following it could have saved you this trouble