RiftborneIndependent Wiki
Strategy analysis

Veil deniable-raider base

strategyPatch 11.75Build a7b5c7cStrategyReviewed
Patch
11.75
Build
a7b5c7c
Scope
Strategy analysis
Reviewed

Veil deniable-raider base is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

Concentrate the active roster’s espionage, cargo, and travel advantages at one launch hub. The result is a selective raiding base whose composition can change quickly after fresh intelligence. Named abilities and diplomatic modifiers must be confirmed in the active world before being included in the calculation.

Why it works

A specialized launch base can turn current information, cargo, and travel advantages into selective economic pressure without committing the entire empire.

Execution

  • Verify the active Veil roster and diplomatic modifiers.
  • Choose a hub by actual route coverage.
  • Keep intelligence and raid cargo available together.
  • Move or stand down when the hub becomes predictable.

Risks and counterplay

  • Repeated launches expose the hub.
  • Weak Astra or replacement income makes raiding self-defeating.
  • Unverified named abilities must not enter the calculation.

Assumptions and ruleset

This is strategic analysis, not a guaranteed outcome. Verify the linked mechanics and the active world’s roster, modifiers, travel times, intelligence age, and opponent response before committing.

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 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.
  4. Active multiplayer-world boundaryThe multiplayer operator owns the world seed, pacing, simulation time, factions, global modifiers, and ship roster. World-specific values must therefore be labeled separately from core rules.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Current multiplayer client contract and read-only world/session telemetry.
  • Advanced tactics and edge casesAdvanced tactics use documented interactions and edge cases to create advantages that are not obvious from headline statistics.
  • Astra trapAstra trap is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.
  • Shield-grinding sacrificial attacksShield-grinding sacrificial attacks is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.
  • Hangar feintHangar feint is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.