mojira.dev
MC-279325

Broken end portals affected by MC-93185 from before 25w02a not datafixed

MC-93185 was fixed in this snapshot but any worlds affected by it remain broken without an exit portal.

Analysis & Suggested Fix

  • ExitPortalLocation doesn't get datafixed to the correct value if the world was generated before snapshot 25w02a. Changing the Y value from -1 to 1 manually via external tools lets you regenerate the portal by following the reproduction steps below.

    [media]
    [media]


    However it would be best if the portal was automatically regenerated if it's detected that it's Y value is below the world bottom.

Also due to custom worlds the fix it wouldn't be as simple as if(y<1) y = 1. Instead it should be if(y<min_y+1) y = min_y+1

Reproduction Steps

  • Generate a world with seed 78539955276621 in 1.21.4

  • Kill the ender dragon

  • Load the world in 25w02a

  • Run these commands

    • /setblock 3 1 0 minecraft:obsidian

    • /setblock -3 1 0 minecraft:obsidian

    • /setblock 0 1 -3 minecraft:obsidian

    • /setblock 0 1 3 minecraft:obsidian

  • Place end crystals on the obsidian blocks

Observed Results

  • Nothing happens

    [media]

Expected Results

  • The end portal would be regenerated

[media]

Linked issues

Attachments

Comments 7

Thank you for your report!
After consideration, the issue is being closed as Won't Fix.

Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behavior, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.

Quick Links:
๐Ÿ““ Bug Tracker Guidelines โ€“ ๐Ÿ’ฌ Community Support โ€“ ๐Ÿ“ง Mojang Support (Technical Issues) โ€“ ๐Ÿ“ง Microsoft Support (Account Issues)
๐Ÿ““ Project Summary โ€“ โœ๏ธ Feedback and Suggestions โ€“ ๐Ÿ“– Game Wiki

So many worlds that have been broken since before 1.13 will remain broken. This is a first from mojang. Not fixing affected worlds when a release version was affected... let alone 8+ full releases!

A wonโ€™t fix resolution is quite puzzling to me. The fix is quite trivial and the issue makes several world literally unbeatable (pretty important). I hope Mojang reconsiders

this is fixable! you need to place one end crystal on an obsidian right next to the pillar (works both diagonally like on my screenshot or just adjacent to it). it creates a new exit portal on the highest block at 0,0 - that is on the old pillar unless you built something higher up at 0,0. tested on 1.21.11 and 26.1-s1

2025-12-17_18.24.15.png
2025-12-17_18.24.29.png

Your method does not work. The portal regenerates partially below the void, leaving it broken.

it seems i have spread misinformation on the internet, so i tested it more and heres the results:

the crystal can be placed anywhere, not just next to the pillar

and this method ONLY works if you: last opened the world and loaded the end in versions 1.16.x - 1.20-pre5 (i tried 1.16.1 then), and then upgrade to 1.20-pre6 or newer. if the dragon was killed in the older version, you need to place the crystal, otherwise it just generates once the dragon dies.

doesnt work if the end was already first loaded in 1.20-pre6 or newer, or if upgrading from before 1.16.x.

it has something to do with how they changed how the exitportallocation is stored in level.dat.

TLDR its only solvable if the world hasnt been open in two and a half years, the bug is still very much there

Ceresjanin123

(Unassigned)

Community Consensus

Platform

Low

Datafixer

25w02a, 1.21.10, 25w43a

Retrieved