Manage Saves

V Rising: Uploading & Migrating Worlds

Transferring a V Rising world from your local PC to a dedicated server is tricky because the game uses a Session ID (GUID) system. If you just copy the save file, the server might create a new "Session" and treat your world as empty, or force you to create a new character.

How to Upload a Save Correctly

1. Locate your Local Save: Navigate to the folder mentioned above. You will see a folder with a random UUID name (e.g., 5a4f-2b1d...).
2. Prepare the Files: Inside that folder, you should see many AutoSave_X.save.gz files and a SessionId.json.
3. Access the Server: Open your Supercraft File Manager.
4. Navigate: Go to /save-data/Saves/v3/world1/ (or whatever your server save name is).
5. Clear & Upload:
   • Delete the existing contents of the server folder.
   • Upload your SessionId.json.
   • Upload your latest autosave (e.g., AutoSave_25.save.gz).
6. Rename (Critical): Check the server's documentation. Usually, the server loads the highest numbered autosave, or you might need to rename your file to match the naming convention exactly.
7. Restart the Server.

The free V Rising Save Handoff tool does this preparation for you in the browser: point it at your local save folder and it finds the world, keeps only the newest autosave (the server loads the latest), preserves SessionId.json and the save-folder name so you avoid the soft wipe, leaves out ServerHostSettings.json so it cannot overwrite an already-configured server, and packages a clean ready-to-drop bundle with a README naming the save name to set. Nothing is uploaded and your originals are untouched.

Troubleshooting "Empty World"

If you join and the world is blank or asks you to create a character:

• Wrong Folder: You might have uploaded the files to /Saves/v3/ root instead of /Saves/v3/world1/.
• New Session: You didn't upload SessionId.json, so the server generated a new one, breaking the link to your character data.

Keep your vampire legacy alive. View plans.