Economy

Rare metals, mining outposts, Noctmarks, and SPUs

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

Rare-metal sites produce materials used by the SPU system. The current 11.75 data table exposes SPU targets including ship classes, economy, capacity, travel, cargo, siege, tracking, evasion, upkeep, research, and intelligence. Evidence

Exact mining chances, delivery timing, recipes, and installed bonuses should be read from the active site and SPU screens. They can depend on the campaign and current augmentation, so this wiki does not publish a universal crafting schedule.

For planning, compare an SPU’s displayed marginal effect with the fleet or colony that will actually use it; a high-tier bonus on an inactive system creates no immediate tempo.

Separate site from augmentation

A rare-metal site is the production source; an SPU is an installed improvement with a displayed target and effect. Owning a site does not automatically mean the resulting augmentation belongs on the nearest or largest fleet.

Workflow

Eligible rare-metal site
        |
        v
Mining outpost and site actions
        |
        v
Rare-metal/SPU inventory -> crafting or transmutation
        |
        v
Delivery state -> eligible recipient -> installed effect

At every arrow, open the current screen and confirm what moved, what remains committed, and which recipient is named. This prevents materials in progress from being mistaken for available inventory and completed items from being mistaken for installed effects.

Allocation questions

Which fleet or colony uses the affected system most often? Does the improvement help the current objective? Is the recipient likely to remain active and supplied? Would a lower apparent bonus create more immediate tempo elsewhere?

Evidence boundary

The installed table confirms the available effect categories. Recipes, chance, delivery schedule, tier, and the final installed value must come from the current site and SPU screens before they are treated as facts. Evidence

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