So, just gonna keep this short... Upgraded to 1.18, and a certain extreme hills biome that I rather enjoyed and had the intention of building a tunnel through for minecarts, (along with the surrounding plains a forest biomes), has been overwritten by a mesa biome.... A very large Mesa Biome. Yes, I did visit these chunks, literally the day before the update, so I know what should be here.... But yet, instead of my very nice extreme hills, I find a sweet potato colored mess of a mesa.
Plus, I also found what may be the shallowest coral reef ever recorded, as behind a village I have spent time in prior to the update, I somehow managed to find a warm ocean biome, completely landlocked, with the most pleasant coral reef having become a part of it upon generation. Yep, shallowest point was a mere 1 block deep, take that oceanology, I found the world's shallowest coral reef.
Anyways, lucky I made that copy of the world, so hopefully this can be fixed and I can resort to using to previous incarnation of this world and get back to my pixelated existence.
Included you will find a screenshot of me standing on the exact spot where my extreme hills biome should be, so, enjoy?
Rockatoa, Brickticks out!
_______________________________________
Copied from MCPE-149771
Reproduce (requires a Windows PC or iPadOS/iOS device)
Create a world in the Minecraft version 1.17.41 or earlier, but not before 1.17.0.
Load all chunks within your render distance, preferably wait a couple of seconds and maybe even a minute so that your chunks load properly in all directions.
Exit the world and load it into version 1.18.0.
Notice that some chunks which are a little bit further away from you, have not been touched yet still visible, are replaced by 1.18.0 terrain generation.
Expected Results
Loaded chunks should not reset when upgrading to 1.18.0.
Linked issues
is duplicated by 12
relates to 4
MCPE-169059
Ghost chunks render from seed data
Reopened
MCPE-175332
Discontinuity between chunks generated in 1.20.30 and 1.20.15, where terrain blending should not be necessary
Resolved
MCPE-186928
Chunks in all dimensions have their biome replaced with an Ocean biome upon reloading in updated older worlds created prior to <1.17.40
Resolved
MCPE-150757
Chunks voided or reset to new generation
Resolved
Attachments
Comments 14
OK, how do I do that? I've tried making a copy of the world file manually, but it keeps saying I don't have permission to move or duplicate the file.... So, erm, what should I do, and how should I do it?
Use the Export button in the world settings, at the bottom of the Game settings, to create a .mcworld file. If it's less than 10 MB, you can attach it to this report. Otherwise, you can upload it to OneDrive and create a sharing link for us to use to download it.
--I have also had a problem like this, and MCPE-149771 describes what might be another example. What might be happening is that no mining or building was ever done in the replaced chunks, so they were considered unmodified chunks and were never written to the world save. Now that world generation has changed, they're still unmodified chunks but now the world generates them differently. There may also be a dependency on the replaced chunks having been first loaded prior to release 1.16. Does that explanation fit your world too?--
Update: I have since learned that the problem I described above is not valid as evidence of a bug, because it only occurred in chunks that I had pruned out of the world in 1.17 using a third-party editor. Mojang can't be responsible for knowing what third-party software did to the world save and therefore can't support the modified world.
Alrighty then, here you go! First up, the current version, post 1.18.
https://1drv.ms/u/s!AgdPqwZh1adghAS9wBvGdD3gu-Qc?e=3CcgRF
And second, here's the copy of the world from 1.17.1 that was made upon being prompted to do so when first opening the world in 1.18...
https://1drv.ms/u/s!AgdPqwZh1adghAVADgiQqTYguMrt?e=o2HfuW
So, let me know if there is anything else, and I'll see what I can do, Rockatoa, a hoping for a quick fix Brickticks out!
P.S. Here's another version of the same world, last played in 1.17.1, it's in creative mode, but uses the same world seed and was created in the same version as the ones above, you know, just in case it helps...
Thanks for providing the example worlds. Could you please confirm whether the worlds have been edited using a third party editor at any point?
Additionally, this might be just that the chunks weren't saved beforehand (because they had not been built in) - if this is the case it might be working as intended.
After the most recent update an underwater monument and a nether fortress moved location in one of my world's. Before the update the nether fortress was at 176, ?, -112. But after the update it was at 384, ?, 272...
I don't remember the precise coordinates for the monument, but it's moved over 800 blocks away, at least.
Ps. I collected blaze rods from the previous fortress only to find that when I went to return to get more it'd moved...
@unknown: The presence of "?" instead of a Y coordinate tells me you took this from the output of a /locate command. Release 1.18 completely replaces world generation, including how the locations of generated structures are calculated from the world seed. The /locate command uses this same calculation and therefore also gives different results in 1.18 than it did in 1.17 with the Caves & Cliffs Experiments toggle turned off. You can no longer use /locate to find the positions of structures that were generated before 1.18. Furthermore, the command may tell you a structure is at some location when in fact there's no structure or a different structure there, because the chunks were already generated in 1.17 using the older style world generation.
Although these consequences are undesirable, they cannot be helped and cannot be described as a bug. The only way to prevent this from happening would be to never change world generation, which would mean we could never have new biomes or structures added to the game.
So, any ETA on when this might be fixed, or should I just keep waiting?
Reply from @unknown:
Please read our guidelines. The bug tracker is not a customer service site and does not get status information from Mojang. Our purpose is just to collect bug information for them.
Comments are meant for providing additional information for the devs. Any other use is off topic and subject to removal.
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – Feature Requests and Suggestions
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Please provide copies of the world from before and after the update.