Chunk corruption: This was not the homecoming I was hoping for . . .

[Professor Dragon]

I'm looking for suggestions on how to continue from here.

I've got a very old world, which has been updated through multiple major versions.

For a long time, I have been moving south, but came back after 14 game years to complete the Resonance Archive. That went fine.

However, going back to my original main base, it is simply gone - along with all of the chunks around it. 

Running in "Repair mode" does not appear to change anything.

The best that I could do was fly in Spectator mode back to a part of the map where it was previously okay, and even though that now also had all missing chunks, exiting, running in Repair mode and coming back in appears to have made that region just fine.

I have the log set.

I don't know if there is any chance of recovering my previous main base area and farms. I am assuming it is gone?

Should I just attempt chunk regeneration? OR should I just walk away from this area and never come back? Practically speaking, apart from nostalgia, I probably don't need anything from this base or area. (Was going to pick up a supply of leather for a saddle, but will sort that another way.)

I could also put this to the Issue Tracker for help.

I don't know how to read the logs effectively.

client-debug.log:
18.11.2025 12:05:11 [Debug] MeshRef with vao id 17771 with 600 indices is leaking memory, missing call to Dispose. Set env var VAO_DEBUG_DISPOSE to get allocation trace.

client-main.log: Nothing obvious.

server-main.log: After waiting, did not seem to do anything.
18.11.2025 12:05:28 [Warning] Server overloaded. A tick took 3396ms to complete.

server-debug.log:
18.11.2025 09:58:39 [Debug] Found 3864 Item requiring remapping
18.11.2025 09:58:39 [Debug] Remapped 0 new Itemids
18.11.2025 09:58:39.249 [VerboseDebug] Remapped existing Itemids: 2416=>2, 2419=>3, 2421=>4, 2422=>5, 2423=>6, 2425=>7, 2=>8, 3=>9, 4=>10, 5=>11, 6=>12, 7=>13, 8=>14, 9=>15, 10=>16, . . . 
18.11.2025 09:59:07.879 [VerboseDebug] Done spawn chunk

The visible green part in the map at top right is all that remains in this area. You cannot leave this area in Creatie mode - you need to enter Spectator mode to be able to fly out.
The rest of the world does not exist at this point - you need to fly to an "existing" chunk, log out, repair mode, come back in and then that chunk is fine. This lot is all still missing though.

Thoughts appreciated. Thanks, Professor Dragon.

 

 

 

 

 

Edited November 18, 2025 by Professor Dragon

[LadyWYT]

Honestly, with it being a very old world, I would submit it to the issue tracker. 

58 minutes ago, Professor Dragon said:

Should I just attempt chunk regeneration? OR should I just walk away from this area and never come back? Practically speaking, apart from nostalgia, I probably don't need anything from this base or area. (Was going to pick up a supply of leather for a saddle, but will sort that another way.)

If you can manage to repair the chunks even a little at a time(it sounds like you've managed to do this?), an alternate solution is to repair only the chunks you care most about, save the builds as blueprints(or however this happens via worldedit), and then import the builds into a brand new world. For items, make a list of the important stuff on paper, and then use creative to give it all back.

Unfortunately, it's not a solution that preserves the world, but worst case scenario, it should allow you to at least preserve the builds.

[Professor Dragon]

4 hours ago, LadyWYT said:

If you can manage to repair the chunks even a little at a time

Thanks LadyWYT. 

Unfortunately, the repair did nothing - not even replace the missing chunks with default world gen chunks.

I will put this to the Issue Tracker and see what they say. 

It is not super important, besides nostalgia really. It was my first real base where I started out, and I was keen to see the transition between "then and now," 1,000 hours on. The only fragment that escaped unharmed had dirt walls with glass panes in them.  And the farm fields had one water source at an end, rather than placed as still water. So I can see I've moved a long way.

I do have my original Save game from that point, not that I suppose that helps.

I was going to use it as a jumping off point to Story 2, because everything seems to generate based off a distance from world spawn, rather than my current spawn (Hmmm. I probably could have reset world spawn if I had thought about it, before asking for directions . . . ).

In practical terms, I'm regrouping, building up a new "northern base" from which to launch story forays, and will chalk this one up to "instability from the Rust World seeping through." Worst case, I can try rebuilding whole chunks just to patch that area - although I'm not sure how far it extends, as there was nothing to see in any direction.

Professor Dragon.

EDIT
Logged to:
https://github.com/anegostudios/VintageStory-Issues/issues/7540

Edited November 18, 2025 by Professor Dragon

[LadyWYT]

I see.  Hopefully the devs can help figure out a way to save the world, but at the very least, it's probably useful data to have on their end in regards to what can happen to worlds that span multiple updates. 

[Maelstrom]

What version was the world created in?

[Professor Dragon]

1 hour ago, Maelstrom said:

What version was the world created in?

Ooops. Forgot to include that here. 

v1.16.4.

[Maelstrom]

That's not surprising actually.   I recall Tyron cautioned tht shenanigans would likely happen in the 1.19 world gen revamp.