RiftborneIndependent Wiki
Getting started

Match structure and victory conditions

confirmedPatch 11.75Build a7b5c7cCore + live worldReviewed
Patch
11.75
Build
a7b5c7c
Scope
Core + live world
Reviewed

A Riftborne match is governed by tempo: the rate at which an empire converts production, movement, and information into useful options. Evidence

Patch 11.75 presents two standard victory tracks:

  • Origin Wormhole: hold the Origin at (0,0) and raise its culture-specific Wormhole to level 100.
  • Valor: generate 250,000 faction Valor through Valor Conduits on controlled Keystones.

The active multiplayer operator owns world settings and may change campaign parameters, so the live victory panel is authoritative. Evidence

Between those objectives, good play means maintaining capacity headroom, protecting Astra-supported garrisons, keeping useful queues active, shortening response paths, and refreshing intelligence before committing a fleet.

Three layers of play

The economy layer creates resources and queues. The operational layer converts them into movement, intelligence, defense, and replacement. The objective layer converts sustained map control into victory progress. Weakness in any layer eventually limits the others.

Information horizon

Distinguish current UI facts, recent observations, and forecasts. Longer plans need checkpoints where live state replaces assumptions.

Multiplayer consequence

Persistent time makes coverage and handoffs strategic resources. Clear response ownership can outperform larger assets that arrive separately or too late.

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