RaidForge

RaidForge

RaidForge is a server-side V Rising mod for configurable raid schedules, offline base protection, opt-in raiding, purchased protection, weapon and explosive raiding, raid interference, map alerts, Siege Golem automation, Soul Shard rules, and per-castle servant limits.

Current mod version: 3.2.2

[!IMPORTANT]

RaidForge changes important combat and castle-protection rules. Back up your world and configuration files before installing or updating it, and validate changes on a test server first.

What's New

• Easier raid-time command: Players can use.raidtime, or the shorter.raidt, to see when the next raid window begins.
• Optional command customization: Server owners can rename or disable individual RaidForge commands and choose whether they appear in normal.help results. Command changes apply after a full restart.
• Separate TNT controls: T01 and T02 explosives can each have their regular damage, castle-wall damage, and after-breach behavior adjusted independently.
• Per-base servant limits: Server owners can cap selected servant types separately for every castle.
• Clan-safe counting: Clanmates share the servant limit for the base they are using, while a different castle keeps its own count.
• Safe servant rejection: A servant coffin refuses an extra servant before the captured NPC is consumed.
• Clear player feedback: Rejection messages are simple and throttled so repeated interactions do not spam chat.
• Lightweight troubleshooting: Detailed diagnostic logging remains off unless a server owner intentionally enables it.

Requirements

• A V Rising dedicated server
• BepInEx 6 for IL2CPP
• HookDOTS.API
• VampireCommandFramework

RaidForge is server-side. Players do not need to install the mod locally.

This source tree expects the following locally supplied build dependencies:

libs/HookDOTS.API.dll

libs/VampireCommandFramework.dll

Those third-party binaries are intentionally not stored in this repository.

Installation

• Stop the dedicated server and back up its save and configuration directories.
• Install BepInEx, HookDOTS.API, and VampireCommandFramework.
• Copy RaidForge.dll into BepInEx/plugins.
• Start the server once so RaidForge can create its configuration files.
• Stop the server, review BepInEx/config/RaidForge, and enable only the systems you intend to use.
• Restart the server and verify the startup log.

[!IMPORTANT]

If RaidForge controls scheduled castle damage, the active save's ServerGameSettings.json must use "CastleDamageMode": "TimeRestricted". Do not use Always or Never/disabled. RaidForge switches castle damage to Always during its configured window and returns it to TimeRestricted afterward.

The vanilla weekday and weekend castle raid times must also all be set to 00:00. In JSON, that means every StartHour, StartMinute, EndHour, and EndMinute below is 0. Put the real raid windows in RaidScheduleAndGeneral.cfg.

{

"CastleDamageMode": "TimeRestricted",

"PlayerInteractionSettings": {

"VSCastleWeekdayTime": {

"StartHour": 0,

"StartMinute": 0,

"EndHour": 0,

"EndMinute": 0

},

"VSCastleWeekendTime": {

"StartHour": 0,

"StartMinute": 0,

"EndHour": 0,

"EndMinute": 0

}

}

}

Merge these values into the existing file rather than replacing unrelated server settings. They are required for reliable scheduled activation. Zeroing the vanilla times prevents a second raid schedule from overlapping RaidForge.

Server Time and Schedule Offset

The dedicated server machine's local clock is RaidForge's source of truth. RaidScheduleDisplayOffsetHours adds a fixed number of hours to that clock for both schedule checks and command output:

• 0 uses the server clock unchanged.
• A positive value moves RaidForge's schedule clock later.
• A negative value moves it earlier.
• Example: if the server clock is 08:00 and the offset is 2, RaidForge treats the schedule time as 10:00.

Use the offset when the server's clock and the community's desired timezone do not match. RaidScheduleTimeZoneForDisplay i