Affects Version/s: Minecraft 1.10.2, Minecraft 1.11.2, Minecraft 1.13, Minecraft 18w30a, Minecraft 18w32a, Minecraft 1.13.1, Minecraft 1.13.2-pre1, Minecraft 1.13.2-pre2, Minecraft 1.13.2, Minecraft 18w43a, Minecraft 18w43b, Minecraft 18w43c, Minecraft 18w44a, Minecraft 18w45a, Minecraft 18w46a, Minecraft 18w47a, Minecraft 18w47b, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w02a, Minecraft 19w03b, Minecraft 19w03c, Minecraft 19w04b, Minecraft 19w05a, Minecraft 19w06a, Minecraft 19w08b, Minecraft 19w09a, Minecraft 19w11a, Minecraft 19w11b, Minecraft 19w12b
Fix Version/s: None
The ender dragon cannot be respawned at an end portal if the dragon was killed before 1.9 and the resulting end portal is generated at a location other than (0,<y>,0).
Furthermore, when placing the necessary end crystals on the portal, this error will be logged:
What I expected to happen was:
The ender dragon would respawn.
What actually happened was:
The ender dragon did not respawn.
- Download the attached world world_MC-104897.zip
- Load the world in 1.10.1 or later.
- Enter the active end portal. (You should spawn at a stronghold)
- Locate the exit portal, and place the necessary crystals.
→ See that the respawning process does not restart.
Code analysis (from
What seems to be happening (using MCP names) is that the fix for
MC-103497 made DragonFightManager.respawnDragon() always try to use exitPortalLocation, even though findExitPortal() only sets this field when the detected portal is at (0,0). It should instead use the value returned by findExitPortal(), properly offset of course.
Workaround can be found here.