Configurer une petite partie V Rising entre amis : les réglages qui comptent

Getting V Rising server settings right is what turns a chaotic free-for-all into a game your group actually wants to keep playing. Between ServerGameSettings.json and ServerHostSettings.json, you control slots, clan size, castle limits, decay speed, raid windows and loot rates — all without touching a single line of game code.

ServerHostSettings vs ServerGameSettings: What Each File Actually Controls

V Rising splits its configuration across two JSON files, and mixing them up is the number one reason tweaks "don't work." ServerHostSettings.json handles the connection layer: the name shown in the browser, port numbers, password, max player count and save slot name. ServerGameSettings.json is where the real gameplay tuning lives — clan size, castle rules, decay, raid windows, resource and loot multipliers, and difficulty presets like Standard, Hard or Brutal.

Both files sit in the VRisingServer/save-data/Settings folder (or the save-specific subfolder once a world has been generated). If you're running V Rising alongside other game instances on the same machine through a Pterodactyl VPS, you'll find these files through the panel's file manager without needing direct shell access. For a dedicated setup built specifically around this game, the V Rising server hosting environment at Fly-Serv ships with sensible defaults already applied, so you're editing from a working baseline instead of a blank template.

Locating and Editing the Files

Both JSON files can be edited with any plain text editor. Stop the game instance before editing — V Rising reads these files on startup and some values (like clan size or max database size) are only applied at boot, not hot-reloaded.

VRisingServer/
└── save-data/
    └── Settings/
        ├── ServerGameSettings.json
        └── ServerHostSettings.json

Tuning Player Slots, Clan Size and Castle Limits

For a small group of friends, the default clan size of 4 and the standard castle territory limits are often too generous or too restrictive depending on how many of you actually log in regularly. Start with ServerHostSettings.json to cap the total population:

{
  "Name": "Sunset Coven",
  "Description": "Small group session",
  "Port": 9876,
  "QueryPort": 9877,
  "MaxConnectedUsers": 6,
  "MaxConnectedAdmins": 2,
  "ShowStatusTool": true,
  "AutoSaveCount": 20,
  "AutoSaveInterval": 300
}

MaxConnectedUsers is your hard population cap — keep it close to your actual friend group size rather than leaving it at a default built for public lobbies. Then move to ServerGameSettings.json for clan and territory behavior:

{
  "ClanSize": 6,
  "CastleMinDistance": 2,
  "CastleLimit": 3,
  "CastleBloodEssenceDrainModifier": 1.0
}

Why Clan Size Matters More Than You Think

Setting ClanSize above your actual player count lets everyone share one castle heart and pool resources without splitting into awkward sub-clans. For a six-person group, matching ClanSize to 6 (or slightly above, to allow guests) avoids the frustration of someone being locked out of shared storage because the clan is "full."

Castle Limits for Small Groups

If your group builds one shared base rather than individual castles, lowering CastleLimit prevents accidental sprawl and keeps the map readable. If each player wants their own territory, raise it instead — just watch your CastleMinDistance value so bases don't overlap and trigger decay conflicts near shared borders.

Decay, Raid Windows and Loot Multipliers: Building V Rising Server Settings Around Your Playstyle

This is where V Rising server settings stop being administrative housekeeping and start shaping the actual feel of the game. A small cooperative group rarely wants the same pacing as a competitive public lobby.

Decay Speed

Castle decay punishes absence — fine for large populations, brutal for a five-person group where two people go on holiday for a week. Reduce the pressure in ServerGameSettings.json:

{
  "CastleDecayRateModifier": 0.3,
  "CastleSiegeTimer": 300,
  "GraceSiegeTimer": 240
}

A CastleDecayRateModifier below 1.0 slows the countdown considerably, giving your group breathing room without disabling decay entirely — which still matters for keeping abandoned structures from cluttering the map permanently.

Raid Windows

If raiding isn't the point of your session (many small groups play V Rising purely for the building and vampire progression loop), you can restrict when castles become vulnerable:

{
  "RaidTimeTimer": "18:00",
  "SiegeEnabled": false
}

Setting SiegeEnabled to false removes raid mechanics entirely — a common choice for friend groups who want progression without the stress of defending a base while offline. Leave it enabled with a tight RaidTimeTimer window if you still want occasional PvP tension on your own schedule.

Loot and Resource Multipliers

Adjusting drop rates changes the whole pace of the campaign. A faster-paced session for people with limited weekly playtime benefits from higher multipliers:

{
  "MaterialYieldModifier_Global": 1.5,
  "ResourceDurabilityModifier_Global": 1.3,
  "BloodEssenceYieldModifier": 1.2,
  "JewelCraftCostModifier": 0.75
}

Setting	Lower value effect	Higher value effect
MaterialYieldModifier_Global	Slower progression, more grinding	Faster crafting and building
CastleDecayRateModifier	Bases persist longer unattended	Decay punishes absence quickly
ClanSize	Forces smaller sub-groups	One shared clan for everyone

Validating Your Changes

Always restart the game process after editing both files and check the console log for parsing errors — a missing comma in either JSON file will silently fall back to defaults instead of crashing, which makes mistakes easy to miss. Keep a saved copy of both files before major edits; a quick manual backup or an automated snapshot through your panel saves you from rebuilding settings from memory after a bad edit.

Applying Changes Without Breaking Your Save

Some values in ServerGameSettings.json only take effect on a fresh world, while others apply live on restart to an existing save. Clan size and castle limits generally apply retroactively, but drastically lowering CastleLimit below your current built territories can orphan existing castles rather than delete them — test on a copy of your save-data folder first if you're unsure.

• Stop the process cleanly before editing JSON files.
• Validate JSON syntax before restarting (a linter or even a quick online validator catches trailing commas).
• Keep the console log open during the first boot after changes to catch silent rollbacks to defaults.
• Take a manual backup of save-data before testing aggressive decay or clan size changes.

If you're managing this through a control panel rather than raw file access, the same logic applies: edit, save, restart, then check the live console output before inviting your group back in. Browsing the full list of supported titles on All our game servers is useful if you're also running a second game instance for the same group, since the backup and file-editing workflow stays consistent across Pterodactyl-managed environments.

For broader context on the underlying values and accepted ranges, Stunlock Studios maintains settings documentation worth checking against your own file: V Rising Wiki.

Tuning clan size, castle limits, decay and loot multipliers lets a small group shape V Rising around how they actually want to play, rather than fighting defaults built for large public lobbies. Test changes on a backup save first, restart cleanly, and adjust gradually until the pacing feels right for your group.

FAQ

Why don't my ServerGameSettings.json changes apply after restart?

Check the console log first — a JSON syntax error like a trailing comma silently reverts the file to defaults instead of throwing a visible crash. Validate the file structure before restarting.

Can I change clan size after a world has already been created?

Yes, ClanSize generally applies retroactively on restart, but existing clans larger than a newly lowered value won't be automatically split — only new clan formations respect the updated cap.

Does disabling SiegeEnabled remove all PvP from the game?

No, it only disables castle sieges and raiding. Open-world combat between players outside of castle territories still functions normally unless you adjust separate PvP settings.