Siphalor
- Siphalor
- siphalor
- Europe/Stockholm
- Yes
- No
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.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.
Siphalor, everything appears to be working fine for me in 17w50a. Closed again.
If you still got an issue, please create a new report.

I think the issue changed a bit. In versions 17w47a and 17w47b, both x- and y-rotation behave like y_rotation.
It would be nice if you could update the issue.
Now x_rotation is correct again and y_rotation doesn't work.
You can reopen this issue in its first version.
(Snapshot 17w50a)
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.
Duplicate: https://bugs.mojang.com/projects/MC/issues/MC-147754
Sorry, didn't find the duplicate :/
Can confirm for 1.15 and 1.15.1 Pre-Release 1