RiftborneIndependent Wiki
Strategy analysis

Separate public plans from launch orders

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

Separate public plans from launch orders is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

Maintain a broad faction plan (“secure western Inner Keystone”), but share exact fleet composition and launch time only with participants. Assume enemy spy snapshots and social leakage exist.

Why it works

A faction needs shared intent but does not need every operational detail exposed to every observer. Separating objective from execution reduces the value of social leakage.

Execution

  • Publish the broad objective and support needs.
  • Keep exact composition, route, and launch time with participants.
  • Give nonparticipants clear defensive or logistics tasks.
  • Reveal more only when coordination benefit exceeds information risk.

Risks and counterplay

  • Too much secrecy causes duplicated action.
  • A small planning group can become a single point of failure.
  • In-game observations may reveal the operation anyway.

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 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. Current objective and victory implementationThe current client defines an Origin Wormhole victory at level 100 and a Valor victory at 250,000 faction Valor. Keystones generate Valor through Valor Conduits; current objective sites include Inner, Border, and Outer tiers.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of SpecialSiteSystem, VictoryConditionTracker, and the victory Codex screen.
  5. 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.
  • Build a logistics spineBuild a logistics spine is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.