How to Configure Your V Rising Server
V Rising uses two separate JSON config files to control network settings and game rules. Here's how to find, edit, and validate them safely.
The Two Config Files
V Rising splits its server configuration across two JSON files, both located in:
VRisingServer_Data/StreamingAssets/Settings/
- ServerHostSettings.json — network and visibility settings (server name, ports, passwords, browser listings)
- ServerGameSettings.json — all gameplay rules, difficulty, PvP modes, and modifiers
You need to understand which file controls what before you start editing. Changing the wrong file won't break anything, but it also won't do what you intended.
Editing ServerHostSettings.json
This file controls how your server presents itself to the outside world. Here's a minimal working example:
{
"Name": "My V Rising Server",
"Description": "Welcome! No griefing.",
"MaxConnectedUsers": 40,
"MaxConnectedAdmins": 4,
"Port": 9876,
"QueryPort": 9877,
"Password": "",
"Secure": true,
"ListOnSteam": true,
"ListOnEOS": true,
"HideIPsFromPlayers": false,
"CompressionEnabled": true
}
Key fields to know:
| Field | What it does |
|---|---|
Name |
Server name shown in the browser |
MaxConnectedUsers |
Player cap (not counting admins) |
Port |
Game port (default 9876) |
QueryPort |
Steam query port (default 9877) |
Password |
Leave empty for a public server |
ListOnSteam |
Show in Steam server browser |
ListOnEOS |
Show via Epic Online Services |
How to Edit Safely
Always stop your server before editing config files. V Rising writes its configuration to disk on shutdown — if you edit while the server is running, your changes may be overwritten when it stops.
- Stop the server from your control panel
- Open the file manager and navigate to
VRisingServer_Data/StreamingAssets/Settings/ - Edit
ServerHostSettings.jsonin the built-in editor - Before saving, validate your JSON — paste it into jsonlint.com or use your editor's built-in validator
- Save the file
- Start the server
Invalid JSON will prevent the server from starting. The most common mistakes are trailing commas after the last property and mismatched curly braces. Always validate before you restart.
Checking Your Changes Took Effect
After restarting, look at your server in the Steam server browser or check the server log for any config-related errors. If the server name or max players didn't update, double-check that you saved to the correct file and that the JSON is valid.
For game rules and difficulty settings, see the companion article on ServerGameSettings.json.