RiftborneIndependent Wiki
Strategy analysis

Fight campaigns, not battles

strategyPatch 11.73Reviewed

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

Evidence status — Strategy: This page derives recommendations from confirmed mechanics. It does not describe an official guarantee.

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.

References

  1. Installed Riftborne gameplay guide, patch 11.73Bundled with the local Steam build dated 22 July 2026.
  2. Official Riftborne gameplay guideOfficial reference; some values may predate patch 11.73.
  • 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.