Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-243092

Summon a "falling block" within a block of same type causes the block to stop rendering or just disappear.

XMLWordPrintable

    • Icon: Bug 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:

      1. Open any world, with commands active
      2. /setblock ~ ~ ~2 stone
      3. /summon minecraft:falling_block ~ ~.8 ~2 {NoGravity:1b,BlockState:{Name:"minecraft:stone"}}

      Easy way to reproduce it, for block stop rendering:

      1. Open any world, with commands active
      2. /setblock ~ ~ ~2 stone
      3. /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")

      1. Open any world, with commands active
      2. /setblock ~ ~ ~2 stone
      3. /summon minecraft:falling_block ~ ~.8 ~2 {Time:1,NoGravity:1b,BlockState:{Name:"minecraft:sandstone"}}

         

       

            Unassigned Unassigned
            KamiADN KamiADN
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: