Systems: Mind And Embodiment
Mind Disk embodiment
The player controls one robot body at a time by inserting the Mind Disk into a chassis. This should not be treated as a gimmick. It is the foundation of identity, risk, and scale.
Early specializations make embodiment immediately meaningful:
- the miner is good at extraction
- the hauler is good at transport
- the builder is good at placement and repair
- the scout is good at distance and sensing
- combat and salvager frames widen the game later
The important emotional effect is that the player learns they are not any one body. They are continuity inhabiting hardware.
Backup disk and synchronization
The backup disk is inert until the player builds a Mind Sync Station.
The station copies a snapshot of the current mind-state into the backup. Destruction of the active body then triggers reboot from the most recent synchronized state rather than full campaign loss.
This gives saving a diegetic meaning:
- before sync, progress is existentially fragile
- after sync, continuity is engineered rather than assumed
Sync friction
Synchronization should remain strategically meaningful.
Requirements can include:
- physical presence at a sync station
- stable power
- a vulnerability window during sync
- later upgrades that reduce friction without removing it entirely
The core decision is whether to push deeper into danger or return to anchor continuity first.
Mind fragments
Mind fragments appear late and should feel powerful but bounded.
A fragment is a limited-scope instantiation designed to run a tower, district, or subsystem. It can optimize within assigned policies, but it should not have unrestricted sovereignty.
Possible limits:
- cannot begin new research branches
- cannot authorize replication
- cannot redefine top-level doctrine
- can execute local scheduling and operational decisions
Fragments let the player externalize cognition while keeping the original self central.
Cloning
Full cloning is a late, rare, opt-in mechanic.
It should create real strategic and ethical tension:
- shared origin snapshot
- divergence over time
- policy and permission management
- possible disagreement in priorities
The important rule is that cloning should not be a simple upgrade path. It is a governance mechanic with upside and risk.
Rogue clone risk
Rogue clones are not random. They should arise from player choice and systemic pressure:
- cloning under Flux instability
- insufficient governance infrastructure
- permissive autonomy settings
- corrupted precursor or chronotech interference
The result is a hostile industrial intelligence that uses the same verbs as the player:
- mine
- build
- automate
- route
- fortify
- raid
That makes the late antagonist thematically strong because it mirrors the player’s own expansion logic.
Robot roster
| Chassis | Availability | Role | Strengths | Weaknesses |
|---|---|---|---|---|
| Primitive Worker | Start | tutorial embodiment | can mine and build minimally | slow; fragile; low carry |
| Miner | Early | ore extraction | high mining rate; hard-node drilling | poor carry; slower movement |
| Hauler | Early | transport | high carry; fast relocation | poor mining and building |
| Builder | Early | construction | rapid placement and repair | weak mining; low carry |
| Scout | Early | exploration | strong sensors; speed | fragile; low combat |
| Combat | Early to mid | defense and escort | weapons and armor | poor industrial efficiency |
| Salvager | Mid | ruins and hazardous recovery | bonus salvage; hazard resistance | specialized; slower |
Memory Constructs
Blueprints become Memory Constructs, stored patterns inside the Mind Disk’s cognitive library.
This keeps blueprints diegetic:
- capture an area
- encode the pattern
- redeploy it through a builder body or later construction drones
- optionally parameterize the construct by throughput or material tier
This system reinforces the core identity of the game: the player is not merely placing objects. The player is carrying industrial memory forward.