Strategy analysis

Hangar feint

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

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

Only stationed ships defend. A base can appear wealthy but weak because hulls are hangared—or can invite an attack and station them before arrival.

Counter: refresh intel near impact and model enemy reaction time.

Why it works

Because only stationed ships defend, the visible defensive state can change when stored hulls are reassigned. The tactic exploits the delay between an attacker’s observation and impact.

Execution

  • Measure the attacker’s travel time and likely last intelligence refresh.
  • Keep the intended defenders available rather than committed elsewhere.
  • Station them only when doing so will not create an upkeep crisis.
  • Prepare a second response in case the attacker recalls.

Risks and counterplay

  • Fresh espionage can expose the change.
  • Astra limitations can make the apparent reserve unusable.
  • Holding too much in reserve sacrifices pressure elsewhere.

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.