#Issues with chunk saving/loading in new update
1 messages · Page 1 of 1 (latest)
After some more testing, I think the issue definitely involves chunk saving.
Interestingly, the same exact chunks get reset if I make, save, and load a world with the same seed and noise parameters
After dozens of new Dig Deep world tests with the same seed and parameters, I have discovered the following:
- Saving/loading while far from, near, or even within a reset chunk will NOT prevent it from resetting.
- Placing or removing any block within the reset chunk WILL prevent it from resetting.
BTW, a "reset chunk" is any chunk that consistently deletes any trees within it upon loading a save (like in the images of the main post). I'm using trees as an easy way to detect chunks that are resetting to their default terrain as dictated by the world seed and noise parameters.
Hope this helps any devs trying to fix the issue!
Another weird thing I noticed: only trees that START in the affected chunk get reset. Trees that grow over into the chunk are just fine.
Uhh, one of the chunks that vanished a while ago just... came back? I already harvested the tree stumps from when the chunk vanished originally, so now I have a bunch of floating trees. I assume the chunk returned when I loaded the game.