RiftborneIndependent Wiki
Strategy analysis

Build a logistics spine

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

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

Use backline production, forward launch hubs, and fortified transfer nodes. Keep slow siege behind the line until the target is confirmed. Pre-position cargo and Astra before the war, because market travel after the alarm is often too late.

Why it works

A logistics spine reduces the number of long, fragile movements required to keep a front supplied. It is a network of production bases, transfer points, and launch bases chosen by actual travel time.

Execution

  • Identify the front’s likely launch and fallback points.
  • Place cargo and Astra behind the exposed edge, not on it.
  • Move siege only after intelligence establishes a structural target.
  • Give each node a named owner and resupply condition.

Risks and counterplay

  • A single obvious transfer node becomes a high-value target.
  • Forward stockpiles create losses if the front collapses.
  • Combining every fleet at one hub can leave the rear undefended.

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 economy and storage implementationProduction, storage capacity, upkeep, hidden-resource, and transmutation behavior is taken from the executable paths used by the running client.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of BuildingConfig and EconomySystem.
  3. 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.
  4. 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.
  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.
  • 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.