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

Killed ender dragon will never disappear if constantly being teleported to a set location, even if the location is the point at which the ender dragon would die

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • None
    • 1.16.1, 20w27a, 20w28a, 20w29a, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 2, 1.16.2 Pre-release 3, 1.16.2 Release Candidate 1, 1.16.2 Release Candidate 2, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Pre-release 1, 1.16.4 Pre-release 2, 1.16.4 Release Candidate 1, 1.16.4, 20w45a, 20w46a, 20w48a, 20w49a
    • None
    • Community Consensus
    • Mob behaviour

      The bug

      If an ender dragon that has been already killed is constantly being teleported to a set location, then it will never go away, meaning that it will never drop experience orbs and the bossbar will never go away, as well as the exploding ender dragon.

      How to reproduce

      1. Create/open a world where the ender dragon has not been killed yet
      2. Create a command block with the command listed at the bottom of this report, set to always active and repeat
      3. Kill the ender dragon without using commands
      4. Notice that the ender dragon will never go away; it will just stay in that same location forever (still with explosion particles, bossbar, and end crystal beam).

      This also occurs if the ender dragon is set to teleport to its usual death point, which is unlike its regular death (if you try to teleport the dragon to a coordinate while it is dying, nothing will happen). I found that occasionally, one death ray (as I'll call it) appears, but is locked and does not disappear even if the DragonPhase NBT value is changed. 

      Video

      https://youtu.be/r34uNSVLEo8

      Command

      tp @e[type=minecraft:ender_dragon] ~ 80 ~

            Unassigned Unassigned
            markderickson [Mod] markderickson
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: