If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
What does your leaf model look like? (Also, when posting text, please use Pastebin rather than screenshots) If it's the default then there's your problem right there!
When adding textures to a block with a child model you have to work with the designations that already exist in that block's model. Leaves don't know what "top" or "side" is. All they're expecting to see is "all" and since you didn't provide "all" you got an error. So you either need to leave them with a single texture or else change the base leaf model to be expecting the textures you want to give it.
What does your leaf model look like? (Also, when posting text, please use Pastebin rather than screenshots) If it's the default then there's your problem right there!
When adding textures to a block with a child model you have to work with the designations that already exist in that block's model. Leaves don't know what "top" or "side" is. All they're expecting to see is "all" and since you didn't provide "all" you got an error. So you either need to leave them with a single texture or else change the base leaf model to be expecting the textures you want to give it.
I hope that helps you.
How would I be able to change the base leaf model?
Rollback Post to RevisionRollBack
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
How would I be able to change the base leaf model?
Well... unless you want to change it for every type of leave you should probably leave it alone.
Instead, it might work to make your model a child to a different base model that already has distinct top, bottom, and side textures. I forget the exact file name, but I think the base model for the pillar blocks should server your purposes nicely. Well... mostly. There's no way to give a block that isn't orientable a "front" face. You'd just have "top", "bottom", and "side" as your texture designations.
If there isn't an existing block model that works, you can make your own model. I suggest using BlockBench and looking very closely at how the base models for both leaves and pillars work. Though if this is the only leaf block you want to change then it'd be best just to replace that leave with a custom model all its own and make it a child of "block/block" to get it the proper size in inventories and the like.
Well... unless you want to change it for every type of leave you should probably leave it alone.
Instead, it might work to make your model a child to a different base model that already has distinct top, bottom, and side textures. I forget the exact file name, but I think the base model for the pillar blocks should server your purposes nicely. Well... mostly. There's no way to give a block that isn't orientable a "front" face. You'd just have "top", "bottom", and "side" as your texture designations.
If there isn't an existing block model that works, you can make your own model. I suggest using BlockBench and looking very closely at how the base models for both leaves and pillars work. Though if this is the only leaf block you want to change then it'd be best just to replace that leave with a custom model all its own and make it a child of "block/block" to get it the proper size in inventories and the like.
I hope that helps you.
I'll see if the pillar code would work in place of the old code I made. Cheers!
Rollback Post to RevisionRollBack
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Well... unless you want to change it for every type of leave you should probably leave it alone.
Instead, it might work to make your model a child to a different base model that already has distinct top, bottom, and side textures. I forget the exact file name, but I think the base model for the pillar blocks should server your purposes nicely. Well... mostly. There's no way to give a block that isn't orientable a "front" face. You'd just have "top", "bottom", and "side" as your texture designations.
If there isn't an existing block model that works, you can make your own model. I suggest using BlockBench and looking very closely at how the base models for both leaves and pillars work. Though if this is the only leaf block you want to change then it'd be best just to replace that leave with a custom model all its own and make it a child of "block/block" to get it the proper size in inventories and the like.
I hope that helps you.
Sadly the pillar code would not work infact it broke the pack to the point where minecraft was not willing to work with my resource pack after tweaking the code trying to get it to work nothing happened. I'm trying to replace all the leaf blocks with Christmas lights on the side but now I understand this may not be as possible as I think.
Rollback Post to RevisionRollBack
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Sadly the pillar code would not work infact it broke the pack to the point where minecraft was not willing to work with my resource pack after tweaking the code trying to get it to work nothing happened. I'm trying to replace all the leaf blocks with Christmas lights on the side but now I understand this may not be as possible as I think.
Can you post your new model file please? This should honestly be pretty easy. I think you're just not understanding something fundamental about how this system works.
Can you post your new model file please? This should honestly be pretty easy. I think you're just not understanding something fundamental about how this system works.
Alrighty I would think I would understand sense I've created 3D models and done this before with other blocks but here.
{
"parent": "block/jungle_leaves",
"textures": {
"end": "blocks/leaves_jungle_2",
"side": "blocks/leaves_jungle"
}
}
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
OK, so... why do you have jungle_leaves as your parent block? If you're replacing jungle leaves with this model, that should be what this model file is named. You can't have a model be its own child.
More to the point, if you've done models before why not just do a completely original model as I suggested and make it a child of "block/block" to get the size and positioning information? That would probably be easier on you.
I have a graphic somewhere on my other computer that I made to explain how these things fit together to someone else. If I remember I'll try to post it here for you as well. It won't be exact to your situation like it was to his, but it should help you none the less.
The Meaning of Life, the Universe, and Everything.
Join Date:
7/18/2017
Posts:
105
Minecraft:
SonicJDF
Member Details
Thanks the reason I have jungle_leaves is because when you put leaves down it shows the normal textures.
Rollback Post to RevisionRollBack
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Yea, particularly because of the biome coloring a custom model mapped the way you want it would probably be the easiest way to go.
I also attached the graphic I was talking about. Maybe seeing how things connect might work better for you. Like I said, it's a different but similar case of someone not hooking up parent and child models properly so it might at least help a bit to see a similar case. I dunno. Worth a try anyway.
Just remember, it's all about matching like with like. If an input is expecting something, make sure the output on the other file matches that name.
The Meaning of Life, the Universe, and Everything.
Join Date:
7/18/2017
Posts:
105
Minecraft:
SonicJDF
Member Details
Alrighty thanks I will work on the leaves when I got the time right now im working on something else on the pack! Talk to you again soon!
Rollback Post to RevisionRollBack
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
I'm trying to make the leaves have different textures on different sides. (Unknown Texture Error Is Happening)
(What I have done.) sorry if the resolution is terrible lol (I already know its bad don't need to say :3)
Textures
I don't understand whats going on this is a add-on pack to another pack im making.
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
What does your leaf model look like? (Also, when posting text, please use Pastebin rather than screenshots) If it's the default then there's your problem right there!
When adding textures to a block with a child model you have to work with the designations that already exist in that block's model. Leaves don't know what "top" or "side" is. All they're expecting to see is "all" and since you didn't provide "all" you got an error. So you either need to leave them with a single texture or else change the base leaf model to be expecting the textures you want to give it.
I hope that helps you.
How would I be able to change the base leaf model?
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Well... unless you want to change it for every type of leave you should probably leave it alone.
Instead, it might work to make your model a child to a different base model that already has distinct top, bottom, and side textures. I forget the exact file name, but I think the base model for the pillar blocks should server your purposes nicely. Well... mostly. There's no way to give a block that isn't orientable a "front" face. You'd just have "top", "bottom", and "side" as your texture designations.
If there isn't an existing block model that works, you can make your own model. I suggest using BlockBench and looking very closely at how the base models for both leaves and pillars work. Though if this is the only leaf block you want to change then it'd be best just to replace that leave with a custom model all its own and make it a child of "block/block" to get it the proper size in inventories and the like.
I hope that helps you.
I'll see if the pillar code would work in place of the old code I made. Cheers!
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Sadly the pillar code would not work infact it broke the pack to the point where minecraft was not willing to work with my resource pack after tweaking the code trying to get it to work nothing happened. I'm trying to replace all the leaf blocks with Christmas lights on the side but now I understand this may not be as possible as I think.
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Can you post your new model file please? This should honestly be pretty easy. I think you're just not understanding something fundamental about how this system works.
Alrighty I would think I would understand sense I've created 3D models and done this before with other blocks but here.
{
"parent": "block/jungle_leaves",
"textures": {
"end": "blocks/leaves_jungle_2",
"side": "blocks/leaves_jungle"
}
}
Doing leaves does not show up the textures ):
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
OK, so... why do you have jungle_leaves as your parent block? If you're replacing jungle leaves with this model, that should be what this model file is named. You can't have a model be its own child.
More to the point, if you've done models before why not just do a completely original model as I suggested and make it a child of "block/block" to get the size and positioning information? That would probably be easier on you.
I have a graphic somewhere on my other computer that I made to explain how these things fit together to someone else. If I remember I'll try to post it here for you as well. It won't be exact to your situation like it was to his, but it should help you none the less.
Thanks the reason I have jungle_leaves is because when you put leaves down it shows the normal textures.
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF
Yea, particularly because of the biome coloring a custom model mapped the way you want it would probably be the easiest way to go.
I also attached the graphic I was talking about. Maybe seeing how things connect might work better for you. Like I said, it's a different but similar case of someone not hooking up parent and child models properly so it might at least help a bit to see a similar case. I dunno. Worth a try anyway.
Just remember, it's all about matching like with like. If an input is expecting something, make sure the output on the other file matches that name.
Alrighty thanks I will work on the leaves when I got the time right now im working on something else on the pack! Talk to you again soon!
If you have mistakes in something you create and don't like them yet release the thing you created to people. then you are letting yourself down and the people you send it to down. -SonicJDF