I have a Realms world that the bedrock was not replaced on at all in already generated chunks. I have a copy of this world as creative (for building/designing purposes) that is not on Realms and the bedrock was replaced after the 1.18.2 hotfix. The hotfix has not fixed the Realms world, or any download of the Realms to create a new copy either.
Attachments
Comments 9
The world and Realm are updated to 1.18.2, I verified after I downloaded a saved copy of the Realm to be sure. The are both 1.18.2 as of the hotfix, and the world was updated prior to that as well. This was a previously 1.17 Realm, so no the hotfix did not fix this for all worlds or even realms despite being marked as Fixed.
The creative copy of the realm downloaded before the 1.18.2 Hotfix and the update to 1.18 (a pure 1.17 world initially, updated to 1.18.2 when I decided to verify if this was honestly an issue still given it was previously marked Fixed) That world actually DOES have the replaced bedrock (I traveled to the same coordinates I was in in my Realm to make sure, those chunks were already generated when I made the creative copy), but anything downloaded post 1.18 and 1.18.2 does not. This information was actually in my original comment, although I did not state the creative copy of my Realm was originally 1.17 before I updated it.
I'm trying to clarify what the sequences were that worked and didn't. Here's what I think you are saying:
Update directly from 1.17.x to 1.18.2 works.
Update from 1.17.x to 1.18.0 (prior to fix of MCPE-149251) and then to 1.18.2 does not work when the update happened on a realm, but does work when the update happens locally.
If you meant something different, or if there is some other sequence that works or doesn't please briefly describe that.
I didn't actually play when the Realms were updated to 1.18. My Minecraft automatically updates, and my Realms automatically follow that–literally it locks me out of my Realm until a day after my Minecraft has been updated. I logged in to find out the 1.18.2 Hotfix was already a thing, and already downloaded. I haven't really had time to play after 1.18 dropped.
So as far as I know the Realm went from 1.17 to 1.18 to 1.18.2, but I didn't actually see it at the state of 1.18.
The world copy that was downloaded prior to 1.18 and was not on the Realm prompted me to update when I went to load and verify, and it updated directly from 1.17 to 1.18.2 and was fine. The world copy I downloaded from my Realms (most current copy of my Realm) after the 1.18.2 update did not prompt me to update the world so I know it was updated to the latest update, and that world still has Bedrock.
So to summarize:
Realm - World started with 1.17, possibly updated to 1.18 through auto-update did not play on realm at this time, updated to 1.18.2 through auto-update and world still had Bedrock when loaded in
Downloaded World Save from Realm after 1.18.2 update - 1.18.2 still has Bedrock
Downloaded World Save from Realm prior to 1.18 update - 1.17 updated to 1.18.2 Bedrock replaced with Deepslate
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I've added another screenshot that shows how far I had to travel in a rather straight line before I hit new generation. You can see the beginnings of a bedrock wall where I finally began to drop below level 0.
If possible, could you please export and attach the world in which you are experiencing the issue?
This ticket will automatically reopen when you reply.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Had you already updated the world to 1.18.0 or 1.18.1 (by playing in the realm)?
MCPE-149251 was reported for those versions, and is resolved as Fixed. However, it may be that worlds that did not get bedrock replaced with deepslate in the original 1.18 update from 1.17 are not yet being updated when going from 1.18.1 to 1.18.2.
It might also be helpful to know if you download a realm backup from before the 1.18.2 hotfix and then opened locally will replace the bedrock with deepslate.
This report has been temporarily closed as Awaiting Response. It will automatically reopen when you comment with new information. Please be sure to provide all requested information. Reports that do not contain enough information may be closed as Incomplete.