When frosted ice ages it's data value goes up by 1 per age (tested with the testforblock command)
But whenever you try to setblock frosted ice with that age, it's age will be 0 under any circumstances.
/setblock 6 47 -46 minecraft:frosted_ice 2should have set frosted ice with age 2, but it sets frosted ice with age 0.
This is really inconsistent when you consider that cloning frosted ice with different ages works.
Comments 12
this limits to what map makers can do, I tried to add moving ice blocks that freeze the water, and the water would unfreeze after a specific amount of time, now I can't add the notifier that says how far it is with melting 😞
Please reconsider this resolution
Also, it makes no sense that you can setblock any block, with any blockstate conbination, and any datatag, but not set frosted ice with an age value
I request you take another look at this, @unknown, because it just limits what map makers can do, and it provides inconsistency
Confirmed for
15w47c
This is really inconsistent when you consider that cloning frosted ice with different ages works
perhaps mojang would reconsider this then; and I think I saw some other tickets having done the same
How is this working as intended? It is inconsistent behaviour.