Overview
Game systems fail in combination. The economy designer reduces monster Gold drops by 20% to fight inflation. The combat designer doesn't know about this change. The player now earns 20% less Gold from combat, but the combat system's damage output and enemy HP haven't changed — so the player spends the same time in combat for 20% less reward. The combat feels unrewarding. The player avoids combat, which means they earn less XP, which means the progression system slows down. The economy change cascaded through combat into progression — three systems affected by one change, only one of which was intentional.
The System Interaction Balance prompt builds cross-system balance frameworks with three properties: (1) system coupling map — every interaction between game systems is documented (economy→combat: Gold drops fund equipment purchases; combat→economy: kill rate determines Gold generation rate; progression→combat: level determines damage output; combat→progression: kills provide XP), (2) cascade prediction — when a parameter changes in one system, the framework predicts which other systems are affected and how, before the change is implemented, and (3) isolation testing — each system can be tested in isolation with mocked inputs from other systems, ensuring that a change in one system doesn't break another system's assumptions.
What you get: - System coupling map with interaction directions and strength - Cascade prediction template for cross-system impact analysis - Isolation testing specification with mock input definitions - System boundary definitions (what each system owns vs. depends on) - Cross-system regression test suite - System interaction audit checklist
Built for: technical designers, systems architects, and lead designers who need games where systems work together — not games where systems fight each other.