RiftborneIndependent Wiki
Strategy analysis

Tracking cap efficiency

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

Tracking cap efficiency is a strategy pattern derived from documented Riftborne mechanics and should be evaluated against the active world state. Evidence

Tracking/evasion edge clamps at ±20%. Once you hit the cap against the expected target, more tracking has no direct power benefit in that matchup. Spend the next augmentation slot elsewhere.

Why it works

Tracking investment has diminishing decision value once the current matchup reaches its implemented edge limit. Additional investment should be judged by whether it helps a different expected opponent.

Execution

  • Identify the target class and current evasion.
  • Confirm the effective edge in the current preview.
  • Compare the next tracking improvement with attack, defense, cargo, speed, or upkeep alternatives.
  • Retest whenever the opposing mix changes.

Risks and counterplay

  • A capped matchup against one fleet may be uncapped against another.
  • A roster update can change the comparison.
  • Aggregate power may hide which target class receives the benefit.

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.