Getting started

Opening priorities

confirmedPatch 11.75Build a7b5c7cCore rulesReviewed
Patch
11.75
Build
a7b5c7c
Scope
Core rules
Reviewed

Opening priorities are the early investments that prevent capped production, Astra failure, and directionless construction. Evidence

  1. Queue culture-specific central infrastructure with a deliberate unlock in mind.
  2. Add resource production and enough storage that the next login will not find capped stores.
  3. Stabilize Astra before training a meaningful garrison.
  4. Scout the local ring and measure routes, including wrapped map edges.
  5. Decide whether the first outpost is economic, positional, or rare-metal focused.
  6. Build the shipyard family that supports the selected base role.
  7. Inform the faction of the empire’s location, active period, and intended role.

Three strategic shapes are coherent, but their exact build order depends on the active campaign:

  • Macro/outpost: pursue the next verified expansion unlock, then support the new site with capacity and a defensible route.
  • Raid tempo: prioritize the displayed shipyard prerequisites, intelligence, cargo-capable fleets, and replacement income.
  • Fortress/core: preserve Astra runway, add the culture-specific defensive structure, and keep reinforcement travel short.

The bad opening is not a specific build order. It is buying whatever happens to be affordable without deciding what the base is becoming.

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