Can't set leaves blockstates
So leaves (e. g. minecraft:spruce_leaves) have two properties: decayable and check_decay.
So I tried to have a different model for decayable=false,check_decay=false:
{
"variants": {
"decayable=true,check_decay=false": { "model": "bookshelf" },
"decayable=true,check_decay=true": { "model": "bookshelf" },
"decayable=false,check_decay=true": { "model": "bookshelf" },
"check_decay=false,decayable=false": { "model": "granite" }
}
}
The resource pack is loading fine but no matter what block state I set with setblock, the model used is always the standard model.
By adding "normal": { "model": "andesite" } I figured out that Minecraft is only using the normal block model. That's very inconsistent as you can set custom blockstate models for all other blocks.
Created Issue:
Can't set leaves blockstates
So leaves (e. g. minecraft:spruce_leaves) have two properties: decayable and check_decay.
So I tried to have a different model for decayable=false,check_decay=false:
{ "variants": { "decayable=true,check_decay=false": { "model": "bookshelf" }, "decayable=true,check_decay=true": { "model": "bookshelf" }, "decayable=false,check_decay=true": { "model": "bookshelf" }, "check_decay=false,decayable=false": { "model": "granite" } } }The resource pack is loading fine but no matter what block state I set with setblock, the model used is always the standard model.
By adding {{"normal":
{ "model": "andesite" }}} I figured out that Minecraft is only using the normal block model. That's very inconsistent as you can set custom blockstate models for all other blocks.
So leaves (e. g. minecraft:spruce_leaves) have two properties: decayable and check_decay.
So I tried to have a different model for decayable=false,check_decay=false:
{ "variants": { "decayable=true,check_decay=false": { "model": "bookshelf" }, "decayable=true,check_decay=true": { "model": "bookshelf" }, "decayable=false,check_decay=true": { "model": "bookshelf" }, "check_decay=false,decayable=false": { "model": "granite" } } }The resource pack is loading fine but no matter what block state I set with setblock, the model used is always the standard model.
By adding {{ "normal":
{ "model": "andesite" }}} I figured out that Minecraft is only using the normal block model. That's very inconsistent as you can set custom blockstate models for all other blocks.
duplicates
So leaves (e. g. minecraft:spruce_leaves) have two properties: decayable and check_decay.
So I tried to have a different model for decayable=false,check_decay=false:
{ "variants": { "decayable=true,check_decay=false": { "model": "bookshelf" }, "decayable=true,check_decay=true": { "model": "bookshelf" }, "decayable=false,check_decay=true": { "model": "bookshelf" }, "check_decay=false,decayable=false": { "model": "granite" } } }The resource pack is loading fine but no matter what block state I set with setblock, the model used is always the standard model.
By adding {{ "normal":
{ "model": "andesite" }
}}I figured out that Minecraft is only using the normal block model. That's very inconsistent as you can set custom blockstate models for all other blocks.So leaves (e. g. minecraft:spruce_leaves) have two properties: decayable and check_decay.
So I tried to have a different model for decayable=false,check_decay=false:
{ "variants": { "decayable=true,check_decay=false": { "model": "bookshelf" }, "decayable=true,check_decay=true": { "model": "bookshelf" }, "decayable=false,check_decay=true": { "model": "bookshelf" }, "check_decay=false,decayable=false": { "model": "granite" } } }The resource pack is loading fine but no matter what block state I set with setblock, the model used is always the standard model.
By adding "normal": { "model": "andesite" } I figured out that Minecraft is only using the normal block model. That's very inconsistent as you can set custom blockstate models for all other blocks.
This is exactly the same thing: the client is not informed about the states changing until the client interacts with the block; your models do load, but don’t show due to the lack of that update.
duplicates
That's not a duplicate
MC-60242is about something really different.Firstly the issue aren't really related to each other and secondly with 1.13 it really makes sense to have those different usable blockstates.
Sorry about that
Does
MC-77170describe your issue? If not, could you please attach a resource pack which can be used to reproduce this issue?That's not the same issue as described, this is about the block state file ignoring every block state combination and only using "normal".
Is this still an issue as of the latest prerelease? The given leaves states were removed.
No, (at least) distance can be used just fine.