Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Region Layer

The region layer is the most tactile layer in the entire game. It is where the player experiences matter directly through machines, belts, chassis, terrain, and local hazards.

Primary purpose

This layer teaches the player the operational grammar of the game:

  • extraction
  • routing
  • transformation
  • storage
  • power
  • local defense
  • embodied traversal

It also establishes trust. The player has to believe that local cause and effect are consistent before the game can ask them to think at larger scale.

What belongs in this layer

Typical systems in the region layer:

  • ore fields and extraction nodes
  • furnaces and processors
  • assemblers and modular production blocks
  • belts, pull rails, and local drones
  • local power grids
  • repair and maintenance loops
  • defensive structures and alert beacons
  • chassis bays and sync stations

Desired feel

This layer should feel:

  • material
  • readable
  • noisy
  • constrained
  • personal

The player should sense distance, pathing, congestion, and machine placement as concrete realities.

Region layer gameplay loops

Foundational loop

  1. identify resource access
  2. establish extraction
  3. refine the raw material
  4. route outputs into useful manufactured parts
  5. stabilize power and throughput

Embodiment loop

  1. choose the correct chassis for the job
  2. perform a burst of high-value local work
  3. swap when the local bottleneck changes
  4. automate the task enough that physical presence is less necessary next time

Expansion loop

  1. diagnose the current bottleneck
  2. add infrastructure or redesign a line
  3. restore stability
  4. push output high enough to unlock the next industrial objective

Region layer design constraints

Travel time must matter

The player should feel that moving physically across a factory has meaning. Travel cost is part of why automation and later remote management become desirable.

Layout must tell a story

A region should reveal its history through the factory:

  • improvised early belts
  • later standardized modules
  • emergency patches after damage
  • zones built around natural terrain constraints

Local failure must be legible

If a line starves, floods, browns out, jams, or gets damaged, the player should be able to understand why from what is visible on screen.

Region archetypes

Different regions should encourage different industrial shapes:

  • mineral-rich basin
  • coastline refinery region
  • dense ruin zone with salvage opportunities
  • hazardous Flux-touched region
  • mountain or canyon region with constrained route planning

This helps ensure that a second or third factory is not merely a copy of the first.

Relationship to the rest of the game

The region layer should remain relevant after macro play unlocks.

Later, the player may visit a region to:

  • upgrade a specialized industrial district
  • repair a strategic bottleneck
  • secure a threatened Sync Station
  • add exports for orbital or frontier demand
  • recover after a raid, storm, or logistics collapse