PVESieges

PVESieges (V Rising)

Hostile factions besiege your castle in waves: they march on your castle heart, blow your doors with a sapper's bomb, and fight anyone who gets in their way. Beat the raid for the spoils of war.

Install

Only the server needs the mod: the dedicated server, or in a private / hosted game the built-in server the game starts (VRising_Server in the game folder). Players who join need nothing. Requires BepInEx 6 (IL2CPP, build 733 or newer).

• Thunderstore / r2modman (private or hosted game): install PVESieges with the mod manager and start the game from it. A mod manager puts mods in the game's own BepInEx, which the built-in server doesn't use, so the package brings ServerLaunchFix along: it makes the server the game starts use the same mods. The first host can time out while BepInEx prepares the server; host again (a few tries at most). ServerLaunchFix needs the game on an NTFS drive and rewrites the built-in server's doorstop_config.ini and BepInEx.cfg on every start.
• Dedicated server: install BepInEx on the server and copy PVESieges.dll into its BepInEx/plugins (with a mod manager: from its profile's BepInEx/plugins). Restart the server.
• Private / hosted game by hand (no mod manager): set BepInEx up in VRising_Server as for a dedicated server: copy BepInEx/ (without BepInEx/interop and BepInEx/cache, which are made fresh for the server), dotnet/, winhttp.dll, doorstop_config.ini and .doorstop_version from the V Rising folder into VRising_Server, and put PVESieges.dll in VRising_Server/BepInEx/plugins. The first host after that (and after each game update) can take 1–2 minutes while BepInEx prepares the server; if the game gives up, host again.
• Check it runs: the server's log (BepInEx/LogOutput.log; for a hosted game VRising_Server/BepInEx/LogOutput.log) shows Loading [PVESieges ...] and server world found. In the game client's own log the mod only says it has nothing to do there: that's expected.
• Updating: copy the new PVESieges.dll in; older ones can stay, BepInEx loads the newest. Upgrading from 1.0.242 or older: remove the old DLL (see below).

What it keeps and changes on your PC

• No internet access. The mod's own files hold no player data (no names, no SteamIDs).
• Player names: the only place one appears is the server log, when an admin uses !siege all or !siegestop (for example PVESieges: called a siege on every castle with someone home ...). Its purpose is to let server owners see who started or stopped raids. The mod writes it nowhere else and keeps it nowhere. Raid messages in chat (!siegemsg) and opting out (!siegeoptout) are remembered only until the server restarts and are never written to disk.
• Only with Trails on (off by default): walked trails near castles but outside players' plots (map positions only, per castle; inside a plot only the spots where a walk crosses its edge) in %LOCALAPPDATA%/CastleSieges/castles, saved once a minute in the background (off the server's main thread). Files of castles not on this save are kept (another save on the same PC may use them) and removed after 30 days unused.
• Its config, BepInEx/config/PVESieges.cfg.
• The heart scan and the game's terrain it reads are kept in memory only, for the raid, and never written to disk. With Trails off (the default) the mod writes nothing but its config.
• It never deletes, moves or copies any DLL. Several versions in the plugins folder are fine: BepInEx loads the newest. Upgrading from 1.0.242 or older (the plugin id changed from melty.castlesieges to pvesieges): remove the old DLL yourself; while it's still loaded, the new one stays off and the log names the file.

How sieges start

• At random: at sunrise (8%, DayChance) and nightfall (10%, NightChance), for every castle whose owner or a clan-mate is online. If someone is home (inside the castle's territory; with HomeTerritoryOnly off, within 60 m of the heart counts too), it starts right away; if they're all away, it waits and marches as soon as the owner or a clan-mate gets home (one waiting raid per castle; online clan members get a message).
• After slaying a V Blood (70%, VBloodRaidChance): that boss's own faction comes for your clan's castle when you or any clan-mate is back home (without a clan: your castle, when you are). One such raid waits per clan at a time; a kill while one is waiting says so. Beasts and bosses without a raiding faction don't.
• Raids are called off if the owner and the whole clan go offline.
• Admins (logged in with adminauth) can call and stop sieges in chat (see Commands).

Factions

Which factions can come depends on your castle heart level:

Heart level — Sunrise — Nightfall

1-2 — Bandits, Restless Dead (Farbane) — Restless Dead

3 — Militia, Dunley Dead — Dunley Dead

4 — the Transcendum, Dracula's Vanguard (the Legion's lesser troops), Restless Spirits (ghosts) — Restless Spirits

5 — the Church of Light's army, the Blackfang's Venom Blades, Dracula's Legion — any of these

Slaying a faction's V Blood sends that faction whatever your heart level. A clan gets one kind of raid at a time: while a random raid (sunrise or nightfall) is waiting, under way, or has ended since the last sunrise or nightfall, V Blood kills call no raid; and while a V Blood raid is, sunrise and nightfall don't roll for that clan.

Rarely, the forest itself comes: at every nightfall and sunrise there's a 3% chance (TreantRaidChance) of a Treant raid instead, whatever your heart level, with waves of 2 Treants each (TreantWaveSize). Treants never sleep during a raid and plant no bombs: they line up before your door and break it with one volley of entangling projectiles.

A siege

• A warning, then 30 seconds later (WarningSeconds) the first wave. Three waves by default (Waves, 1–10) of 5, 8 and 10