RiftborneIndependent Wiki
Strategy analysis

Command checklist

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

A recurring command checklist is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

At each meaningful login:

  1. Check inbound fleets, alerts, and faction messages.
  2. Check Astra runway at every garrison.
  3. Spend or route resources before storage caps.
  4. Keep all intended build/training lanes working.
  5. Refresh priority intel.
  6. Re-evaluate travel times, not just map distance.
  7. Ask what the empire should become over the next two to four launch windows.
  8. Tell allies anything that changes their decisions.

Why the order matters

Inbound threats and faction messages come first because they can invalidate every queued plan. Astra and capacity follow because they determine whether assets survive and production continues. Only then should a commander optimize new construction or launches.

Handoff note

Before leaving, record the next completion, next cap, critical arrival, objective change, and any decision an ally may need to make.

Periodic review

Reassess base roles, response-time cells, objective route, and obsolete market commitments. Repetition is valuable only while the checklist reflects the current campaign.

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