RiftborneIndependent Wiki
Warfare and intelligence

Siege

confirmedPatch 11.75Build a7b5c7cCore rulesReviewed
Patch
11.75
Build
a7b5c7c
Scope
Core rules
Reviewed

Siege is the building-damage stage of a successful attack. Surviving siege capability and the selected target determine whether building levels are removed. Evidence

Siege is not interchangeable with raid cargo or ordinary combat power. A fleet that wins the ship battle can still fail to achieve its structural objective if too little siege capability survives.

Use the current simulator with the exact target building and infrastructure. World-specific building costs and modifiers make a universal “siege per level” table unreliable.

Structural objective

Select the building because its removal changes the defender’s next decision: production, capacity, logistics, defense, static attack, shipbuilding, siege support, or objective progress. “Any damage” is not a sufficient campaign objective.

Fleet construction

The combat line must survive long enough for siege capability to remain after the ship battle. Compare alternate compositions in the current simulator and specify the target building. More siege at launch is not automatically better if the supporting fleet collapses.

Multi-wave planning

Rebuild the fixture after every impact. Integrity, stationed ships, building levels, resources, and reinforcements can all change before the next wave.

Evidence

Sanitized transcripts from the current client. Raw player captures remain private.

  1. Installed client identityThe installed Windows client reports patch 11.75, build a7b5c7c, built 2026-07-31 15:16:13 UTC.Patch 11.75 · build a7b5c7c · verified 2026-08-01 · Riftborne.exe --build-info and Content/build_info.json.
  2. Current economy and storage implementationProduction, storage capacity, upkeep, hidden-resource, and transmutation behavior is taken from the executable paths used by the running client.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of BuildingConfig and EconomySystem.
  3. Current culture-specific building namesThe current client maps Astraean storage to Solvault and Heliovex, Varkon storage to Skarncache and Voltforge, and Veil storage to Nyxvault and Gloamwell. Astraean static attack infrastructure is named Solis Battery.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of BuildingNamingSystem in the installed client.
  4. Current building effectsThe first culture-specific storage building adds capacity for Vulkron, Aurelite, and Deuterium; the second adds Astra capacity. Solis Battery adds flat attack against light and heavy hulls and remains active while standing.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of BuildingConfig.GetEffects and the current Codex renderer.
  5. Current fleet and movement implementationFleet role, movement, infrastructure, and roster statements are limited to behavior exposed by the current client implementation and Codex.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of ShipTravelSpeedSystem, ShipInfrastructureSystem, and Codex ship screens.
  6. Current combat, raid, siege, and espionage implementationPublished combat statements are limited to behavior used by the current CombatSystem and the Codex. Power is an estimate rather than a fixed conversion from ship count.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of CombatSystem and SiegeTargetCatalog.
  • Raids, shields, siege, and spiesRaids, shields, siege, and spies is part of Riftborne’s warfare and intelligence system and is documented here for patch 11.75.
  • Raid ceilingRaid yield is limited by surviving cargo capacity, visible target resources, and raid-loot modifiers.
  • Shield integrityDefensive-structure integrity scales its combat contribution and can be reduced by direct attacks separately from building-level siege damage.
  • EspionageEspionage missions use Intelligence hulls to obtain time-sensitive information about hostile bases and objectives.