Multiplayer

Organization progression and limits

observedPatch 11.75Build a7b5c7cLive worldReviewed
Patch
11.75
Build
a7b5c7c
Scope
Live-world observation
Reviewed

Organization progression and limits belong to the active world unless the current client evidence proves otherwise. Record the level screen and the action that exposes each gate. Evidence

Progression ledger

Level or state Cost Prerequisite Unlock or limit change Source screen
Current Record Record Record Record
Next Record Record Record Record
Later preview Record only if displayed Record Record Record

Track member capacity, share or funding limits, loan capacity, contract capacity, subsidiary limits, role permissions, cooldowns, and treasury requirements as separate fields. Do not extrapolate a later level from one observed step.

Use Organization screen field guide to preserve provenance and revisit dependent pages when an unlock changes available finance or control actions.

Needs verification: Maximum level, cost curve, unlock schedule, capacity formulas, downgrade behavior, cooldowns, world overrides, and whether limits apply per organization, account, faction, or ownership chain.

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