[Experimental] Loading world (created before 1.17.20.23) creates a huge mountain at the exit site
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld
- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
Loaded, the nearest area will be turned into a mountain.
And also the bedrock will be raised.
Expected results:
The generation of loaded chunks should not change.
Image:
Linked Issues
is duplicated by9
MCPE-139715Y Level ElevatedDuplicateMCPE-139722Generation errorDuplicateMCPE-139742World corruption when loading pre 1.17.30.23 worldsDuplicateMCPE-139785Among the worlds run before 1.17.30.22, the world map with the experimental function turned on has an error terrain.DuplicateMCPE-139796World corruptionDuplicateMCPE-139838Importing world height bugDuplicateMCPE-140024Floating Water & Chunk ChangingDuplicateMCPE-140042New chunk World Generation breaking world...DuplicateMCPE-140182I enabled Molnag in my creative world and for some reason my entire world with its chuck move likr 50 blocks upwards and all my villagers died :( new chucks generated normlsy thoDuplicate
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
Created Issue:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Attachments1
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
The submerged nearby area will turn into a mountain.
Expected results:
The generation of loaded chunks should not change.
Image:
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
The submerged nearby area will turn into a mountain.
Expected results:
The generation of loaded chunks should not change.
Image:
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
The submerged nearby area will turn into a mountain.
And also the bedrock will be raised.Expected results:
The generation of loaded chunks should not change.
Image:
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
The submergednearbyarea will turn into a mountain.
And also the bedrock will be raised.Expected results:
The generation of loaded chunks should not change.
Image:
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
Loaded, the nearest area will be turned into a mountain.
And also the bedrock will be raised.Expected results:
The generation of loaded chunks should not change.
Image:
![[MCPE Mod] Dr.Awesome4333](../../../data/assets/gravatar/drawesome4333.png){kind=small}
relates to
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site[Experimental] Loading world (created before 1.17.20.23) creates a huge mountain at the exit site
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
- Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23) MCPE-139669.mcworld- Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
Loaded, the nearest area will be turned into a mountain.
And also the bedrock will be raised.Expected results:
The generation of loaded chunks should not change.
Image:
is duplicated by
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're actually already tracking this issue at MCPE-139669, so we will resolve and link this ticket 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:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
![[Helper] lillybeacon](../../../data/avatars/users/93893.png){kind=small}
Parker S The screenshot you're referring to is MCPE-139669
Thank you for your report!
We're tracking this issue in MCPE-139669, 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
The screenshot clearly shows version 1.17.30.24.
And I think this is true information. And this happens due to an attempt to return the raised chunks to their place. Apparently there was an error and worlds that have not actually undergone changes associated with version 1.17.30.23 anyway "return" the chunks to their place (to -64 height). After the test MCPE-139669 in version 1.17.30.24 I was unable to reproduce the error, and the old world returned whole chunks to their place.
https://bugs.mojang.com/browse/MCPE-139669?focusedCommentId=1065427&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1065427
I can provide the world if needed for testing.
Welcome234, the overworld issue in that video looks very like MCPE-139669, where a world created before 1.17.30.23 is converted to a 1.17.30.23 Caves and Cliffs world and unexplored chunks are raised.
I couldn't see gaps into the void as present in the nether on the current beta or below y = 1 on 1.17.30.23 overworlds (MCPE-139665).
Alas, due to MCPE-139669, you will no longer be able to completely fix this world. These chunks will not be returned to their place, since the loaded areas can no longer be changed (incomplete chunks) (full chunks were returned to their place). If you can reproduce the problem again in version 1.17.30.25 - add reproduction steps (reproduce in a world where the chunk bug has not happened before).
And this bug happened for the first time in version 1.17.30.23. I'm right?
Confirmed.
In my case I used an old world from 2017 and then upgraded it to 1.17.20.23 and then 1.17.30.23
Original bedrock level of the world has been raised to 64, 1.17.20.23's bedrock extends from 0 to 64. Void exists in previously (2017 and 1.17.20.23) generated chunks that have been modified (ex mined a block) in some way modified from -64 to 0. Un touched but previously generated chunks are over written with new (but correct) genration except when near a previously modified chunck.
However this does not affect a world from 2017 directly upgraded to caves and cliffs in 1.17.30.23.
I’ve found a cinematic example of this issue. I agree that it shouldn’t be like this, but I have to admit that it does look cool sometimes…
Experience this as well. My partner and I have a world we just traveled to find an ocean monument in. Weve had the experimental features on all year so it's gone through each update. This most recent well the outcome is extreme as the surrounding chunks along the entire journeys path have done this. The oceans are especially frustrating. Hoping this is a quick and easy fix for Mojang and we can continue on our unopened just in case copy of the world. Otherwise sadly this has killed it and we will need a new one 😨
Are anyone still having this issue in the 1.17.30.24?
I don't have this problem anymore.
in my old world, the full central chunks returned to their place, but the edges, alas, remained in place. I think the problem is solved and in version 1.17.30.24 it cannot be reproduced!