RiftborneIndependent Wiki
Strategy analysis

Objective information asymmetry

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

Objective information asymmetry is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

Enemy objective progress is snapshot-based. A faction can accelerate between spy cycles or deliberately present stale progress. Rotate spies and avoid announcing donation timing.

Why it works

Objective progress observed through espionage is a timestamped snapshot. A coordinated faction can change its position between reports, so uncertainty itself must be included in planning.

Execution

  • Assign repeated observations to named players.
  • Store capture time with every report.
  • Increase refresh frequency as the victory margin narrows.
  • Keep exact friendly contribution timing within the smallest useful group.

Risks and counterplay

  • Duplicate probes waste intelligence capacity.
  • Overconfidence in a stale report can miss a victory push.
  • Excessive secrecy can prevent allies from providing coverage.

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 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.
  3. 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.
  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.