Repairing a corrupt savegame or worldmap: Difference between revisions

From Vintage Story Wiki
(Added Navbox)
Tags: Mobile edit Mobile web edit
No edit summary
Line 6: Line 6:
2. Make yourself a bit familiar with the [https://sqlite.org/cli.html sqlite client tools]<br>
2. Make yourself a bit familiar with the [https://sqlite.org/cli.html sqlite client tools]<br>
2. Set up a environment path or paste in your broken savegame right besides the sqlite binaries.<br>
2. Set up a environment path or paste in your broken savegame right besides the sqlite binaries.<br>
3. Run the command <code>sqlite3 broken.vcdbs ".recover" | sqlite3 repaired.vcbds</code>, replace "broken.vcdbs" with your actual savegame name. This will try to fix any corrupted chunks.
3. Run the command <code>sqlite3 broken.vcdbs ".recover" | sqlite3 repaired.vcdbs</code>, replace "broken.vcdbs" with your actual savegame name. This will try to fix any corrupted chunks.


===If you get an exception in Entity.FromBytes()===
===If you get an exception in Entity.FromBytes()===

Revision as of 19:04, 3 June 2022

If you get any kind of SQLiteException

This means a chunk or other part of your game world has gone corrupt, but you can probably still save most of it.

1. Download sqlite
2. Make yourself a bit familiar with the sqlite client tools
2. Set up a environment path or paste in your broken savegame right besides the sqlite binaries.
3. Run the command sqlite3 broken.vcdbs ".recover" | sqlite3 repaired.vcdbs, replace "broken.vcdbs" with your actual savegame name. This will try to fix any corrupted chunks.

If you get an exception in Entity.FromBytes()

This means one of the world creatures or other types of entities have gone corrupt. This can be repaired from within the game

Run the savegame in repair mode, fly to where the game crashes, then save again and start normally.

If you get completely black chunks

This means the lighting step of a chunk did not fully complete. You can fix these chunks manually by walking/flying into them and running the command /debug cr


{{{title}}}