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

/summon does not fail anymore when providing invalid block data for enderman and falling_block


    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • Minecraft 18w05a, Minecraft 1.13-pre3, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 19w12b, Minecraft 19w13b, Minecraft 19w14a, Minecraft 19w14b, 20w51a, 21w03a, 1.16.5, 21w05b, 21w06a, 21w08b, 21w17a, 1.17.1, 1.18.2, 22w16b, 1.19, 1.19.2
    • Confirmed
    • Commands

      The bug

      In 1.12.2 /summon used to fail for falling_block if the specified block was not valid:

      /summon falling_block ~ ~ ~ {Block:"invalid",Time:-2000}

      In current versions this is not the case and there is not even an error message in the log.
      For endermen the command did not fail unless you provided an invalid short (for example 32768s) but it used the outdated integer id system anyways.

      How to reproduce

      1. Try summoning an enderman holding an invalid block
        /summon minecraft:enderman ~ ~ ~ {carriedBlockState:{Name:"minecraft:invalid"}}
      2. Try inspecting its carriedBlockState tag
        /data get entity @e[type=enderman,limit=1] carriedBlockState

        It does not exist

      1. Try summoning a falling_block entity for an invalid block
        /summon minecraft:falling_block ~ ~ ~ {BlockState:{Name:"invalid"},Time:-2000}
      2. Inspect its BlockState tag
        /data get entity @e[type=falling_block,limit=1] BlockState

        It defaulted to sand

            Unassigned Unassigned
            marcono1234 [Mod] Marcono1234
            4 Vote for this issue
            2 Start watching this issue