Configurer un serveur V Rising pour jouer à plusieurs

V Rising server settings are defined almost entirely in two JSON files that ship with every dedicated instance: ServerHostSettings.json and ServerGameSettings.json. Together they govern clan size, PvP windows, castle decay, loot drops and build limits. This guide walks through what each parameter does and how to edit the files without breaking your save.

Where V Rising Server Settings Actually Live

Every V Rising instance stores its configuration under the VRisingServer/VRisingServer_Data/StreamingAssets/Settings folder. If you're running it manually, this is the path relative to your installation directory. If you're using a managed panel, the same files appear in the file manager, usually under a Settings or Config subfolder, ready to edit without touching a terminal.

Two files matter for gameplay tuning:

• ServerHostSettings.json — session-level parameters: name, description, password, max player count, clan size, PvP toggle and save interval.
• ServerGameSettings.json — the full ruleset: day/night length, resource rates, decay timers, castle limits, loot tables and raid behavior.

If you want to skip the manual setup entirely and get both files pre-generated with a working default ruleset, a V Rising server hosting instance deploys them automatically and exposes every field through the control panel's file editor.

Editing ServerHostSettings.json: Clan Size, Slots and PvP Scheduling

This file controls the structural rules of your session rather than in-game mechanics. Open it with any plain text editor — never Word or a rich-text tool, since they can inject invisible characters that break JSON parsing.

Core fields you'll touch most often

Field	Purpose	Typical value
Name	Session name shown in the server browser	"My Clan Castle"
Password	Join password, leave empty for public	"" or a string
MaxConnectedUsers	Maximum concurrent players	10–40
MaxConnectedAdmins	Admin slots reserved separately	2–4
ClanSize	Maximum players per clan	1–8
Port	Game port, must be forwarded if self-managed	9876
AutoSaveCount / AutoSaveInterval	Number and frequency of autosaves	20 / 120

Example snippet

{
  "Name": "Dusk Haven",
  "Description": "PvE focused, weekend PvP window",
  "Port": 9876,
  "MaxConnectedUsers": 20,
  "MaxConnectedAdmins": 4,
  "ClanSize": 4,
  "AutoSaveCount": 20,
  "AutoSaveInterval": 120,
  "ListOnMasterServer": true,
  "Password": ""
}

Clan size has a direct effect on balance: raising it to 6 or 8 favors large groups and makes castle sieges heavier on CPU during raid windows, while keeping it at 2–3 preserves a more solo/duo friendly pace. Adjust it based on your community size rather than copying a generic value.

Fine-Tuning ServerGameSettings.json: Decay, Loot and Castle Limits

This is the file where most of the real V Rising server settings tuning happens. It's larger, and a single misplaced comma will prevent the instance from starting, so always keep a backup copy before editing.

PvP scheduling

PvP windows are controlled through the GameModeType and PvPProtectionMode blocks combined with SiegeWeaponHealth and raid time fields. A common setup restricts sieges to weekends:

"CastleHeartDamageMode": "SiegeWeaponOnly",
"SiegeWorldStateType": "Weekend",
"StartHour": 18,
"StopHour": 22

Test any PvP schedule change on a copy of your world first — the siege window logic depends on server time, not player local time, so confirm the timezone your instance reports before announcing a raid night to your community.

Castle decay and territory limits

Decay prevents abandoned castles from clogging the map. Key fields:

• CastleDecayRateModifier — multiplier on how fast an unheated or unvisited castle degrades.
• CastleMinimumDistanceInFloors — minimum spacing between territories, raise it on smaller maps to prevent overlapping claims.
• CastleBloodEssenceDecayPct — percentage drain applied to the heart over time without upkeep.

"CastleDecayRateModifier": 1.0,
"CastleMinimumDistanceInFloors": 1,
"CastleBloodEssenceDecayPct": 0.05

On a community instance with limited map space, pushing CastleDecayRateModifier above 1.0 clears inactive bases faster and keeps prime territory available for active clans.

Loot tables and resource rates

Loot abundance is driven by DropTableModifier_General, DropTableModifier_Shard and resource yield multipliers under ResourceYieldModifier. Increasing these numbers speeds up progression — useful for a PvP-focused community that wants players geared quickly, but it flattens the long-term crafting loop if pushed too high.

"DropTableModifier_General": 1.5,
"ResourceYieldModifier": 1.25,
"JournalVBloodSourceUnitMaxHealthModifier": 1.0

Keep a changelog of every modifier you touch. When a build suddenly feels too easy or too grindy, you'll want to trace it back to a specific line instead of guessing.

Applying V Rising Server Settings Changes Without Breaking the World

JSON is unforgiving: a missing bracket or trailing comma stops the process from launching, and the error message in the console log is often generic. Follow a short checklist before every restart.

Validate before you restart

1. Copy both files to a dated backup folder.
2. Paste the edited JSON into a validator to catch syntax errors before upload.
3. Apply one change category at a time — don't edit clan size, decay and loot rates in the same pass.
4. Restart and check the console log for a clean load message.

Restarting through the console

If you manage the process directly over SSH on a Linux machine, a typical restart sequence looks like this:

cd /home/vrising/VRisingServer
screen -S vrising -X stuff "stop\n"
sleep 10
./VRisingServer.sh -persistentDataPath ./save-data > vrising.log 2>&1 &

On a managed panel, the equivalent action is a single click on restart, with the console tab showing load progress and any JSON parsing errors in real time — far faster to diagnose than tailing a raw log file.

Backups matter more than the settings themselves

Before any batch of changes, trigger a manual backup of your save data in addition to the automated ones. Decay and castle-limit edits especially can interact unpredictably with existing structures, and a save-corrupting bug is far easier to recover from with a recent snapshot than by trying to hand-edit the save file. For a broader look at how other survival titles expose comparable configuration options, browse All our game servers or check the Fly-Serv blog for game-specific guides.

If you're running the instance on your own infrastructure through a control panel, a Pterodactyl VPS setup gives you the same file editor and console access described above, with sub-user permissions if you want to delegate settings edits to a trusted co-admin without handing over full access.

Conclusion

Getting comfortable with ServerHostSettings.json and ServerGameSettings.json turns vague complaints like "raids are too easy" or "decay feels off" into specific, testable adjustments. Change one parameter at a time, keep backups, and validate your JSON before every restart to keep your world stable.

FAQ

Why won't my V Rising instance start after editing the JSON files?

This almost always means invalid JSON syntax — a missing comma, an extra bracket, or quotes left open. Paste the file content into a JSON validator before uploading it again, and restore your backup if you can't locate the error quickly.

Can I change clan size on an existing world without wiping progress?

Yes. ClanSize only affects new or restructured clans going forward; existing clans above the new limit stay intact until members leave and try to re-form, so it's safe to adjust mid-session.

How do I test new decay or loot settings without risking the live world?

Duplicate your save folder and configuration files into a separate test instance, apply your changes there, and run it for a few in-game days before porting the confirmed values back to your main configuration.