Web Analytics Made Easy - Statcounter
Server Tools

Tools / V Rising

V Rising Save Handoff

Moving a V Rising world onto a dedicated server? Two things quietly break it: bringing all your old autosaves (the server only loads the newest, the rest just bloat it) and copying your old ServerHostSettings.json over the server's own. Point this page at your save folder: it keeps only the newest autosave, drops ServerHostSettings.json, preserves the exact SaveName folder so the server loads your world instead of soft-wiping, and packages a clean, ready-to-drop bundle.

Your save never leaves your browser. It reads only file names, sizes and modified-times, builds the handoff zip locally from your own files, and never modifies your original save.

Your save never leaves your browser Reads names, sizes & times only Copies files - originals untouched

Pick your save folder

A dedicated server keeps saves in VRisingDedicatedServer\save-data\Saves\v3\; solo saves live under %APPDATA%\..\LocalLow\Stunlock Studios\VRising\Saves\v3\. Pick the long-named SaveName folder (with the AutoSave_*.save.gz files) or its Saves/v3/ parent. Stop the server first.

Want this on a real server? Supercraft hosts V Rising →

What a clean V Rising handoff needs

A V Rising world is a folder named with a long SaveName under Saves/v3/, holding AutoSave_<n>.save.gz files plus StartingCompressedSave, ServerGameSettings.json, SessionId.json, StartDate.json and ServerHostSettings.json. Two rules make a handoff clean:

  • Only the newest autosave. The server loads the latest; older ones are dead weight and can confuse a manual copy. This keeps the highest-numbered one and drops the rest.
  • Leave the host settings behind. On a server that's already set up, your old ServerHostSettings.json would overwrite its password, name and rules - so it's dropped by default (with a checkbox to keep it for a brand-new server).

Setting the server's rules? Build a ServerGameSettings.json with the Rules Studio. Prefer it hosted with backups? Run a V Rising server with Supercraft.

Manual handoff (no JavaScript needed)

  1. Stop the target server.
  2. In your world's SaveName folder, delete every AutoSave_*.save.gz except the highest-numbered one.
  3. Delete ServerHostSettings.json from the copy (unless the server is brand new).
  4. Copy the whole SaveName folder into the server's save-data\Saves\v3\.
  5. Set SaveName in the server's ServerHostSettings.json to that folder's name, and start the server.

FAQ

Is my save really not uploaded?

Really - there's no upload endpoint on this page. Reading the folder and building the handoff zip both happen in your browser; the network tab shows zero requests carrying your save.

Which SaveName do I set on the server?

The folder name the tool shows (and names the bundle after). Put that exact value in the server's ServerHostSettings.json SaveName field so it loads your world instead of creating a new one.

Will I lose progress by dropping old autosaves?

No - the newest autosave is the current state of the world; the older ones are just previous snapshots. Keep your original folder as a backup until the server loads the world.