-
Bug
-
Resolution: Duplicate
-
None
-
20w51a
-
None
-
Windows 10, Java version 15.
-
Unconfirmed
-
(Unassigned)
The Bug
Changing the 'BlockState' value of a falling block with commands doesn't update client-side (doesn't visually update) causing the block that's falling not actually be the block that lands. see attached video.
NOTE: Reloading the world/relogging updates the appearance of the block.
Steps to reproduce
- Put 2 command blocks next to each other
- Put this command in the first one: /summon minecraft:falling_block ~ ~1 ~ {Time:1,NoGravity:1b}
- Put this command in the second one: /data merge entity @e[type=minecraft:falling_block,limit=1,sort=nearest] {BlockState:{Name:"minecraft:gravel"}}
- Power the first command block, then the second one.
- Notice how the block doesn't visually change.
- Run this command: /data merge entity @e[type=minecraft:falling_block,limit=1,sort=nearest] {NoGravity:0b}
- Notice how the block changes to the correct one only on landing.
- duplicates
-
MC-72849 Block state of falling block doesn't visually update when modified with /data command
- Reopened