A V Rising server on a VPS: Windows, settings and a daily restart
The V Rising dedicated server is free, and anyone can download it, even without buying the game. But one limitation decides your choice of plan: the server is released for Windows only. The developers say so plainly in the official guide. People run it on Linux through Wine, but that is a community workaround, and after a game update such a server may simply refuse to start. If you want a reliable server without the fuss, take a Windows VPS and count on the system taking 2–3 GB of memory from the start.
Which plan your group needs
Load in V Rising grows less with the number of players than with the number of castles. Every castle is hundreds of blocks, servants, workstations, storage and prisoners, and the server keeps simulating them even when the owner is offline. After a couple of weeks of active play a server holds a dozen castles, and it needs noticeably more memory than on day one.
- A group of up to 10 people. 4 cores and 8 GB of memory. Even with Windows that leaves headroom for co-op or a small PvP server.
- A community of 20–40 players. 4–6 cores and 16 GB. A big server has many clans and castles, and during raid hours all of that load lands at the same time.
- More than 40 players. Technically the server supports up to 128 people, but that takes a fast high-clock processor and spare memory. Have a look at the high-frequency VPS selection.
The server is built on Unity, and the main simulation runs in one thread, so core speed affects smoothness more than the core count does. When the server runs short of power, players notice it in combat: abilities fire late, enemies slide around, and a castle siege turns into a lottery.
Installation and ports
The server is installed through SteamCMD as app 1829350 with an anonymous login. To update it, run the same command again while the server is stopped. Don't just launch VRisingServer.exe on its own: without parameters it starts with default settings. The folder contains an example script, start_server_example.bat. Copy it under a different name, because the original file is overwritten on updates.
Always set the -persistentDataPath parameter to a dedicated folder. The server puts its settings and saves there, and you will know exactly what to back up. Without it everything ends up deep inside the Windows user profile.
Ports are set in the settings. In the default file they are 9876/UDP for the game and 9877/UDP for the Steam server list. If you want the server to show up in the public list, open both in the Windows firewall. For connecting by direct address the game port alone is enough. RCON for remote management is off by default. If you turn it on, open port 25575/TCP to your own IP only.
Two settings files
The settings are split between two files in the Settings folder. ServerHostSettings.json covers the server itself: name, password, the player limit MaxConnectedUsers, ports and autosaves. ServerGameSettings.json covers the rules of the game: PvP or PvE, siege times, gathering rates, castle limits and clan size. Leave the default files in the StreamingAssets folder alone, since updates overwrite them too. Put your own copies in the settings folder, and list only the parameters you actually changed.
Limiting castles per player and clan size is the easiest way to keep the load in check on a big server. Fewer castles means fewer objects for the server to hold in memory.
Restarts and backups
The developers recommend restarting the server every day, during the hours with the fewest players online. A restart frees memory that has piled up and installs updates at the same time. On Windows it is easy to schedule with Task Scheduler.
Saves live in the Saves folder inside your persistentDataPath. The server makes autosaves itself and keeps the last few. The AutoSaveSmartKeep parameter lets you keep not just the newest copies but also ones that are an hour, a day or more old. That saves you when a mistake in the settings goes unnoticed for a while. Still, copy the folder off the VPS once a day. You can also bring your own world from your computer: copy the save folder into Saves/v4 on the server and put its name in -saveName.
Where to put the server and whether you need protection
V Rising has fast combat, and you feel the ping. For a group in Europe, a server in Germany or the Netherlands keeps most players well under 40 ms. North American players should pick a data centre on their own side of the ocean: a transatlantic connection adds around 80–100 ms, which is fine for PvE but noticeable in PvP. If part of your group plays from Russia or the CIS, Finland gives them a short route without hurting players in Western Europe much. You can compare locations on the VPS in Europe and VPS in the USA pages. Open servers in the public list sometimes get attacked, and players don't forgive a disconnect in the middle of a siege, so for an open server take a plan with DDoS protection.