1.18, of course, generates worlds with a different set of strongholds from that of a world created in a previous version.
The bug:
If a world created prior to version 1.18 is upgraded, /locate and the Eye of Ender will direct the player to one of these new 1.18 strongholds - even if the chunks that this 1.18 stronghold would generate in are old chunks that never had a stronghold.
Reproduce:
Create a Creative Mode world in version 1.X that generates strongholds, entitled w1.X.
Copy the world and name the copy w1.18.
Open the w1.18 copy in version 1.18 and use /locate or an Eye of Ender to find the nearest stronghold. Copy down the coordinates of the stronghold. If the stronghold is entirely below Y:0, delete the worlds and start over from step 1.
Open the original w1.X world in version 1.X and go to the coordinates you just copied down, loading in those chunks. Verify that there is no stronghold at these coordinates.
Finally, upgrade and open the original w1.X world in version 1.18. Use /locate or an Eye of Ender to find where the game thinks the nearest stronghold is.
Expected result:
The game locates the nearest stronghold that actually exists, likely in a newly-generated 1.18 chunk.
Bugged result:
The game points you towards the location of the stronghold that you found in the copy w1.18 in step 3, but does not actually exist in the upgraded w1.X chunks.
This is a terrible inconvenience for people who have survival worlds that they've extensively explored in versions prior to 1.18, but didn't bother locating a stronghold in until after upgrading said worlds to 1.18. I spent several hours attempting to locate just such a stronghold, in a world which I can attach if desired.
I have attempted to reproduce this bug with other generated structures, but so far I can only verify that strongholds are affected. If more info comes to light I will update this report accordingly.
Comments 9
MC-244692 , MC-244153 and MC-243990 refer to this same problem.
I think the source of the issue is that 1.18 generates different locations for strongholds than what 1.17 and earlier were producing.
Beyond the problem of strongholds not generating if their chunk was already generated, the location changes mean that /locate and Eyes of Ender no longer point to strongholds that were generated in 1.17 or earlier.
D E, in the third bug it's explicitly stated that the game is pointing the player to chunks that haven't been generated yet, so I don't know what's up with that, but the other two are definitely related. Truly sad.
Dhranios, dang that's an old issue. That's probably what this is a duplicate of. It was rather difficult to find bugs on this topic. Didn't know it affected older versions.
This was my first bug report, what do I do now? Should I (or can I) close the report myself? Do I need to wait for a mod to report it as duplicate?
This bug has the same root cause as MC-135996 , the location of strongholds changed between versions (between 1.12 and 1.13 in that case).
From looking at it on ChunkBase the change in location for 1.12 to 1.13 is usually minor for the innermost strongholds but diverges more the further out you go from the origin.
Meanwhile the change in location between 1.17 and 1.18 is much more noticeable at the innermost strongholds.
Duplicate of MC-135996.
@Brent Wrong. This bug pertains specifically to the upgrading of old worlds, whereas that one deals with the inaccuracy of /locate in general. I would consider this a Duplicate of #MC-135996.
Thank you for your report!
We're tracking this issue in MC-135996, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Sounds like MC-135996.