Economy

SPU crafting and delivery

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

SPU crafting converts rare-metal-system inputs into an augmentation intended for a displayed target or inventory. The current data confirms many possible effect categories, but the active screen remains authoritative for the recipe and result. Evidence

Safe crafting procedure

  1. Open the relevant rare-metal or SPU screen.
  2. Record the selected recipe or result category.
  3. Read every required input and compare it with uncommitted inventory.
  4. Confirm the recipient or delivery destination.
  5. Read the estimated completion or delivery state.
  6. Commit only after the preview matches the intended use.
  7. Return after completion and verify where the item or effect appears.

Inventory states that look similar

Materials on hand, materials committed to an action, a completed but undelivered result, and an installed effect are different states. When an expected item seems missing, check the current action, delivery destination, and recipient before reporting a loss.

Worked decision

Suppose one result affects travel and another affects a ship class. The useful comparison is not which label looks stronger; it is which eligible recipient will use the effect during the next objective window. Keep the conclusion strategic until the current screen supplies the exact values.

Needs verification

Universal recipes, odds, completion times, cancellation refunds, and delivery delays are not established by the available core evidence. Capture the complete confirmation panel if these details are needed for a future verified table. 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. 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.
  3. 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.