P3: Reflection

Before designing a systems game, I imagined that it would be a largely mathematical process, involving calculations, balancing resources, and creating symmetry between different players and objects within the system. I expected much of the design work to focus on how resources flow and how to ensure that the game is balanced. However, through designing Data-Centered, I learned that a mathematically balanced system does not necessarily make an interesting game, nor does it necessarily represent reality well.

One of the most important decisions we made was to introduce more asymmetry into the game. In our earlier versions, the gameplay felt too linear and repetitive. Each round followed a similar pattern, and the different roles—government, NGOs, and tech companies—did not feel sufficiently distinct. Although the system might have been easier to balance mathematically, it failed to capture the different powers and relationships between these actors in the real world. We therefore introduced special abilities for each role. For example, tech companies could build private data centers, governments had action cards whose effects lasted for several terms, and NGOs could disrupt or deconstruct data centers. This helped me understand the concept of “fruity” game balance, which I had not encountered before. Previously, I was only familiar with transitive and intransitive relationships in game balance. I realized that balance does not have to mean giving everyone equal resources or equivalent abilities. Instead, giving players distinct powers can create more interesting interactions while also modeling the inequalities and tensions within a real-world system.

Players had fun joking about the titles – even though its not directly related to winning.

Another thing that surprised me was what players actually found fun. Because our game was resource-heavy, I expected players to derive most of their enjoyment from strategizing, calculating, and optimizing their decisions. However, during playtesting, I noticed that players spent a surprising amount of time reading the flavor text, joking about bureaucracy and tech companies, and discussing how the game reflected real-world issues. They also seemed to enjoy simply attacking or disrupting one another, even when those actions were not necessarily the most strategically optimal.

I had underestimated the importance of flavor text and thematic design. When I play games myself, I tend to focus on winning, often overlooking details that do not directly contribute to my strategy. Watching others play reminded me that fun can emerge from many different sources, including humor, role-playing, social interaction, and connections to players’ lived experiences. I learned that designing a systems game is not just about creating a mathematically coherent model, but also about making that system meaningful and enjoyable to inhabit.

 

About the author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.