Strategy analysis

How to value a tile

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

Tile value is determined by yield, travel time, reinforcement access, and exposure rather than yield alone. Evidence

Rank a target on four axes:

  1. Yield: production/terrain bonuses and rare-metal table.
  2. Reach: travel time from a real shipyard, not visual distance.
  3. Support: who can reinforce and supply it?
  4. Exposure: how many hostile launch bases can reach it before your faction can?

A modest tile inside a reinforcement triangle is often worth more than a spectacular tile hanging alone in enemy space.

Why it works

The best tile is the one that improves the empire’s network. Raw yield matters, but reach, support, and exposure determine whether that yield remains usable during war.

Execution

  • Record the tile’s displayed effects and allowed settlement type.
  • Measure routes from current production bases and allies.
  • Count hostile launch options inside the response window.
  • State the tile’s role before spending the colonization hull.

Risks and counterplay

  • A high-yield isolated tile can become a permanent escort burden.
  • Visual proximity is unreliable on a wrapped map.
  • The wrong settlement type can block the infrastructure the plan expects.

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