Systems Design
Economies, progression, balance, and emergence - the interconnected rules that create depth and replayability.
Entries
| Entry | What it covers |
|---|---|
| Economy & Resources | How value flows through videogames - sources, sinks, and flow |
| Progression Systems | Tracking and displaying player advancement |
| Balance Philosophy | What "balance" means and how to achieve it |
| Emergent Behavior | Complex patterns from simple rules |
Core Insight
Systems design is about relationships between parts, not individual mechanics.
A resource matters because of what creates it, what consumes it, and what it enables. A progression system matters because of what it rewards and what it gates. Balance matters relative to the experience you're creating.
By Framework Concept
| Concept | Systems Application |
|---|---|
| Gesture | Systems shape the feel of playing - scarcity vs abundance, power vs vulnerability |
| The 4 A's | Arc is central - systems unfold over time and create rhythms |
| Aesthetic Heritage | Where your systems vocabulary comes from (board games, economics, simulations, other videogames) |
| Permissions | Systems are Permissions made mathematical - rules about what's allowed, required, and forbidden |
Teaching Sequence
Recommended order for introducing systems concepts:
- Economy & Resources - Concrete and visual. Students can diagram it.
- Progression Systems - Familiar from every RPG. Easy to analyze.
- Balance Philosophy - Requires understanding of context and player experience.
- Emergent Behavior - Most abstract. Requires understanding of systemic interaction.
Common Misconceptions
"More systems = more depth"
Students often add systems without purpose. Complexity isn't depth. Every system should serve the core experience.
"Balance = equality"
Balance doesn't mean everything is equal. It means the experience works as intended. Asymmetric balance is often more interesting than symmetric.
"Emergence just happens"
Emergence is designed, not accidental. You create the conditions for emergence through careful system interaction. Random systems produce noise, not emergence.
Analysis Exercise
Map a videogame's economy:
- Identify all resources (currency, items, time, attention)
- Draw sources (where resources come from)
- Draw sinks (where resources go)
- Identify feedback loops (positive and negative)
- Find the pressure points - where does the system create tension?
Creation Exercise
Design a two-resource economy:
- Resources must be interdependent (you need A to get B, B to get A)
- Include at least one meaningful choice
- Playtest: does it create interesting decisions or degenerate into one strategy?
Systems Thinking Origins
Systems design draws from cybernetics, economics, and ecological modeling. Videogames are simulations, and simulation inherits these disciplines.
The key insight: behavior emerges from structure. Change the relationships, change the behavior. Individual components matter less than their connections.
Feedback Loops and Player Psychology
Positive feedback loops (success breeds success) create momentum and drama. Negative feedback loops (rubber banding) create tension and catch-up.
The balance between these loops shapes the emotional arc of play. See Player Psychology for more.
The Simulation Gap
All systems are simplifications. The gap between your simulation and reality (or player expectation) creates the design space.
This gap isn't a flaw - it's where videogames live. The question is whether your simplifications serve your design intent.
References
- Adams, Ernest & Dormans, Joris. Game Mechanics: Advanced Game Design (2012)
- Koster, Raph. A Theory of Fun for Game Design (2004) - patterns in systems
- Salen, Katie & Zimmerman, Eric. Rules of Play (2004) - foundational systems theory
- Meadows, Donella. Thinking in Systems (2008) - general systems theory
Related Sections
- Player Psychology - feedback loops are the engine of systems behavior
- Permissions - systems shape what's possible
- Case Studies - systems in action