V Rising Server Config Generator

The name players see in the in-game server browser. Default "My V Rising Server" — which is also what every un-configured server is called, so change it unless you enjoy being one of a thousand identical entries. Keep it short and searchable.

Short blurb shown under your server name in the browser. Empty by default. One line of "PvP, weekly raid windows, Discord in info" does more to fill slots than the name does — worth filling in for a community server.

Required to join. Leave it blank for an open public server; set a password to make it private (friends still connect via the browser or direct connect with the password). Empty by default = open server.

UDP port players connect on. Default 27015. Forward it on your router and open it on the firewall. Change it (and the query port below) if you're running more than one V Rising server on a single box.

UDP port the Steam server browser queries for server info (name, player count). Default 27016, one above the game port. Without it set and forwarded, your server may show up empty or not at all in the browser.

Total concurrent players allowed. Default 40, and the hard cap is 128 — the game won't go higher. Each extra player costs CPU and RAM and adds a castle to simulate, so don't set 128 on a box that can barely hold 40; performance falls off well before the slot limit on modest hardware.

Extra slots for admins above the Max Connected Users cap, so staff can always join even when the server is genuinely full. Default 4. These are bonus capacity, not carved out of the player cap. Admins are matched by the adminlist, not by this number alone.

How many times per second the server simulates the world. Default 30. Higher (up to 60) makes combat feel crisper but costs CPU; lower eases a strained box at the price of laggier fights. 30 is the sweet spot for most servers — only push to 60 if you have the headroom and a PvP crowd that notices.

The save directory name the server loads world and player data from. Default "world1". This isn't cosmetic — change it on a live server and you boot into a different (usually empty) save while the old one sits untouched on disk. Set it once and leave it alone unless you deliberately want a fresh world.

How many rolling autosave backups the server keeps before overwriting the oldest. Default 20. More backups = deeper rollback history if a save corrupts or someone needs reverting, at the cost of disk space. Pair with the interval below.

Seconds between automatic saves. Default 120 (every 2 minutes). Shorter intervals mean less lost progress on a crash but more frequent micro-stutters as the server writes; longer intervals are smoother but risk losing more on a hard crash. 120 is a sensible balance.

TCP port the RCON interface listens on. Default 25575. Keep it different from the game/query ports, and only forward it if you genuinely need off-box remote control — an exposed RCON port with a weak password is a server-takeover waiting to happen.

The password RCON clients authenticate with. Empty by default. Must be set if RCON is enabled, or the RCON listener silently won't start — a classic "why won't my tool connect" gotcha. Use a long random string; anyone with this has full admin over your server.

Name of a built-in gameplay preset (e.g. StandardPvP, StandardPvE). ⚠ If you set this, the server IGNORES your ServerGameSettings.json entirely and uses the named preset's values instead. Leave it blank to use the custom settings you build here. This is the single most common reason "my settings didn't apply."

The master mode switch. PvP (default) lets players damage each other; PvE makes it a cooperative server where they can't. Most of the castle/player damage settings below only bite on PvP — on PvE they're largely moot, but set them anyway in case you switch later.

When player castles can be damaged. Always (default) = raidable any time. Never = castles are indestructible (the usual PvE choice). TimeRestricted = only during the castle windows you set in Time-Restricted PvP below. This is the headline raid-rules dial.

When players can damage each other. Always (default) = open PvP 24/7. TimeRestricted = players can only fight during the player windows you set in Time-Restricted PvP below. There's no "Never" here — for a no-PvP server, set Game Mode to PvE instead.

How the castle heart — the core that owns a base — can be taken or destroyed. CanBeDestroyedByPlayers (default) = raiders can smash it outright. CanBeDestroyedOnlyWhenDecaying = only vulnerable once the base is decaying (offline protection). CanBeSeizedOrDestroyedByPlayers = raiders can claim the base instead of just wrecking it. Seizing is the brutal full-takeover option.

How long fresh characters get a no-PvP grace period after first spawning. Disabled = none. Short, Medium (default), Long = progressively longer protection. Keep it on a PvP server so new players aren't spawn-camped into quitting; Disabled suits a hardcore crowd.

How tough the Siege Golem (the raid weapon) is, which effectively sets how long a raid window has to breach a base. Normal (default) through the escalating High → Max tiers make golems last longer, favouring attackers. Crank it up for a raid-heavy PvP server; leave it Normal for balanced sieges.

Who can loot the container your stuff drops into when you die. Anyone (default) = full wild-west PvP looting. ClanMembers = only your clan can recover it. OnlySelf = only you. PvE servers usually run OnlySelf; cutthroat PvP leaves it on Anyone.

How the endgame Soul Shard relics spawn. Unique (default) = one of each across the whole server, so clans fight over them — the intended competitive endgame. Plentiful = each clan can hold their own, removing the contest. Unique is the PvP choice; Plentiful suits PvE or co-op.

Multiplier on how many items fit in a single stack. Default 1.0. Raise it (2–4×) on a boosted server so chests and inventories hold more before you're juggling slots — a big quality-of-life win that pairs naturally with higher yield rates.

Multiplier on general loot drops from mobs and the world. Default 1.0. Raise for a more generous server where kills and exploration pay out faster; this is separate from the resource yield setting below, which covers harvesting nodes.

How much you get per resource node hit — the single most-tweaked V Rising rate. Default 1.0. 2× cuts gathering time in half without trivializing it; 4–5× turns harvesting into a checkbox. The headline "boosted server" dial.

Multiplier on Blood Essence harvested from creatures — the fuel that keeps your castle heart running and your servants fed. Default 1.0. Raise it so players spend less time topping off the heart and more time playing; a common comfort tweak on casual servers.

Multiplier on materials needed to place structures. Default 1.0. Lower is cheaper — 0.5 halves the cost of every wall, floor, and station. Drop it on a creative or casual server where building sprawl is the fun, not the grind.

Multiplier on materials required to craft items. Default 1.0. Lower is cheaper. Combine 0.5 here with a higher Resource Yield above for proper boosted-server tuning — players gather more and spend less per craft.

How fast crafting stations produce items. Default 1.0. Higher is faster — 2× halves every craft timer. A near-universal quality-of-life tweak; waiting on the furnace is nobody's favourite part of the game.

Multiplier on the materials (paper, schematics) needed to research recipes. Default 1.0. Lower is cheaper. Drop it so unlocking the tech tree is less of a paper grind — pairs well with the research-time setting below for a faster-progressing server.

Multiplier on inputs for refining stations (sawmills, furnaces, grinders). Default 1.0. Lower is cheaper — fewer logs per plank, less ore per ingot. Combine with faster refinement rate below to keep the supply chain flowing on a busy server.

How fast refining stations convert raw materials. Default 1.0. Higher is faster — 2× halves smelting and milling times. One of the most-appreciated comfort tweaks on community servers so admins aren't forever babysitting the furnace.

Multiplier on how long research takes to complete. Default 1.0. Lower is faster — 0.5 halves the wait to unlock recipes. The standard boosted-server move is to drop this below 1.0 so the tech tree opens up faster.

How fast captured humans convert into servants in the thrall coffin. Default 1.0. Higher is faster. Bump it (2–3×) so a high-tier servant takes minutes instead of a long real-world wait — converting feels like a reward, not a punishment.

Multiplier on materials needed to repair gear and structures. Default 1.0. Lower is cheaper — set it low (or near 0) so maintaining your kit isn't a constant resource drain. A nice comfort tweak on PvE and casual servers.

How fast your blood pool depletes as you act — V Rising's hunger equivalent. Default 1.0. Higher drains faster, forcing more frequent feeding (a hardcore touch); lower eases the constant blood upkeep for a more relaxed pace. Raise it for a survival-flavoured server.

How fast weapons and armour lose durability with use. Default 1.0. Higher wears gear out faster (more repair pressure, a hardcore lever); lower makes equipment last longer. Set it low on a casual server so players aren't constantly back at the workbench.

How harshly garlic-saturated areas (towns, certain dungeons) debuff you. Default 1.0. Set to 0 to remove the garlic penalty entirely; raise it for a server where human settlements are genuinely hostile to a vampire. Lower it for easier town raids.

How much holy ground (cathedrals, the Church zones) burns and weakens you. Default 1.0. 0 disables it; higher makes the late-game holy areas a real gauntlet. This is a key difficulty lever for the endgame regions where the toughest content lives.

How much carrying or being hit by silver hurts you. Default 1.0. 0 removes the silver penalty, which some players do so they can stockpile silver coins freely; raise it to make silver weaponry and the silver economy genuinely dangerous to handle.

How much daylight damages you — the defining vampire constraint. Default 1.0. 0 lets you walk around at noon with no penalty (very casual); 2× makes daytime genuinely lethal and forces nocturnal play. The single biggest "how vampire is this server" dial.

Multiplier on player maximum health. Default 1.0. Raise it for tankier vampires and more forgiving fights (good for PvE or casual PvP); lower it for a lethal, glass-cannon server where one bad trade is fatal.

Multiplier on the player energy pool that fuels abilities. Default 1.0. Raise it so players can chain more ability casts before running dry — a power-fantasy boost; lower it to make resource management in combat matter more.

Multiplier on melee/weapon damage players deal. Default 1.0. Raise on PvE for faster boss kills; raise carefully on PvP since it makes melee builds hit hard and shortens fights. Pairs with Spell Power below for overall combat tuning.

Multiplier on ability/spell damage players deal. Default 1.0. Raise it to favour caster builds and speed up boss fights; on PvP this can swing the meta toward spell builds, so tune it alongside Physical Power to keep the two in balance.

Multiplier on the damage your gathering tools deal to resource nodes — how fast you mine rock and chop trees, separate from yield. Default 1.0. Raise it so harvesting feels faster even at vanilla yield; a subtle quality-of-life boost.

Maximum members per clan. Default 4. Small caps (2–4) keep PvP balanced and prevent zerg clans steamrolling the server; larger caps (10+) suit big PvE communities. Setting it to 1 effectively makes the server solo-only.

Minimum gap, measured in floor tiles, that must sit between one clan's castle and another's. Default 2. Larger values spread bases out and reduce boxing-in griefing; 0 lets players build wall-to-wall. Raise it on a crowded PvE server to keep neighbours civil.

How fast a castle decays when its heart runs out of fuel. Default 1.0. Higher decays faster; lower preserves bases longer. To effectively disable decay, set it to a very small value like 0.1 rather than exactly 0 — a literal 0 can behave oddly (see the inline warning).

How fast the castle heart consumes stored Blood Essence to keep the base powered. Default 1.0. Lower means you refuel less often — drop it on a casual server so players aren't constantly feeding the heart; 0 effectively makes the heart run forever.

How long, in seconds, a castle stays in the vulnerable "under siege" state once a Siege Golem is activated against it. Default 420 (7 minutes). Longer windows favour attackers (more time to breach); shorter ones favour defenders. Tune alongside Siege Weapon Health for your raid pacing.

How many separate castles a single clan can own at once. Default 2 (a main base plus an outpost). Raise it to let clans hold multiple territories — common on large PvE servers — but more castles per clan means more of the map locked down. Nests under CastleStatModifiers_Global in the output.

Real-world seconds for one full in-game day-night cycle. Default 1080 (18 minutes). Shorter cycles bring night — and the safety from the sun — around faster; longer cycles stretch each day out. Tune this against Sun Damage to set how much of real time players spend dodging daylight.

The earliest, in in-game days, a blood moon can occur after the last one. Default 10. The game picks a random day between this and the Max below, so blood moons don't land on a perfectly predictable schedule. Set both Min and Max equal for a fixed cadence.

The latest, in in-game days, before a blood moon must occur. Default 18. With the Min above, the actual blood moon day lands somewhere in the 10–18 range by default. Lower this for more frequent blood moons; raise it to make them rare.

How strong the buff players receive during a blood moon is, as a fraction. Default 0.2. Higher makes blood moon nights a real power spike worth planning PvP around; 0 removes the buff so the blood moon is purely atmospheric. A modest 0.2 keeps it meaningful without warping the meta.

Which clock the windows below are measured against. Local (default) = the server machine's local time; UTC = universal time. Pick Local if your community is in one region; pick UTC for an international server so everyone reads the same window the same way.

Hour (0–23) that player-vs-player combat opens on weekdays. Default 17 (5pm). Only used when Player Damage Mode is TimeRestricted. Pair with the end hour below to set the evening fight window after people get home from work.

Hour (0–23) that weekday player combat closes. Default 23 (11pm). Outside this window players can't damage each other. Only relevant when Player Damage Mode is TimeRestricted.

Hour (0–23) player combat opens on weekends. Default 17 (5pm). Many servers run a wider weekend window than weekdays — start earlier and end later — since players have more free time. Only used with TimeRestricted player damage.

Hour (0–23) weekend player combat closes. Default 23 (11pm). Outside the window, PvP is off. Only relevant when Player Damage Mode is TimeRestricted.

Hour (0–23) castles become raidable on weekdays — V Rising's "raid window," independent from player combat. Default 17 (5pm). Only used when Castle Damage Mode is TimeRestricted. This is the setting most servers tune to confine raiding to evenings.

Hour (0–23) the weekday castle-raid window closes. Default 23 (11pm). Outside this window bases can't be damaged. Only relevant when Castle Damage Mode is TimeRestricted.

Hour (0–23) castles become raidable on weekends. Default 17 (5pm). Weekend raid windows are often longer than weekday ones, since that's when most of the server is online to attack and defend. Only used with TimeRestricted castle damage.

Hour (0–23) the weekend castle-raid window closes. Default 23 (11pm). Outside the window, bases are safe. Only relevant when Castle Damage Mode is TimeRestricted.

Binds the server to one specific local network interface (IP) on a multi-homed box. Blank by default = listen on all interfaces, which is what you want on a normal single-IP machine. Only set this if you know you have multiple NICs and need to pin the server to one.

The reduced tick rate used while the server is empty, when Lower FPS When Empty is on. Default 5. Lower saves more CPU; the server jumps back to its normal tick rate the moment a player connects, so this only affects idle time.

Automatically wipes the world every N days — for season/reset servers. Default 0 = no scheduled wipe (the normal case). Set it to, say, 30 for monthly resets. Pair with the day-of-reset setting below to control which weekday the wipe lands on.

Which weekday a scheduled wipe is allowed to occur on. Default Any. Only used when the wipe interval above is greater than 0 — pin it to, say, Monday so resets always land at the start of the week rather than mid-weekend.

How long, in seconds, a slot is held open for a player who dropped, so they can rejoin without losing their place when the server is full. Default 300 (5 min). Pair with the slot count below — this is purely about reconnect grace, not normal capacity.

How many dropped-player slots the server reserves for reconnection grace at once. Default 10. Raise it on a busy full server where disconnects are common so returning players aren't locked out by newcomers grabbing freed slots.

A tiered save-retention rule (advanced) that keeps a thinning history of older saves rather than a flat rolling count. Blank by default = use the simple Auto-Save Count from the Capacity section. Leave it blank unless you specifically need long-tail backup retention.

Loads a built-in difficulty profile (Easy / Normal / Brutal) for the host. Blank by default = no preset applied. We couldn't fully confirm the exact value set this maps to against the current patch, so treat it as a convenience and verify in-game if your server depends on a specific difficulty.

Multiplier on rewards from servant missions (the hunts you send thralls on). Default 1.0. Raise it so the mission system pays out faster on a boosted server; this is separate from the general and resource drop rates in the main Rates section.

How much of a structure's build cost you get back when you dismantle it. Default 0.75 (75% refund). Raise toward 1.0 for a near-full refund so rebuilding is cheap; lower it to discourage constant teardown-and-rebuild on a survival-flavoured server.

How much durability your equipped gear loses when you die. Default 0.25 (a quarter). Set to 0 to remove the death durability penalty entirely (casual); raise it toward 1 for a harsher server where dying genuinely wrecks your kit.

Scales how the death durability loss is converted into a resource cost to repair. Default 1.0. Works alongside the durability-loss setting above to set how expensive recovering from a death is. Most servers leave this at vanilla.

The max distance at which a V Blood boss counts as "encountered" for your journal/tracking. Default 25. A deep tuning value most admins never touch — raise it only if you want bosses logged from further away.

Multiplier on the siege damage players deal to castles. Default 1.0. Raise it to make raids faster (favours attackers); lower it to make breaching a base take longer. Nests under VampireStatModifiers alongside the main power stats.

Multiplier on damage players take. Default 1.0. Below 1.0 makes players tankier (casual/PvE); above 1.0 makes everything hit harder for a lethal server. A blunt overall difficulty lever that pairs with Max Health.

How long, in seconds, before a player can cancel a revive (e.g. choose a different spawn). Default 5. A small timing value most servers leave alone; nests under VampireStatModifiers.

Multiplier on the max-energy stat granted by equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Scales how much gear contributes to your energy pool, separate from the base vampire stat.

Multiplier on the max-health stat granted by equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Controls how much your gear adds to total health on top of the base vampire stat.

Multiplier on the resource-yield bonus from equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Stacks with the global resource yield rate for gear that boosts gathering.

Multiplier on the physical-power stat from equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Scales how much melee/weapon damage your gear adds, separate from the base vampire stat.

Multiplier on the spell-power stat from equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Scales how much ability damage your gear contributes.

Multiplier on the siege-power stat from equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Affects gear that boosts castle-damage during raids.

Multiplier on movement-speed bonuses from equipment. Default 1.0. Nests under EquipmentStatModifiers_Global. Raise it to make speed-boosting gear matter more on a fast-paced server.

Multiplier on the health of normal (non-V-Blood) enemy creatures. Default 1.0. Nests under UnitStatModifiers_Global. Raise it to make the world tankier and combat longer; lower it for faster clears.

Multiplier on the damage normal enemy creatures deal. Default 1.0. Nests under UnitStatModifiers_Global. The companion to enemy health above — raise both for a genuinely dangerous overworld.

Multiplier on the health of V Blood bosses specifically. Default 1.0. Nests under UnitStatModifiers_VBlood. Tune this independently of normal enemies to make boss fights tougher or quicker without changing the rest of the world.

Multiplier on the damage V Blood bosses deal. Default 1.0. Nests under UnitStatModifiers_VBlood. Pair with boss health above to set how punishing the marquee fights are, separate from ordinary mobs.

How often, in seconds, castle systems (decay, blood drain) update. Default 5. A low-level performance/behaviour knob — most admins leave it at vanilla. Nests under CastleStatModifiers_Global.

Flat damage resistance applied to castle structures, as a fraction. Default 0 (no extra resistance). Raise it toward 1 to make bases much tougher to breach — a defender-friendly lever on top of Siege Weapon Health. Nests under CastleStatModifiers_Global.

How many Safety Boxes (the offline-protected storage) each castle can have. Default 1. Raise it to let players stash more across protected containers. Nests under CastleStatModifiers_Global.

How many Tombs (servant-summon structures) each castle can hold. Default 12. Raise it for bigger servant armies; lower it to cap base power. Nests under CastleStatModifiers_Global.

How many Vermin Nests each castle can build. Default 4. A production-structure cap most servers leave at vanilla. Nests under CastleStatModifiers_Global.

Max floor tiles a Level 1 castle heart can support. Default 30. The heart-level limits set how big a base can grow at each upgrade tier. Nests under CastleStatModifiers_Global.HeartLimits.Level1.

Max servants a Level 1 castle heart can hold. Default 3. Nests under CastleStatModifiers_Global.HeartLimits.Level1.

Max floor tiles a Level 2 castle heart can support. Default 100. Nests under CastleStatModifiers_Global.HeartLimits.Level2.

Max servants a Level 2 castle heart can hold. Default 5. Nests under CastleStatModifiers_Global.HeartLimits.Level2.

Max floor tiles a Level 3 castle heart can support. Default 150. Nests under CastleStatModifiers_Global.HeartLimits.Level3.

Max servants a Level 3 castle heart can hold. Default 7. Nests under CastleStatModifiers_Global.HeartLimits.Level3.

Max floor tiles a Level 4 (max) castle heart can support. Default 250. Nests under CastleStatModifiers_Global.HeartLimits.Level4.

Max servants a Level 4 (max) castle heart can hold. Default 9. Nests under CastleStatModifiers_Global.HeartLimits.Level4.

The decay penalty percentage applied in pylon range 1. Default 0 (no penalty). These are admin-supplied curve values; leave them at 0/0/0 unless you specifically know the decay-curve behaviour you want. Nests under PylonPenalties.Range1.

Lower bound for pylon range 1. Default 0. Nests under PylonPenalties.Range1.

Higher bound for pylon range 1. Default 0. Nests under PylonPenalties.Range1.

The decay penalty percentage applied in pylon range 2. Default 0. Nests under PylonPenalties.Range2.

Lower bound for pylon range 2. Default 0. Nests under PylonPenalties.Range2.

Higher bound for pylon range 2. Default 0. Nests under PylonPenalties.Range2.

The decay penalty percentage applied in pylon range 3. Default 0. Nests under PylonPenalties.Range3.

Lower bound for pylon range 3. Default 0. Nests under PylonPenalties.Range3.

Higher bound for pylon range 3. Default 0. Nests under PylonPenalties.Range3.

The decay penalty percentage applied in pylon range 4. Default 0. Nests under PylonPenalties.Range4.

Lower bound for pylon range 4. Default 0. Nests under PylonPenalties.Range4.

Higher bound for pylon range 4. Default 0. Nests under PylonPenalties.Range4.

The decay penalty percentage applied in pylon range 5. Default 0. Nests under PylonPenalties.Range5.

Lower bound for pylon range 5. Default 0. Nests under PylonPenalties.Range5.

Higher bound for pylon range 5. Default 0. Nests under PylonPenalties.Range5.

The decay penalty percentage applied in floor range 1. Default 0. Nests under FloorPenalties.Range1.

Lower bound for floor range 1. Default 0. Nests under FloorPenalties.Range1.

Higher bound for floor range 1. Default 0. Nests under FloorPenalties.Range1.

The decay penalty percentage applied in floor range 2. Default 0. Nests under FloorPenalties.Range2.

Lower bound for floor range 2. Default 0. Nests under FloorPenalties.Range2.

Higher bound for floor range 2. Default 0. Nests under FloorPenalties.Range2.

The decay penalty percentage applied in floor range 3. Default 0. Nests under FloorPenalties.Range3.

Lower bound for floor range 3. Default 0. Nests under FloorPenalties.Range3.

Higher bound for floor range 3. Default 0. Nests under FloorPenalties.Range3.

The decay penalty percentage applied in floor range 4. Default 0. Nests under FloorPenalties.Range4.

Lower bound for floor range 4. Default 0. Nests under FloorPenalties.Range4.

Higher bound for floor range 4. Default 0. Nests under FloorPenalties.Range4.

The decay penalty percentage applied in floor range 5. Default 0. Nests under FloorPenalties.Range5.

Lower bound for floor range 5. Default 0. Nests under FloorPenalties.Range5.

Higher bound for floor range 5. Default 0. Nests under FloorPenalties.Range5.

The in-game hour (0–23) at which daytime begins. Default 9. Shifts the window of daylight (and sun danger) within each cycle. Nests under GameTimeModifiers.

The minute (0–59) of the day-start hour at which daytime begins. Default 0. Fine adjustment on top of the start hour above. Nests under GameTimeModifiers.

The in-game hour (0–23) at which daytime ends and night begins. Default 17 (5pm). Together with the start hour this sets how long daylight lasts each cycle. Nests under GameTimeModifiers.

The minute (0–59) of the day-end hour at which daytime ends. Default 0. Fine adjustment on top of the end hour above. Nests under GameTimeModifiers.