The thread itself, yes. However it was last updated in september, and is still a guide for the current format (as it really hasn't changed much since my last edit). Its age is actually less of an issue than the fact it is not as complete and in-depth as I originally wanted.
So really it still a great resource for anyone wanting to add custom models to their pack.
Rollback Post to RevisionRollBack
"I'm an outsider by choice, but not truly.
It’s the unpleasantness of the system that keeps me out.
I’d rather be in, in a good system. That’s where my discontent comes from:
being forced to choose to stay outside.
My advice: Just keep movin’ straight ahead.
Every now and then you find yourself in a different place."
-George Carlin
It is phenomenally frustrating that Mojang decided implement alternate textures in this way. While it's better than nothing, we have(had) 2 previously standard methods for alternate textures: Block metadata which Mojang did away with, and MCP which is a pretty good indicator of what the community wants.
Instead we get a method for randomly having textures pop up without any form of control? Grr...
It is phenomenally frustrating that Mojang decided implement alternate textures in this way. While it's better than nothing, we have(had) 2 previously standard methods for alternate textures: Block metadata which Mojang did away with, and MCP which is a pretty good indicator of what the community wants.
Instead we get a method for randomly having textures pop up without any form of control? Grr...
They got rid of metadata because they needed a new way to make different versions of the same block without having the restriction of only 16 versions of a single block (which is what metadata did). The Block States method lets Mojang (& modders) add unlimited versions of a single block.
It is phenomenally frustrating that Mojang decided implement alternate textures in this way. While it's better than nothing, we have(had) 2 previously standard methods for alternate textures: Block metadata which Mojang did away with, and MCP which is a pretty good indicator of what the community wants.
Instead we get a method for randomly having textures pop up without any form of control? Grr...
Its better this way. It allows me to do things like have a random lilypad have an actual 3D flower on it instead of just a flat texture. It allows for randomized textures, as well as randomized models, or both!
Rollback Post to RevisionRollBack
Cast aside your festive doylaks: dragon stuff is about to happen.
Multiplayer is lonely once you understand how it actually works.
Seriously, though. I dig the ability for random textures/models (It does amazing things for ruins/stone/cobble/etc) but not being able to spawn a block with a custom texture is maddening. Fixing it because of the limit, sure, but to remove the ability altogether? Bollocks.
Well entity editing will be possible. One can hope expanded block state functionality will come around eventually.
I know entity animation editing is coming & I can't wait to play with that! But expanded block state functionality will be possible with Resource Packs with the Modding API, BUT not currently though.
I'm not sure why, but the brick textures never seem to load. I've tried everything. I've checked and rechecked the code, but the game always renders both the item and the block as the purple and black squares. Help!
Right, I've started writing up a little bit more for the guide. Currently adding two more mini sections on how to make random textures for a normal texture (the example I have now with grass is actually a bit of a special case) and with something like logs which are also different than the other blocks. I'll have a look around and see if there are any special model formats for commonly used blocks.
I'll also try and add a section about making alternate textures appear on only one side of a block instead of all sides like they do by default.
I figure since there are so many other tutorials about making custom models themselves I should just focus on some useful things you can do once you've got the models or extra textures made.
Hmmmm, can't say I've had that issue before... If they work when they're first in the list then it means the separate model files should be correct too...
What version of minecraft are you running? Try going to a version one patch up or down, see if that fixes it. If not then it's probably not a minecraft bug at least.
Each variant works when it is first in the list, and I do have Alternate Blocks enabled
Are you plopping down a melon field to make sure it's working? The random system in Minecraft is based on the world position and persistent. It wouldn't surprise me if it always was using the first option for that 1 particular melon. It certainly won't change when you f3+t if that's what you're thinking.
Otherwise, does the launcher log give you any info? I don't see anything that should be an issue.
Rollback Post to RevisionRollBack
"I'm an outsider by choice, but not truly.
It’s the unpleasantness of the system that keeps me out.
I’d rather be in, in a good system. That’s where my discontent comes from:
being forced to choose to stay outside.
My advice: Just keep movin’ straight ahead.
Every now and then you find yourself in a different place."
-George Carlin
That's from one year ago...
Putting the CENDENT back in transcendent!
The thread itself, yes. However it was last updated in september, and is still a guide for the current format (as it really hasn't changed much since my last edit). Its age is actually less of an issue than the fact it is not as complete and in-depth as I originally wanted.
So really it still a great resource for anyone wanting to add custom models to their pack.
"I'm an outsider by choice, but not truly.
It’s the unpleasantness of the system that keeps me out.
I’d rather be in, in a good system. That’s where my discontent comes from:
being forced to choose to stay outside.
My advice: Just keep movin’ straight ahead.
Every now and then you find yourself in a different place."
-George Carlin
Instead we get a method for randomly having textures pop up without any form of control? Grr...
They got rid of metadata because they needed a new way to make different versions of the same block without having the restriction of only 16 versions of a single block (which is what metadata did). The Block States method lets Mojang (& modders) add unlimited versions of a single block.
Its better this way. It allows me to do things like have a random lilypad have an actual 3D flower on it instead of just a flat texture. It allows for randomized textures, as well as randomized models, or both!
Cast aside your festive doylaks: dragon stuff is about to happen.
Multiplayer is lonely once you understand how it actually works.
Alpha 1.0.4
Seriously, though. I dig the ability for random textures/models (It does amazing things for ruins/stone/cobble/etc) but not being able to spawn a block with a custom texture is maddening. Fixing it because of the limit, sure, but to remove the ability altogether? Bollocks.
Cast aside your festive doylaks: dragon stuff is about to happen.
Multiplayer is lonely once you understand how it actually works.
Alpha 1.0.4
It will not change in 1.9. If it does, then I would be surprised.
Cast aside your festive doylaks: dragon stuff is about to happen.
Multiplayer is lonely once you understand how it actually works.
Alpha 1.0.4
I know entity animation editing is coming & I can't wait to play with that! But expanded block state functionality will be possible with Resource Packs with the Modding API, BUT not currently though.
As for the block, post your blockstates code and your block code here, I'll see if I can help you out.
Edit: Added code.
It is somewhat complicated to explain.
But feel free to look at how i do it in my pack (see my sig.) and reuse the .JSON files if you want.
All my logs except spruce and jungle have random alternates.
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
I'll also try and add a section about making alternate textures appear on only one side of a block instead of all sides like they do by default.
I figure since there are so many other tutorials about making custom models themselves I should just focus on some useful things you can do once you've got the models or extra textures made.
{
"variants": {
"normal": [
{ "model": "melon/melon1" },
{ "model": "melon/melon2" },
{ "model": "melon/melon3" },
{ "model": "melon/melon4" }
]
}
}
What version of minecraft are you running? Try going to a version one patch up or down, see if that fixes it. If not then it's probably not a minecraft bug at least.
Are you plopping down a melon field to make sure it's working? The random system in Minecraft is based on the world position and persistent. It wouldn't surprise me if it always was using the first option for that 1 particular melon. It certainly won't change when you f3+t if that's what you're thinking.
Otherwise, does the launcher log give you any info? I don't see anything that should be an issue.
"I'm an outsider by choice, but not truly.
It’s the unpleasantness of the system that keeps me out.
I’d rather be in, in a good system. That’s where my discontent comes from:
being forced to choose to stay outside.
My advice: Just keep movin’ straight ahead.
Every now and then you find yourself in a different place."
-George Carlin