I thought it would be good to have a thread to discuss this stuff.
Here's one thing that has me baffled. I get errors like this, sometimes tons of them. I don't know what it means and often the texture seems to work as desired in spite of the error.
Client thread/WARN]: Unable to resolve texture due to upward reference: #side in minecraft:block/fence_inventory
If the textures are still working then that means you have a reference that's just sitting out there doing nothing. Not applied to any face, but not getting any texture information either. You might also have a reference that's referencing itself in the parent block model, but a child model is providing it with a texture anyway.
I can't really tell what's wrong without examining the pack, though. I also get errors like these, but I beat them with a stick until they go away.
Is this one also giving an error? It says "fence_inventory" in the error you posted earlier, not "fence_post". "fence_inventory" would be referenced by the item model, not another block model.
Is this one also giving an error? It says "fence_inventory" in the error you posted earlier, not "fence_post". "fence_inventory" would be referenced by the item model, not another block model.
Yeah, all my similarly altered fence models are giving me that error, the post model was the simplest one giving the error, so i posted it.
Yeah, all my similarly altered fence models are giving me that error, the post model was the simplest one giving the error, so i posted it.
Hmmm... That is odd. Nothing immediately jumps out at me as being wrong.
Is this happening in a version presently available for download? If not would you mind sending it to me via PM. Solving these kinds of "puzzles" is sometimes fun for me.
OK, so, now that I've gotten a good look at the pack (Eleazzaar sent it to me via PM for those following the thread) it's obvious where the problem is.
What's happening is that Minecraft assembles everything as a series of parent/child relationships with each file feeding into the next. As such, things are getting taken partly from default, and partly from the pack, and they're not matching up. Here's a walkthrough for the Oak Fence Post:
STEP 1:
blockstate/fence.json
Comes from: DEFAULT
References block file: "oak_fence_post.json"
STEP 2:
models/block/oak_fence_post.json
Comes from: DEFAULT
Child block file to: "blocks/fence_post.json"
Sends texture called "texture" as "blocks/planks_oak.png"
STEP 3:
models/block/fence_post.json
Comes from: Visibility
Looks for textures called "side" and "top"... but can only find one called "texture".
See the problem? The default files, which you haven't replaced, are supplying your model with one texture named "texture" when it wants two textures named "side" and "top.
The same problem applies to all of the fence models. Somewhere along the line your files are asking for something that the default isn't giving, or vice-versa. There's a simple disconnect somewhere in the sequence of events.
Yeah, thanks. I understand the above, but was blinded by confident, but inaccurate memories of what i had already done. I think that closes the issue, but i'll need to do a lot of file-wrangiling to make sure it all works out.
Here's one thing that has me baffled. I get errors like this, sometimes tons of them. I don't know what it means and often the texture seems to work as desired in spite of the error.
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
I can't really tell what's wrong without examining the pack, though. I also get errors like these, but I beat them with a stick until they go away.
Parent Model:
"textures": {
"particle": "#side"
},
"elements": [
{ "from": [ 6, 0, 6 ],
"to": [ 10, 16, 10 ],
"faces": {
"down": { "uv": [ 6, 6, 10, 10 ], "texture": "#top", "cullface": "down" },
"up": { "uv": [ 6, 6, 10, 10 ], "texture": "#top" },
"north": { "uv": [ 6, 0, 10, 16 ], "texture": "#side" },
"south": { "uv": [ 6, 0, 10, 16 ], "texture": "#side" },
"west": { "uv": [ 6, 0, 10, 16 ], "texture": "#side" },
"east": { "uv": [ 6, 0, 10, 16 ], "texture": "#side" }
},
"__comment": "Center post"
}
]
}
Child Model:
"parent": "block/fence_post",
"textures": {
"side": "blocks/wood/fence-birch",
"top": "blocks/wood/fence-birch-top"
}
}
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
Is this one also giving an error? It says "fence_inventory" in the error you posted earlier, not "fence_post". "fence_inventory" would be referenced by the item model, not another block model.
Yeah, all my similarly altered fence models are giving me that error, the post model was the simplest one giving the error, so i posted it.
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
Hmmm... That is odd. Nothing immediately jumps out at me as being wrong.
Is this happening in a version presently available for download? If not would you mind sending it to me via PM. Solving these kinds of "puzzles" is sometimes fun for me.
What's happening is that Minecraft assembles everything as a series of parent/child relationships with each file feeding into the next. As such, things are getting taken partly from default, and partly from the pack, and they're not matching up. Here's a walkthrough for the Oak Fence Post:
STEP 1:
blockstate/fence.json
Comes from: DEFAULT
References block file: "oak_fence_post.json"
STEP 2:
models/block/oak_fence_post.json
Comes from: DEFAULT
Child block file to: "blocks/fence_post.json"
Sends texture called "texture" as "blocks/planks_oak.png"
STEP 3:
models/block/fence_post.json
Comes from: Visibility
Looks for textures called "side" and "top"... but can only find one called "texture".
See the problem? The default files, which you haven't replaced, are supplying your model with one texture named "texture" when it wants two textures named "side" and "top.
The same problem applies to all of the fence models. Somewhere along the line your files are asking for something that the default isn't giving, or vice-versa. There's a simple disconnect somewhere in the sequence of events.
I hope that helps you.
EDIT: Yep, error messages have been eradicated.
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
Putting the CENDENT back in transcendent!
Chain?
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
A sequence or 'chain' of files starting with the blockstate. Basically what I demonstrated above.