lore / World / EN
Machine doctrine
Observation, testing, production and deployment give the threat its logic.
This archive entry may contain campaign spoilers.
Synthera develops designs through a six-step cycle.
- Observation: sensors record hits, routes and how far machines reached; communications carry available reports.
- Comparison and trials: computing centers compare models across fronts. A failed column can still produce useful information.
- Selection: successful armor and control designs are chosen for later use.
- Production and repair: factories build with real parts, consuming Energy and time; servicing returns some damaged machines to use.
- Deployment: terminals load columns and relays distribute approved control models.
- New reports: the next battle begins the cycle again.
Sensor loss limits what she knows. Cutting supplies constrains future production but does not erase completed machines or stockpiles. An improved machine does not appear instantly merely because a previous assault failed.
This learning belongs to the fiction. The game's enemy rosters, entry waves, routes and scaling are authored and deterministic. It does not train on your tower layout or permanently learn a counter from your previous attempt.
Fast units test gaps in sustained fire. Aircraft demand the right weapon layer. Vaulters force changes between ground and air. Armored platforms absorb fire, reconstructors punish interrupted damage, and Overseers coordinate mixed forces. The Machine Archive explains all eighteen types.