Move a Solo Save to a V Rising Dedicated Server

Find the session and duplicate it

In game, open Load Game, select the session and choose Go to Directory. The instructions also give these Windows roots:

%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRising\CloudSaves\<SteamID>\

or %USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRising\Saves\

On 1.1, inside that tree: a v4 directory, then a folder such as db4b1c0e-2b7d-430a-87ef-4b6c09398dcf. It holds AutoSave_#.save.gz files, ServerGameSettings.json, ServerHostSettings.json, SessionId.json and StartDate.json.

Copy the whole GUID folder before you delete anything from it. If the move fails, the original still has to exist.

You can drop ServerHostSettings.json from the copy when the dedicated server already has its name, password and ports, in a file or on the command line. You can keep only the latest AutoSave_#, or keep them all. The latest is the one that loads. Rename the GUID folder to a simple directory name.

Put it where the dedicated server reads

By default the dedicated server writes to:

%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\Saves

With -persistentDataPath, Saves is a subdirectory of that path. The session goes in Saves/v4/, next to other 1.1 worlds.

Start with -saveName set to the folder name you copied. Clear GameSettingsPreset so a StandardPvP preset does not replace the session's rules. Do not add a ServerGameSettings.json in the override Settings folder. The instructions say that file would win over the one stored with the save. The ServerGameSettings.json that matters is the one inside the save folder.

If cloud saves are on, remove the local session from Load Game while the game is running. Deleting it in Explorer with the game closed can make cloud sync restore it on the next launch.

Check it, and what a rename will not fix

Leave the solo machine intact. On the dedicated server you should see the castle, inventory and servants you know. Make one harmless change, shut the process down normally, then restart and check that the change survived. An empty world means the wrong -saveName, the wrong -persistentDataPath, or a folder still under v3 while the binary is 1.1.

A save newer than the client or the server can fail to load. Match versions before you call the copy corrupt. To go back: stop the dedicated server, restore the previous Saves folder, and keep playing the original solo session until you have deleted it from the menu on purpose.

Autosaves and updates: maintenance guide. Offers: V Rising comparison.

Questions