The bug
Damage values in /setblock are ignored for all of the new blocks, yielding the default state for every number input.
How to reproduce
/setblock ~ ~ ~ stripped_oak_log 2
→ It's on its side/setblock ~ ~ ~ stripped_warped_stem 2
→ ❌ It's facing up
Linked issues
is duplicated by 2
Comments 4
It is still an issue in bedrock 1.16.201
I've been testing commands to counter beehive/nest exploits, but only the default block is available in commands.
Apart from what Jake said, other blocks as log, leaves and other can set with value id's above the existing ones with them defaulting to 0
/setblock ~ ~ ~ log 20
Would set a log 0 block in that position
Some other blockstates as powered redstone dust or redstone dust facing to only one specific side cannot be placed
And other blocks as redstone torch are divided into 2 blocks, redstone_torch and unlit_redstone_torch, when they should be one block with multiple states.
I would suggest to change to a format similar to java edition 1.13+ setblock where you can set each block property manually.
/setblock ~ ~ ~ redstone_wire[power=15]
/setblock ~ ~ ~ oak_log[facing=north]
With the changes to new custom blocks in addons that are rn on experimental, when this changes get added to the vanilla blocks, it would be easier to access the properties of them, and with that allowing to fix this issues we have right now.
[data_value=value] is already in the latest betas, see MCPE-112938
Might be the same issue as MCPE-65534