Joshua Horrocks

What’s happening right now though is that obsidian forms on top of the stone that generates from lava flowing on top of water. It’s not exclusive to world generation. Pretty sure this happened as a result of MCPE-128022 being fixed.

Definitely isn’t resolved lol. Encountered this the other day.

Haven’t encountered this bug again, seems fixed to me!

Yeah, so… the bug’s back.

I just had to delete a copy of my world because it said it was corrupted and the current version of my world crashes on launch. 

I’ve still got the issue but it’s not as bad now.

Servertime spikes and FPS drops whenever I go to my old base but the games saves and stuff normally now.

Also a really weird thing with my armor, my Netherite Helmet is now invisible in my inventory and if I hit Y (Shift click) to take it off, it crashes the game instantly.

Preview 1.18.30.23 seems to have fixed my world…

I updated my Minecraft to Preview 1.18.30.23 and launched a copy of this world to see if anything had changed. The entities that got teleported to my new base are still there but I can interact with them now, I can load chunks normally again, the server time doesn’t spike anymore, the nether seems back to normal, et cetera. I managed to make it back to my old base through the nether, there was a bit of lag the closer I got to my old nether portal, it took a minute to load when I went through but my old base seems to be loading relatively normal now. The entities I suspected were teleported from my old base are still here so I suppose it actually duplicated them instead. My old base is lagging a bit more than it used to but it’s actually playable now. I’ve made a copy of my world in this new save in case the glitch happens again, but for now, it seems as I have my world back! If I find anything interesting while playing I’ll make sure to make another comment to update the current info on my world. So happy I can play on my world again!

EDIT:1

When I tried to save and quit it wouldn’t, I dashboarded and tried to load it again, it was doing the glitch again.

EDIT:2

I launched another copy of the world and everything seemed back to normal again, I saved and quit multiple times and it worked fine, it said “uploading world” instead of saving game though. I then tried traveling to my old base again and had the same experience (Kind of laggy closer I got). I saved and quit from my old base and now it says “Saving world” again and is taking a long time to save. It seems that the glitch has something to do with the chunks at my old base since it only starts glitching again once I travel to my old base.

EDIT:3

I let the world save and it took about 45 minutes. Once I relaunched it it seemed like it was struggling to load my old base but not nearly as bad as it was. I walked around my old base for a bit and then saved and quit, it went back to the “uploading world” screen and saved in normal time. I relaunched the world and it was doing the glitch again. I theorize that as long as I stay away from my old base the world should remain playable.

EDIT:4

I’ve let my old base load for an hour and a half while afk and it seems to be back to normal now. Or so I thought; As soon as I entered my old nether portal (overworld side) my game crashed. Every time I try to load that copy of the world my game crashes.

EDIT:5

I’ve been playing on a copy of my world for a couple hours today and it’s still loading normally. As far as I can tell my hypothesis was correct, as long as I stay away from the (what I believe to be corrupted) chunks of my old base (Overwold and Nether side), I can continue to play on this copy of my world normally. I’ll be making a copy of my world with each new update to check if a return to my old base will eventually be possible. For now though, I have to reacquire all the kinds of stuff I had stored at my old base lol.

EDIT:6

I went back to my old base today in the new update (1.18.30.27) and everything is loading normally again! I’ve traveled back a forth a couple of times, save and quit, restarted the game, et cetera, and everything seems back to normal! So based off of this I suppose the only current solution to this bug is to wait. Don’t play on your world for a while, let the beta continue to update, and it should eventually fix itself…