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

Marker armor stand should not have passenger offset

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • Minecraft 16w06a, Minecraft 16w07a, Minecraft 16w07b, Minecraft 1.9 Pre-Release 4, Minecraft 1.9, Minecraft 1.9.1 Pre-Release 1, Minecraft 1.9.1 Pre-Release 2, Minecraft 1.9.1 Pre-Release 3, Minecraft 1.9.1, Minecraft 1.9.2, Minecraft 1.9.4, Minecraft 16w21a, Minecraft 1.10 Pre-Release 2, Minecraft 1.10, Minecraft 16w39c, Minecraft 16w40a, Minecraft 16w44a, Minecraft 1.11, Minecraft 1.11.2, Minecraft 17w15a, Minecraft 1.12 Pre-Release 2, Minecraft 1.12 Pre-Release 6, Minecraft 1.12 Pre-Release 7, Minecraft 1.12, Minecraft 1.12.2, Minecraft 17w48a, Minecraft 17w49b, Minecraft 1.13-pre1, Minecraft 1.13, Minecraft 18w31a, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w04b, Minecraft 19w05a, Minecraft 19w06a, Minecraft 1.14.2, Minecraft 1.14.3 Pre-Release 3, 1.15 Pre-Release 2, 1.15 Pre-release 4, 1.15.2, 20w07a
    • Confirmed
    • (Unassigned)

      The bug

      Summoning a marker armor stand with other entity passengers has the passengers offset upwards, even though they should be aligned to the marker stand's position with no offset due to there being no hitbox size.
      This did not happen before 16w snapshots.

      How to reproduce

       /summon armor_stand ~ ~ ~ {Marker:1b,Passengers:[{id:armor_stand,Marker:0b}]}
       /summon armor_stand ~ ~ ~ {Marker:1b,Passengers:[{id:cow}]}

      Some things do work however, such as a marker armor stand passenger or a villager passenger.

      See screenshot of pig and cow and armor stand for a picture of the issue in 1.9 pre-4

            Unassigned Unassigned
            onnowhere Onnowhere
            Votes:
            31 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: