4
Block Bench Model has no texture help?
SleepyBunnei
I voulenteer in a server making a custom texture pack. I made Melon, Glistering Melon, and Potato models. They were all put into the pack the same way, Melon and Potato are missing their textures, but Glistering Melon is working perfectly. The models are in assets\minecraft\models\item and the textures are in assets\minecraft\textures\block . This way was suggested by the Texture pack lead (The one who approves what textures does and doesn't get put in) she has suggested what to do, but it didn't work. I've been trying to figure how to fix it, but cannot so does anyone have any ideas?
2
Open your model files and see where the textures lead.
Example: Here's my melon model from my resourcepack Bewitched:
In my yellow highlighted area you can see where the texture's are assigned on the model.
In the orange highlighted area is where my "mellon_bottom" texture is, what it's called in the model file ("2") what folder location the texture should be in (block/melon_bottom) and how it's applied on the model ("down")
Blockbench should do this all for you. Reopen your model, reapply the textures (pull these from your resource pack so blockbench can set the right file path) and re-export the model back into that texture pack. You can also fix it manually but that might be a pain if you have lots of model parts.
**another glance at your post and you said your models in the ITEM folder and your textures in the BLOCK folder, make sure that's the correct location //
Generally you should be keeping your BLOCK MODELS in assets < minecraft < models < blocks, and the BLOCK TEXTURES in assets < minecraft < textures < block
Items should be MODELS: assets < minecraft < models < item TEXTURES: assets < minecraft < textures < item
That will keep your files tidy and easy to find
Example: Here's my melon model from my resourcepack Bewitched:
| { "credit": "Made with Blockbench", "parent": "block/cube_column", "textures": { "2": "block/melon_bottom", "end": "block/melon_top", "particle": "block/melon_side", "side": "block/melon_side" }, "elements": [ { "from": [0, 0, 0], "to": [16, 16, 16], "faces": { "north": {"uv": [0, 0, 16, 16], "texture": "#side"}, "east": {"uv": [0, 0, 16, 16], "texture": "#side"}, "south": {"uv": [0, 0, 16, 16], "texture": "#side"}, "west": {"uv": [0, 0, 16, 16], "texture": "#side"}, "up": {"uv": [0, 0, 16, 16], "texture": "#end"}, "down": {"uv": [0, 0, 16, 16], "texture": "#2"} } } ] } |
In my yellow highlighted area you can see where the texture's are assigned on the model.
In the orange highlighted area is where my "mellon_bottom" texture is, what it's called in the model file ("2") what folder location the texture should be in (block/melon_bottom) and how it's applied on the model ("down")
Blockbench should do this all for you. Reopen your model, reapply the textures (pull these from your resource pack so blockbench can set the right file path) and re-export the model back into that texture pack. You can also fix it manually but that might be a pain if you have lots of model parts.
**another glance at your post and you said your models in the ITEM folder and your textures in the BLOCK folder, make sure that's the correct location //
Generally you should be keeping your BLOCK MODELS in assets < minecraft < models < blocks, and the BLOCK TEXTURES in assets < minecraft < textures < block
Items should be MODELS: assets < minecraft < models < item TEXTURES: assets < minecraft < textures < item
That will keep your files tidy and easy to find
Try running the game with output log enabled (In official launcher: Settings>> Open output log when Minecraft:Java Edition starts)
Look for yellow warning and red error entires, after loading the resourcepack.
This way you will see, what Minecraft is searching for, when loading up the custom model - might be wrong texture naming/location, compared to the values specified in the model json.
Look for yellow warning and red error entires, after loading the resourcepack.
This way you will see, what Minecraft is searching for, when loading up the custom model - might be wrong texture naming/location, compared to the values specified in the model json.
