Stunlock Studios published patch 1.1.1 on May 13, 2026 and its reviewed PC dedicated-server instructions cover 1.1.x. The official dedicated server is a Windows application, available from Steam Tools or SteamCMD with App ID 1829350. Legacy 1.0 and Early Access saves are not compatible with 1.1. Use the appropriate legacy branch to continue older worlds.
Self-host or rent?
Self-hosting gives your group access to configuration JSON, network ports, admin accounts, saves, restart schedules and backups. Renting may be easier for a continuously running world. Compare current game version, full file access, backup download, ports, admin controls, and save uploads. Stunlock's featured hosting partner is one option, not a restriction preventing you from choosing another service.
Install the dedicated server
Find V Rising Dedicated Server under Steam's Tools section, or install it using SteamCMD:
steamcmd +force_install_dir "C:\VRisingServer" +login anonymous +app_update 1829350 validate +quitRun VRisingServer.exe. Copy and rename start_server_example.bat if you use it for a custom launch, as the distributed sample can be overwritten when updating.
Ports for V Rising
| Default port | Protocol | Purpose |
|---|---|---|
| 27015 | UDP | Game traffic |
| 27016 | UDP | Query and Steam browser |
| 25575 | TCP | Optional RCON |
Set game and query ports using Port and QueryPort in configuration, or the launch arguments -gamePort and -queryPort. Only open ports actually used by the running installation.
ServerHostSettings.json and ServerGameSettings.json
Hosting and gameplay rules are separated into ServerHostSettings.json and ServerGameSettings.json. Do not edit the bundled templates directly under VRisingServer_Data\StreamingAssets\Settings. Use overrides, by default under:
%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\SettingsFor persistent or multiple instances, Stunlock recommends -persistentDataPath; the selected directory then holds Settings and Saves. Keeping each instance separate also simplifies backups.
PvE and PvP settings
Start a private co-op server with a PvE preset unless your group wants clan raids and PvP-specific rules. Competitive or public servers benefit from clear policies for clans, castles, raids, resets and access. Back up both JSON configuration and world data before making substantial changes.
Administrator rights and optional RCON
On a PC dedicated server, administrators can be listed by Steam ID in adminlist.txt. Enable the in-game console before issuing administration commands. RCON is optional; use a strong password and targeted firewall access rather than exposing it broadly.
Back up a savegame
With -persistentDataPath, world files live under the chosen path's Saves folder. Otherwise the server uses its normal directory under AppData\LocalLow\Stunlock Studios\VRisingServer. Make separate copies rather than moving away the only existing world.
Move your world to another host
Stop the server and copy the complete world save and associated settings to the new hosting machine. Stunlock distinguishes such a server migration from transferring your character to an unrelated existing server: characters, equipment, castles and unlocked skills remain tied to their original server world.
What about 1.0 saves?
V Rising 1.1 does not accept old 1.0 and Early Access world saves directly. Stunlock provides legacy-1.0.x and other legacy Steam branches for continued access. For the 1.1 content, plan for a world compatible with 1.1.
Server not in the browser
A newly launched server can take several minutes to appear. You can use the external IP for direct connection as described by Stunlock. Check running process, patch version, game and query UDP ports, NAT and firewall.
Rubberbanding during saves
Stunlock also documents CompressSaveFiles. Disabling compression may speed up saving and reduce related pauses but consumes more storage. Back up your settings and save first.
For the co-op modes and platforms, see our V Rising game profile.