RiftborneIndependent Wiki
Strategy analysis

Choosing a victory route

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

Victory-route selection compares a faction’s Origin access, Keystone network, defensive coverage, resource throughput, and information position. Evidence

Prefer the Origin Wormhole route when the faction can hold the central colony, sustain both capacity prerequisites, and protect a single highly visible construction project.

Prefer the Valor route when the faction can control and supply Keystones, grow Valor Conduits, and defend a distributed objective network long enough to reach the active-world threshold.

The strongest posture can threaten both routes so opponents cannot concentrate every response on one site. Confirm the live victory panel before committing; the operator owns campaign settings. Evidence

Compare concentration and distribution

The Origin path concentrates progress and defense at one visible central colony. The Valor path distributes control and construction across a Keystone network. Compare which geometry the faction’s logistics and active coverage can sustain.

Decision inputs

Record ownership, friendly and hostile arrival times, prerequisites, capacity, resources, garrisons, and the age of enemy observations. Separate confirmed values from assumptions.

Preserve flexibility

Early staging and intelligence can support either route. Commit when one path offers a defensible next milestone, then communicate its abort condition faction-wide.

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 culture-specific building namesThe current client maps Astraean storage to Solvault and Heliovex, Varkon storage to Skarncache and Voltforge, and Veil storage to Nyxvault and Gloamwell. Astraean static attack infrastructure is named Solis Battery.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of BuildingNamingSystem in the installed client.
  4. Current building effectsThe first culture-specific storage building adds capacity for Vulkron, Aurelite, and Deuterium; the second adds Astra capacity. Solis Battery adds flat attack against light and heavy hulls and remains active while standing.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Read-only inspection of BuildingConfig.GetEffects and the current Codex renderer.
  5. 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.
  6. 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.
  7. 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.
  8. Installed 11.75 data tablesDirective and SPU tables were read from the same installed 11.75 build. Values are used only where the current table exposes them directly.Patch 11.75 · build a7b5c7c · verified 2026-07-30 · Content/Data/directive_paths.csv and Content/Data/spu_bonuses.csv.
  9. 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.
  • Objectives and the late gamePatch 11.75 exposes two standard progress tracks: an Origin Wormhole victory and a faction Valor victory generated from controlled Keystones.