• Icon: Bug Bug
    • Resolution: Fixed
    • 1.13.0.9 Beta, 1.12.1
    • 1.13.0.5 Beta, (14)
      1.12.0.11 Beta, 1.6.0, 1.7.1, 1.7.0, 1.9.0.2 Beta, 1.8.1, 1.9.0, 1.12.0.4 Beta, 1.12.0.6 Beta, 1.11.1, 1.11.4, 1.13.0.4 Beta, 1.13.0.2 Beta, 1.12.0
    • Confirmed
    • Tablet - iOS - iPad Air 2
    • 144453

      Sometimes when I die in The End then re-enter The End, a new Ender Dragon will spawn, even if there was one already there.  

          [MCPE-37590] Multiple Ender Dragons

          At this point, the fix seems to be 100% effective in all new worlds and in all previously existing worlds except for Toycat's. The video leaves no doubt that it's still possible to trigger multiple dragon spawns, but that by itself isn't enough to justify reopening the ticket. Let me try to explain why.

          The essence of fixing a bug is to patch the code that causes it in a new world. The bug can't be considered fixed until it no longer happens in a new world. But many (probably most) bugs affect the world contents, which are saved in the world save files. If the bug also causes damage to the save files, Mojang will also try to repair that damage the first time you load the world in the fixed release. To do that, the developers have to anticipate all the ways the bug could possibly damage the world, figure out how to detect whether a given world has a given kind of damage, and decide the best way to repair it. Needless to say, this is not only very difficult, it's literally impossible sometimes, so the part of a bug fix that repairs damage to old worlds is done on a "best effort" basis. In other words, there is no guarantee that a bug fix can repair your existing worlds perfectly.

          Toycat's world is most likely one where there was damage the developers didn't anticipate and therefore couldn't fix completely. This is especially true because he's well known for "coloring outside the lines". He's done things on the center island that nobody else would do, and his world save is probably quite unique. So after the fix release, it might still have a unique kind of damage that triggers the bug, while other people's repaired worlds don't.

          The upshot is that while it's true that the bug still exists, it has no known impact on anybody but Toycat, and even he isn't being impacted by it any more (other than the cost of replacing all the glass the dragons destroyed). Unless other people start reporting this issue too, there isn't really anything that needs a fix here.

          [MCPE Mod] Auldrick added a comment - At this point, the fix seems to be 100% effective in all new worlds and in all previously existing worlds except for Toycat's. The video leaves no doubt that it's still possible to trigger multiple dragon spawns, but that by itself isn't enough to justify reopening the ticket. Let me try to explain why. The essence of fixing a bug is to patch the code that causes it in a new world. The bug can't be considered fixed until it no longer happens in a new world. But many (probably most) bugs affect the world contents, which are saved in the world save files. If the bug also causes damage to the save files, Mojang will also try to repair that damage the first time you load the world in the fixed release. To do that, the developers have to anticipate all the ways the bug could possibly damage the world, figure out how to detect whether a given world has a given kind of damage, and decide the best way to repair it. Needless to say, this is not only very difficult, it's literally impossible sometimes, so the part of a bug fix that repairs damage to old worlds is done on a "best effort" basis. In other words, there is no guarantee that a bug fix can repair your existing worlds perfectly . Toycat's world is most likely one where there was damage the developers didn't anticipate and therefore couldn't fix completely. This is especially true because he's well known for "coloring outside the lines". He's done things on the center island that nobody else would do, and his world save is probably quite unique. So after the fix release, it might still have a unique kind of damage that triggers the bug, while other people's repaired worlds don't. The upshot is that while it's true that the bug still exists, it has no known impact on anybody but Toycat, and even he isn't being impacted by it any more (other than the cost of replacing all the glass the dragons destroyed). Unless other people start reporting this issue too, there isn't really anything that needs a fix here.

          Chris added a comment -

          Here is a link to the video where it happens: https://youtube.com/watch?v=tyGL3GXq8Ew&t=439s
          Seems like the "fix" in 1.13 only keeps the dragons loaded to reduce the chance of extra spawns. That's why they were able to get back to the central island. It doesn't actually stop the spawning itself. It was just a bandaid fix.

          Chris added a comment - Here is a link to the video where it happens: https://youtube.com/watch?v=tyGL3GXq8Ew&t=439s Seems like the "fix" in 1.13 only keeps the dragons loaded to reduce the chance of extra spawns. That's why they were able to get back to the central island. It doesn't actually stop the spawning itself. It was just a bandaid fix.

          Chris added a comment -

          So, IBXToycat just had 12 dragons spawn in his end and kill him. He posted it on YouTube today. This would be 1.14.1. Looks like this bug may not be fixed after all.

          Chris added a comment - So, IBXToycat just had 12 dragons spawn in his end and kill him. He posted it on YouTube today. This would be 1.14.1. Looks like this bug may not be fixed after all.

          Chris added a comment -

          I had Aksana's issue with a nether portal last night. Eventually it kicked in but I stood there for a good minute. I think that is a separate, also annoying issue. At least the End portal surface is solid, otherwise she would have dropped into the lava. As far as the dragon tho, I have fought her 3 times now in 1.14 and everything seems normal. Only one dragon each time and the knockback seems to have been reduced considerably (feature or bug?). The dragon fight is fun again.

          Chris added a comment - I had Aksana's issue with a nether portal last night. Eventually it kicked in but I stood there for a good minute. I think that is a separate, also annoying issue. At least the End portal surface is solid, otherwise she would have dropped into the lava. As far as the dragon tho, I have fought her 3 times now in 1.14 and everything seems normal. Only one dragon each time and the knockback seems to have been reduced considerably (feature or bug?). The dragon fight is fun again.

          went to check how is it fixed.... could not get in. any advise? 

          Aksana Lapeskina added a comment - went to check how is it fixed.... could not get in. any advise? 

          Veriox22 added a comment -

          This happened to me too! I wasted 20 hours playing in a world but in the end 15 ender dragons spawned and i lost my diamond armor and weapons. I tried to create another world but there were 2 ender dragons in the end! This is so stupid! I can't play survival until it is fixed. I saw in the wiki that this was fixed in bedrock edition 1.12 but the game keeps doing it.

          Veriox22 added a comment - This happened to me too! I wasted 20 hours playing in a world but in the end 15 ender dragons spawned and i lost my diamond armor and weapons. I tried to create another world but there were 2 ender dragons in the end! This is so stupid! I can't play survival until it is fixed. I saw in the wiki that this was fixed in bedrock edition 1.12 but the game keeps doing it.

          Change the title from [Fixed in 1.13] Multiple Ender Dragons to [Fixed] Multiple Ender Dragons. Not only 1.13 fixed this issue but 1.12.1 also did fixed this issue.

          DrownedZombie added a comment - Change the title from [Fixed in 1.13]  Multiple Ender Dragons to [Fixed] Multiple Ender Dragons. Not only 1.13 fixed this issue but 1.12.1 also did fixed this issue.

          1.12.1 was released today and the changelog lists this bug as fixed.

          https://feedback.minecraft.net/hc/en-us/articles/360032928992-Minecraft-1-12-1-Bedrock-

          [Mod] OcelotOnesie added a comment - 1.12.1 was released today and the changelog lists this bug as fixed. https://feedback.minecraft.net/hc/en-us/articles/360032928992-Minecraft-1-12-1-Bedrock-

          What version were you currently play testing in Rylan?

          Euwill Eusebio added a comment - What version were you currently play testing in Rylan?

          Lilyka added a comment -

          I wonder if 1.13.0.9 beta fixes both cases,

          1. Prevents from spawning multiple ender dragons
          2. Automatically kills redundant ender dragons that have already spawned (for players currently suffering from this bug)

          Did someone with affected save data test for case 2?

          Lilyka added a comment - I wonder if 1.13.0.9 beta fixes both cases, Prevents from spawning multiple ender dragons Automatically kills redundant ender dragons that have already spawned (for players currently suffering from this bug) Did someone with affected save data test for case 2?

            zkristoff Zach K
            Votes:
            171 Vote for this issue
            Watchers:
            68 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: