Automation
Player-built machines take over tasks previously done by hand: miners harvest, belts move, assemblers craft, and eventually the factory runs itself while the player designs the next layer. Automation's loop is uniquely satisfying because it is meta-progression of labor — every system automated frees attention for a bigger problem, and the game continuously graduates the player from worker to engineer to architect. Designers use it to create self-directed play (goals emerge from bottlenecks) and near-endless scaling. The design foundations: manual-first pacing (hand-crafting must be tedious enough to motivate automating but tolerable enough to bootstrap), legible machine states (starved, blocked, running — readable at a glance across thousands of machines), and interfaces for copying and scaling proven designs (blueprints). Factorio and Satisfactory differ mainly in dimension and friction, not in loop. Pitfall: automating away the gameplay — if the endgame is watching a solved factory idle, the game must keep injecting new demands (research sinks, threats, exponential goals) to re-open the puzzle.
- Dev effort: Large
- Timing: Real-time
- Common in: automation
Seen in
- Factorio
- Satisfactory