mojira.dev
MCPE-37590

Multiple Ender Dragons

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.  

Linked issues

BDS-1172 So I went to the end in my survival world to fight the dragon and get an elytra I got so excited but when I spawned into the end there were like 4 dragons and I instantly died which made me lose all of my stuff. Resolved BDS-1256 After I died trying to defeat the ender dragon, I went back and 2 more spawned Resolved MCPE-37611 Multiple Ender Dragons Spawned Resolved MCPE-37618 Ender Dragon multiplying bug Resolved MCPE-37742 multiple ender dragons spawned Resolved

Attachments

Comments 84

I am having the same issue on Minecraft Windows 10 edition. I have had 3 dragons in the end when I die. Currently, three appears to be the maximum. I am playing on a Lenovo Windows 10. 

[media]
silentwisperer

This bug happens when dragons fly through end gateways, and there does not seem to be a max (have gotten 15+) Honestly a very easy bug to take advantage of, and seeing as how laggy and buggy dragons already are, this is an easy way to kill the end dimension.

Step-by-step process to reproduce this bug:
https://youtu.be/y312W9CTLbk

[media]

End gateways can't be the only way to cause it, because this happened to me before I had defeated the first dragon which would mean there were no gateways yet. I also didn't get the egg from killing the first dragon. I don't know if the second one broke the egg by landing on the pillar or what. I looked around the end everywhere I could and back at spawn as well. Nothing.

Mathew Backlund

This has happened to me. Xbox bedrock version. The recent changes to the ender dragons attacks are making it near impossible to kill and now I have 3 dragons. Haven't been able to kill a single one. Switched to peaceful and they are still wrecking me. Finally got all the pillars out and haven't been able to kill them. Should have end reset option on bedrock or disable autosave.

Mathew Backlund

I turned back to easy after disabling the pillars I know you can't kill it in peaceful

74 more comments
Aksana Lapeskina

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

[media]

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.

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. 😞

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.

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.

Zach K

(Unassigned)

144453

Confirmed

Tablet - iOS - iPad Air 2

ender_dragon, multiple, realms

1.13.0.5 Beta, 1.12.0.11 Beta, 1.6.0, 1.7.1, 1.7.0, ..., 1.11.1, 1.11.4, 1.13.0.4 Beta, 1.13.0.2 Beta, 1.12.0

1.13.0.9 Beta, 1.12.1

Retrieved