RiftborneIndependent Wiki
Strategy analysis

Fight campaigns, not battles

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

Fight campaigns, not battles is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

A multiplayer attack should answer:

  • What changes on the map if we win?
  • What replaces our losses?
  • Can the target be reinforced before impact?
  • Is siege protected enough to convert the win?
  • Who holds our bases while fleets are away?
  • What is the diplomatic cost?

If those answers are missing, raid, spy, contract, or wait.

Why it works

A favorable report can still be a strategic loss when replacement time, travel exposure, or the absence of siege leaves the map unchanged.

Execution

  • Write the desired map outcome before composing the fleet.
  • Price replacement and return exposure alongside the attack.
  • Assign defense for every launch base that will be weakened.
  • Define the follow-up action and the condition that cancels it.

Risks and counterplay

  • Tactical success can strand the fleet far from the next objective.
  • Allies may optimize for different outcomes unless the purpose is explicit.
  • Repeated commitment can turn sunk cost into campaign failure.

Assumptions and ruleset

This is strategic analysis, not a guaranteed outcome. It assumes the linked mechanic pages still match the active build and that current-world roster, modifiers, travel times, intelligence age, and opponent response have been checked before commitment.

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 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.
  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.
  • Official multiplayer strategyOfficial multiplayer rewards coordinated logistics, current intelligence, response-time organization, and objective timing.
  • Join a faction and become legibleJoin a faction and become legible is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.
  • Organize by response timeOrganize by response time is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.
  • Separate public plans from launch ordersSeparate public plans from launch orders is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.