-
Bug
-
Resolution: Duplicate
-
None
-
1.17.1, 1.18 Release Candidate 3
-
None
-
Confirmed
-
Rendering
Summoning a "falling block" within a block of same type causes the block to disappear.
Also, doing the same but with the "time attribute" causes the block to simply stop rendering itself.
In any case, blocks shouldn't disappear, the intended behavior is simply to summon an entity, not to destroy a block.
How to reproduce:
Easy way to reproduce it, for block disappear:
- Open any world, with commands active
/setblock ~ ~ ~2 stone
/summon minecraft:falling_block ~ ~.8 ~2 {NoGravity:1b,BlockState:{Name:"minecraft:stone"}}
Easy way to reproduce it, for block stop rendering:
- Open any world, with commands active
/setblock ~ ~ ~2 stone
/summon minecraft:falling_block ~ ~.8 ~2 {Time:1,NoGravity:1b,BlockState:{Name:"minecraft:stone"}}
Expected behavior:
Summoning a sandstone (or any other block except stone) on a stone block does not cause it to disappear or be destroyed. (Because it's not the same type the "block entity" vs "block")
- Open any world, with commands active
/setblock ~ ~ ~2 stone
/summon minecraft:falling_block ~ ~.8 ~2 {Time:1,NoGravity:1b,BlockState:{Name:"minecraft:sandstone"}}
- duplicates
-
MC-72248 Falling sand creates invisible blocks
- Resolved