How do I move my V Rising world to my HavoNode server?

A V Rising world is one folder of autosaves. Upload it to Saves/v4/ on your HavoNode server, set SaveName to the folder’s name, and empty GameSettingsPreset so the world keeps the rules it was played with. Everyone gets their own vampire back when they join from the same account.

Check the version first

V Rising 1.1 keeps its saves in a folder called v4. Version 1.0 used v3. A world in a v3 folder is from 1.0, and Stunlock says 1.1’s content needs a new save: an old world only carries on with the 1.0 version of the server. Our servers run the current version, so open a ticket before you upload a v3 world.

From your own PC

If you played the world as a private game, hosted from your own copy of V Rising:

1. In V Rising, open Load Game, pick the world and choose Go to Directory. Its folder opens. The folder has a long random name, such as db4b1c0e-2b7d-430a-87ef-4b6c09398dcf.
2. Copy the whole folder somewhere safe before you touch anything, so you always have the original.
3. In your copy, you can delete ServerHostSettings.json, because your server has its own name and password. You can also delete every AutoSave_ file except the newest, since that’s the one that loads.
4. Rename the folder to something short, like ourworld, using letters and numbers only.

Keep the world’s own ServerGameSettings.json in the folder. Those are the rules you played with.

From another host

1. Stop the old server, so its last save is complete.
2. Download its world folder from Saves/v4/. The folder’s name is the old server’s SaveName.
3. Download its Settings folder too. It holds adminlist.txt, banlist.txt and any ServerGameSettings.json you’d set up there.

Upload it

1. Download a backup from your Game Panel first.
2. Stop your HavoNode server from the Game Panel.
3. In your Game Panel’s file manager, open Saves, then v4, and upload the world folder there. Keep the folder’s name exactly as it is.
4. Set SaveName to that name, in your server’s settings in the Game Panel or in ServerHostSettings.json in the Settings folder.
5. Set GameSettingsPreset to "" (empty) in the same place, so a preset doesn’t load in place of the world’s own rules.
6. Coming from another host? Upload its adminlist.txt, banlist.txt and ServerGameSettings.json into your Settings folder. Coming from your PC? Make sure there’s no ServerGameSettings.json of your own in Settings, so the world plays exactly as it did.
7. Start your server and join.

If you join and find a brand new world, check SaveName first. It has to match the folder in Saves/v4/ exactly. Your upload is still there, so fix the name and restart.

Afterwards, on your PC

Once the world’s running on your server, Stunlock suggests removing it from Load Game on your PC, so the same world doesn’t show up twice. If it’s a Cloud save, delete it from inside V Rising. Delete the folder by hand and Steam Cloud puts it back the next time you start the game.

Characters come with the world

Each player’s vampire is saved in the world and tied to their Steam account, so everyone picks up where they left off by joining from the same account. Stunlock doesn’t support moving one character on its own between different worlds.

If the newest save won’t load

If the server crashes loading the world, or players get “Error: Server Error” when they reconnect, Stunlock says the newest autosave is probably damaged. Download a backup from your Game Panel first, stop the server, and move the AutoSave_ file with the highest number out of the world folder. The server then loads the one before it. You lose the progress since that save, so keep the moved file until you’re sure.