Dazzgracefulmoon Posted August 6, 2015 Share Posted August 6, 2015 I was revisiting LEGO Worlds after I remembered that they put in the first content patch, only to find that one of my worlds (not the important one with all my stuff) Was super messed up, it acted and looked very similar to how Minecraft handles new chunks in an already existing world. Here's a gallery of the intresting generations I found. http://imgur.com/a/PTzZ5 Interestingly enough, I backed up 2 worlds and then tried them out in the new update, nothing was wrong with them. . . Link to comment Share on other sites More sharing options...
lol username Posted August 6, 2015 Share Posted August 6, 2015 It only saves chunks you've modified, and sometimes other chunks loaded around the player under somewhat unconfirmed circumstances (Will initially thought it was upon leaving a world, but I noticed many more new chunk files being saved when loading into a world - but nobody's really done conclusive testing to figure it out AFAIK). The rest are re-generated as needed, as just saving everything would totally swamp your hard drive. I wanted to entirely preserve a certain area, so I just went around it and re-loaded the world from various locations to catch everything around me. That place is now taking up 844 MB, so I'm pretty sure I've got it covered. Link to comment Share on other sites More sharing options...
Dazzgracefulmoon Posted August 6, 2015 Author Share Posted August 6, 2015 That explains quite a bit, which makes sense as to why the other two worlds were barely affected because they had alot of man-made buildings around them. Link to comment Share on other sites More sharing options...
Recommended Posts