V Rising ServerHostSettings.json generator

V Rising uses two JSON files with similar names, and putting a setting in the wrong one is the standard first mistake.

Visual Settings

json Format
Identity

Server name in the browser.

Description shown in the browser.

Game port, UDP.

Query port, normally the game port plus one. This is the one server lists read.

World

Save folder to load. A new name starts a fresh world.

How many autosaves to keep.

Seconds between autosaves.

Players & Access

Slot limit.

Admin slots held above the player limit.

Join password.

Network

Publishes the server publicly. Off means direct connection only, and no external checker can see it.

RCON & Query

Restricts debug commands to admins.

Remote console.

RCON port. Keep it private.

RCON password. Note that game rules — rates, decay, castle limits — are not in this file at all; they live in ServerGameSettings.json.

ServerHostSettings.json

{
  "Name": "Spawnly V Rising",
  "Description": "Vampire rules.",
  "Port": 9876,
  "QueryPort": 9877,
  "MaxConnectedUsers": 40,
  "MaxConnectedAdmins": 4,
  "SaveName": "world1",
  "Password": "",
  "ListOnMasterServer": 1,
  "AutoSaveCount": 20,
  "AutoSaveInterval": 120,
  "AdminOnlyDebugEvents": 1,
  "Rcon.Enabled": 0,
  "Rcon.Port": 25575,
  "Rcon.Password": ""
}

How ServerHostSettings.json syntax works

Both are strict JSON: no comments, no trailing commas, numbers unquoted. ServerHostSettings.json covers the server's identity and networking — name, description, ports, slots, password. Game rules do not belong here.

The mistake that costs people hours

Everything about how the game actually plays — rates, decay, PvP rules, castle limits — lives in ServerGameSettings.json instead. Settings put in the host file are ignored without complaint, which is why so many servers end up running default rules despite a carefully edited configuration.

How much RAM a V Rising server needsCheck a V Rising server’s statusV Rising server hostingAll games
Support & Help