Design game systems that work together
Start from your core loop, give each system its own branch, and look for exploits and broken interactions before you build.
See it in action
A design document for a roguelike whose dungeon remembers your previous runs, with the core loop, the memory mechanic and the boss adaptations worked out.
How it works
Start with the core loop or the player fantasy. Each system gets its own branch, and the model keeps the core loop in context under every one.
-
State the core loop. Ask what the player does, why they do it again, and what changes each time.
-
Add a branch per system. Combat, economy, progression and narrative each get a branch. Under each, ask for specifics such as damage formulas, currency sinks or skill trees.
-
Mark the player’s choices. Under any system, ask where the player makes a real choice and whether each option changes what happens next.
-
Look for exploits. Under the economy branch, ask how a player could break it. If hoarding one resource wins every time, you find out before you write any code.
Where systems meet
A branch only sees the nodes above it, so a question under combat does not know what you decided about the economy. To ask how two systems interact, ask under the core loop, where both are named, or ask Milo, the assistant built into the map, which reads the whole map. Milo is on the Promptmaps and Lifetime plans.
Example
Say you are designing a city-builder where citizens can vote to override the mayor. One branch works out the opinion system: what makes citizens happy, how factions form, when protests start. Another works out building: resource chains, zoning and roads. Under the core loop, you ask what happens when a factory goes up next to homes, and the answer shows that approval is the resource the player really spends.