Yesterday me and my friend were playing on a LAN world and i had left it for about 15 minutes running both of us afk. I came back to it and I thought it had crashed but i was able to get into the pause screen and close it after a hot minute.
However when i came back to it this afternoon alone i noticed the terrain seemed a bit strange so i went into creative to see a bunch of new chunks loaded on top of the old chunks in a grid. it was originally a stone mountain area. i showed it to one of my other buddies and we're both completely baffled by this. It seems to only affect the area i re-spawned in. the further i traveled out it seemed to be the normal terrain. The initial setting i had was 7 chunks for render distance but i don't think that really has much to do with anything? might affect the amount of area this was but i dont think thats exactly the case. its perfectly playable nonetheless besides all the strange mis-matched chunks in that area.
Related issues
Attachments
Comments
migrated
migrated
i want to add i just counted the chunks from my spawnpoint to the edge of the bugged area and its exactly 7 chunks so render distance is definitely a factor in this.
violine1101
Can you attach the game logs from when this happened? Also the log from when you played in the world previously would be good to have.
In which versions did you play the world? Only in 1.15-pre6, or also in previous versions? Did you open the world in 1.14.4?
This issue has been temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
migrated
https://paste.ubuntu.com/p/yWptXtpTJk/
log the day we played on the world
https://paste.ubuntu.com/p/WsnjsHdnFQ/
log from day after initially playing and chunks courrupted
as far as i can recall we only played on 1.15 pre release-6Â
 i do hope this helps clear up the issue.
violine1101
Thanks! We're tracking corruption issues like this in a single ticket (MC-161823), so your ticket has been resolved as a duplicate. Your information will be very valuable.
migrated
this issue is in 1.15 im not sure if its in 1.15.1 havent tested i made a new bug thread