V Rising Dedicated Server Setup (Linux + Wine)
This guide walks through standing up a V Rising dedicated server on Linux. V Rising's dedicated server is currently distributed as a Windows binary only (Steam app 1829350) — there is no native Linux build. Linux hosts run the server through Wine, a one-time install per host.
Windows binary, runs through Wine: When pulling with SteamCMD on Linux, force the platform to Windows so the right binaries download. Then run the server under Wine. Most managed hosts wrap this in their automation; self-hosted Linux requires installing Wine first.
Step 1: Install Wine and SteamCMD
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install -y wine wine32 wine64 winetricks steamcmdVerify Wine is working: wine --version should print a version string.
Step 2: Pull the V Rising Server (Force Windows Platform)
steamcmd +@sSteamCmdForcePlatformType windows \
+force_install_dir /home/steam/V-Rising-Server \
+login anonymous \
+app_update 1829350 validate \
+quitThe +@sSteamCmdForcePlatformType windows flag is critical — without it, SteamCMD on Linux either fails or installs the wrong platform's files. Set it before +force_install_dir.
Step 3: Configure ServerHostSettings.json + ServerGameSettings.json
Both config files live in /home/steam/V-Rising-Server/VRisingServer_Data/StreamingAssets/Settings/:
ServerHostSettings.json— server name, password, ports, slot count, save settings, public visibilityServerGameSettings.json— game-rule settings: difficulty, day/night cycle, decay rates, PvP rules, blood quality, etc.
Server name, port, and password live in HostSettings. Game-rule tuning lives in GameSettings. Edit before first launch.
Step 4: Open Required Ports
| Port | Protocol | Purpose |
|---|---|---|
| 9876 | UDP + TCP | Game traffic |
| 9877 | UDP + TCP | Steam query |
If hosting multiple V Rising servers, increment by at least 2.
Step 5: Launch the Server
Headless Linux hosts typically need a virtual display (xvfb-run) for the Wine-wrapped binary:
cd /home/steam/V-Rising-Server
xvfb-run wine VRisingServer.exe -persistentDataPath ./save-data -serverName "My V Rising Server" -saveName "world1" -logFile "./logs/VRisingServer.log"Common launch flags:
| Flag | Purpose |
|---|---|
-persistentDataPath | Where the server stores save data + settings |
-serverName | Display name (alternative to setting in HostSettings.json) |
-saveName | Save folder name — supports running multiple worlds with different names |
-logFile | Where to write logs |
First Boot Verification
- Watch the log for
Loading [save name]followed byServer started. - The server should appear in the V Rising in-game browser (filter by your server name) if visibility in HostSettings.json is public.
- Connect via in-game browser or direct IP from the menu.
Common Boot Failures
| Symptom | Likely cause | Fix |
|---|---|---|
| SteamCMD reports "no such app" | +@sSteamCmdForcePlatformType windows not set, or set in wrong order | Place the platform-force flag before +force_install_dir |
| Wine errors on launch | Missing 32-bit packages or winetricks dependencies | Run winetricks dotnet48 vcrun2019 in your prefix |
| "Display not available" / cannot init renderer | Headless Linux without virtual display | Wrap in xvfb-run |
| Server boots but doesn't appear in browser | Ports 9876/9877 not forwarded; public visibility off | Open ports + check HostSettings.json |
| Players see "Server not responding" | Query port (9877) blocked | Forward 9877 UDP+TCP |
Wine Compatibility Notes
V Rising on Wine works but is not the supported install path from Stunlock Studios. Things to know:
- Run with the latest stable Wine (or Wine staging) — older Wine versions fail on .NET dependencies V Rising uses
- 32-bit and 64-bit packages both needed
- Some hosts use the "GE Proton" build of Wine for better game compatibility
- If the server crashes randomly, check the
~/.wine/dosdevices/c:/users/...path for Wine logs
Hardware Notes
V Rising is moderately CPU-bound on the server (castle simulation, blood quality calculations, decay timers). Memory usage scales with castle count and player base. NVMe storage smooths autosave writes. Specific resource numbers depend on player count and castle density — watch usage on first boot and adjust your plan.
Related Reading
- V Rising admin commands
- Add admins to your V Rising server
- Kicking and banning
- Official: Stunlock Studios — V Rising Dedicated Server Instructions
Quick Start with Supercraft
Supercraft hosts V Rising dedicated servers with the Wine wrapper preconfigured, both JSON config files exposed via panel form fields, automatic Wine + dependency management, and snapshot backups. Settings (difficulty, decay, PvP rules, blood quality) are panel-driven — no JSON editing.