Minecraft
  1. Minecraft
  2. MC-109020

Weird behavior with taged & markered armor stands.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: Minecraft 16w42a, Minecraft 16w43a
    • Fix Version/s: Minecraft 16w44a
    • Security Level: Minecraft - Public (Viewable by everyone)
    • Labels:
      None
    • Confirmation Status:
      Confirmed

      Description

      Let's do a experiment :

      Place 3 command blocks that you'll activate in this order :

      /summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:1}
      /entitydata @e[tag=A] {Tags:["B"]}
      /execute @e[tag=B] ~ ~ ~ say test
      

      Everything will work as expected, and the armor_stand will say "test".

      Now kill the armor_stand, and change the 3rd command with this :

      /execute @e[tag=B] ~ ~ ~ kill @e[r=0]
      

      Reactivate all the command blocks.

      Strangely, the armor_stand won't be killed, and "Failed to execute 'kill @e[r=0]' as Armor Stand" will appear in the command output.

      Kill the armor_stand again, and just set the marker's value in the 1st command block to 0.

      Reactivate all the command blocks.

      Now, the armor_stand was killed...

      Initially, I thought that this bug is related to MC-88533, but the basic

      /summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:1}
      

      &

      /execute @e[tag=A] ~ ~ ~ kill @e[r=0]
      

      works perfectly.

        Issue Links

          Activity

          Hide
          [Mod] Neko added a comment -

          Cannot reproduce. Using the first two commands then using /execute @e[tag=B] ~ ~ ~ kill @e[r=0] will kill the armor stand.

          Show
          [Mod] Neko added a comment - Cannot reproduce. Using the first two commands then using /execute @e[tag=B] ~ ~ ~ kill @e[r=0] will kill the armor stand.
          Hide
          Bytenka added a comment -

          Sorry for the mistake I've made... In the first command, the tag "marker" must be set to 1.

          Show
          Bytenka added a comment - Sorry for the mistake I've made... In the first command, the tag "marker" must be set to 1.
          Hide
          Bytenka added a comment - - edited

          Still in 1.11-pre1. The only way to bypass that is by using @e[r=1,c=1]

          Show
          Bytenka added a comment - - edited Still in 1.11-pre1. The only way to bypass that is by using @e [r=1,c=1]
          Hide
          [Mod] FVbico (Steven Verberne) added a comment -

          Are you sure it isn't MC-88533 you're seeing?

          Show
          [Mod] FVbico (Steven Verberne) added a comment - Are you sure it isn't MC-88533 you're seeing?
          Hide
          Bytenka added a comment -

          Hum, you're certainly right. It seems like more MC-88533 related

          (
          /summon armor_stand ~ ~1 ~

          {Tags:["A"],Marker:1}

          /execute @e[tag=A] ~ ~ ~ kill @e[r=0]
          won't work now.
          )

          Show
          Bytenka added a comment - Hum, you're certainly right. It seems like more MC-88533 related ( /summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:1} /execute @e [tag=A] ~ ~ ~ kill @e [r=0] won't work now. )

            People

            • Assignee:
              [Mojang] Searge (Michael Stoyke)
              Reporter:
              Bytenka
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                CHK: