RiftborneIndependent Wiki
Strategy analysis

Market capital lock

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

Market capital lock is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

Cargo ships are reserved by live offers and trade legs travel. An attractive offer can immobilize a trader’s capacity. Post only with a liquidity plan; exploit opponents who tie up all cargo by pressuring elsewhere.

Why it works

Market activity competes with military logistics for cargo and attention. A profitable offer can still be harmful if it reserves the capacity needed for emergency movement.

Execution

  • Separate trade cargo from the emergency reserve.
  • Check current obligations before posting an offer.
  • Set a condition for cancelling or declining low-priority trades.
  • Track arrival time rather than treating acceptance as immediate liquidity.

Risks and counterplay

  • World settings can change fees, travel, and reservation behavior.
  • An opponent may pressure the region while cargo is committed.
  • Over-reserving for emergencies can also leave productive trade idle.

Assumptions and ruleset

This is strategic analysis, not a guaranteed outcome. It assumes the linked mechanic pages still match the active build and that current-world roster, modifiers, travel times, intelligence age, and opponent response have been checked before commitment.

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 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.
  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.
  • Advanced tactics and edge casesAdvanced tactics use documented interactions and edge cases to create advantages that are not obvious from headline statistics.
  • Astra trapAstra trap is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.
  • Shield-grinding sacrificial attacksShield-grinding sacrificial attacks is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.
  • Hangar feintHangar feint is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state.