Case Study 1: StarCraft II's Balance Council — Democratizing Balance in the Pro Scene

In 2022, Blizzard did something almost no major studio had ever done: it handed the keys to its flagship competitive game's balance to a council of community members. Not consultation — actual decision-making authority. The StarCraft II Balance Council, formed in mid-2022, became the body responsible for proposing, debating, and shipping the balance patches that shaped the competitive meta of one of the longest-running RTS games in history. It was an unusual experiment, and looking at how it went teaches us things that are hard to learn anywhere else about who balance is for, who is qualified to do it, and what happens when a corporation that no longer has the bandwidth to balance its own game tries to get the community to do the work instead.

The setup is worth understanding. StarCraft II launched in 2010, peaked as a competitive title around 2012-2014, and gradually moved out of Blizzard's primary attention as the company shifted focus to Overwatch, Hearthstone, and World of Warcraft. By 2020, the dedicated multiplayer team was a skeleton crew. The game's pro scene — Korean teams, European leagues, the global circuit — kept playing, but the patch cadence slowed to a near-halt. The community could see Blizzard had run out of attention to spare.

The Balance Council was the structural answer. Blizzard partnered with ESL (the tournament organizer) and a rotating roster of pro players, casters, and community figures to form a body that would propose balance changes. The names rotated, and at various points included pros like Maru (one of the greatest Terrans of all time), PartinG (legendary Protoss), Reynor (top European Zerg), and casters and community fixtures like Avilo, who had a colorful history of balance arguments going back a decade. The Council would convene, debate, draft proposed changes, vote, and submit the result to Blizzard. Blizzard would implement the patch.

This is where the trouble started.

The Old Tensions, Now Internal

StarCraft II has three races — Terran, Zerg, Protoss — and the competitive community has spent fifteen years arguing about which race is overpowered at any given moment. The arguments are real. The arguments are also tribal. Every Terran player privately believes Terran is balanced or weak; every Zerg player believes the same about Zerg; every Protoss player about Protoss. Race loyalty is a sociological constant in the StarCraft community, and it is not fully rational.

Blizzard's old balance team had to navigate this politely from the outside. They could be wrong, but they could not be accused of bias toward their own race. The Balance Council, made up of pros from each race, internalized the bias. Now the same arguments that played out on Reddit for a decade played out inside the room where decisions were made. Avilo, a longtime Terran advocate, would propose Zerg nerfs. Zerg players would object. Protoss players would say that whatever the proposal was, it should also include a Protoss buff. The pattern was: every race wants to be slightly stronger; every race wants the other races slightly weaker; finding a stable consensus is hard, and the resulting patches often tried to please everyone by making symmetric changes that did not actually solve anything.

The community joke became "nerf Terran, buff Zerg, repeat forever," reflecting a perception (held more by Terrans than by anyone else) that the council was systematically pushing Terran down. Whether the perception was accurate is debatable; some patches were Terran-heavy, others Zerg-heavy, and the actual win-rate data fluctuated within a normal range. But the perception of bias became its own balance problem, because in a competitive scene, perceived fairness matters as much as actual fairness for keeping the player base engaged.

A different problem emerged from the gap between pro play and ladder play. The Council was made up almost entirely of top-tier players — grandmasters and pros. Their experience of the game was at a skill level the vast majority of players will never reach. When the Council proposed a change to address a degenerate strategy at the GSL level, the change often hit the ladder differently. A nerf to a unit that was problematic in a top-100 mirror-matchup might wreck the unit's viability for a diamond-tier player who relied on it as a crutch. The Council was aware of this, but the data they had access to was still dominated by their own experience, and the patches reflected that skew.

What Worked

Despite the friction, several things about the Balance Council experiment worked, and they are worth noting because they generalize to small studios in ways the negative lessons do not.

Credibility within the community. When the Council shipped a patch, the community knew real pros had touched it. The criticisms changed in character — instead of "Blizzard doesn't understand the game anymore," the criticisms became "the Council got this wrong because of Race X bias." That is a different conversation, and a more productive one. People can argue against a Council member's specific reasoning. They could not argue against an anonymous Blizzard committee in the same way.

Faster patch cadence. The Council was able to propose changes more frequently than Blizzard's reduced internal team could have alone. The implementation lift on Blizzard's side was relatively small — once the Council agreed on numbers, applying them to the game was a few hours of work. The bottleneck moved to the deliberation, which was a community-driven process.

Visible reasoning. Council deliberations were partially public (some on Discord, some leaked, some described in casters' streams). The community could see the arguments being made for and against changes. This made the philosophy of balance changes visible in a way that Blizzard's internal black-box decisions never had been. Players who disagreed with a change at least understood the case for it.

Pro scene engagement. Pros who would otherwise have quietly resented changes they disliked were now invested participants. Even the pros who lost the votes still had a seat at the table. Engagement is itself a form of community management; the Council made the most influential players feel that the game was theirs to shape, which kept them invested in its longevity.

What Failed

Lack of formal data infrastructure. Blizzard's internal balance team had access to detailed match data — millions of ladder games per month, segmented by rank, race, matchup, map. The Council, while informed by personal experience and tournament results, did not have the same systematic access. Decisions that should have been data-driven were sometimes vibes-driven, because the data infrastructure was not made available in the form the Council needed. This is a structural problem: if you want a council to make data-informed decisions, you have to give them the data.

No accountability mechanism. When a patch landed badly, who was responsible? The Council voted; Blizzard implemented; the community blamed everyone and no one. There was no equivalent of a lead designer who could be held responsible for outcomes and required to explain them. Distributed responsibility means distributed accountability, which means slow learning when changes go wrong.

Race politics dominated. The pattern was depressingly predictable. Council members representing each race advocated for their race. Compromises were often "everyone gets a small adjustment" rather than "the change that the data says should happen." The structural incentive of the Council was to satisfy its members, not to optimize the game.

Patches that felt designed by committee. Some patches were a coherent vision — clearly someone won the argument and the patch reflected a single hand. Others were patchworks of small concessions to every faction, and they did not consistently move the meta in any direction. Design by committee has a quality, and StarCraft II patches under the Council sometimes had it.

What Small Studios Should Learn

The Balance Council is an unusual case — a multi-million-dollar IP, a global pro scene, a corporation no longer fully invested in its own product. But the lessons translate.

Community input is data. Even if you do not form a council, your community is sending you balance signals constantly — Discord arguments, Steam reviews, YouTube videos, Reddit threads. Treat these as input, not noise. Tag them. Aggregate them. They are the same kind of signal the Council provided to StarCraft, just less formalized.

Pro players are the canary, not the audience. The Council's biggest blind spot was the gap between pro and casual experience. If your game has a competitive scene, listen to the top players, but balance for the whole player base. Pro feedback is fast and informative; casual data is what determines whether the game lives or dies.

Visible reasoning builds trust. The Council got this right. Patch notes that explain the why of every change build community trust even when individual changes are unpopular. StarCraft's old silent patches taught the community to assume the worst; the Council's visible debates taught the community that real reasoning was happening, even when they disagreed with the conclusion.

Distributed decision-making needs structure. A council without rules is a debate club. A council with voting rules, charter documents, conflict-of-interest policies, and a clear charter is a deliberative body. If you involve community members in design decisions, formalize the structure — voting, terms, accountability, replacement procedures. Otherwise the loudest voice wins, and the loudest voice is rarely the wisest.

You cannot offload your design responsibility. Blizzard tried, in part, to get out of the balance business by handing it to the Council. They could not fully escape — players still blame "Blizzard" when patches go wrong, even if the Council voted on them. The IP is yours; the responsibility is yours; you cannot delegate the consequences. You can delegate the work, but you remain the author.

Race politics will appear in any partisan game. This is not unique to StarCraft. Class politics in World of Warcraft, role politics in Overwatch, deck-archetype politics in Hearthstone — every game with factions has factional politics around balance. Plan for them. Be aware that any decision-making body composed of partisans will be biased by their partisanship. The remedy is structural (rotation, voting rules, data inputs that override anecdote) rather than aspirational ("just be objective").

The Council Today

As of this writing, the Balance Council remains active, with rotating membership. StarCraft II's patch cadence has stabilized into something like a normal live-service rhythm, with patches every few months rather than the years-long droughts that preceded the Council's formation. Community sentiment toward the Council remains divided — some players see it as the savior of competitive StarCraft, others as a symptom of Blizzard's abandonment.

The honest assessment is that the Council was a better-than-nothing solution, and its existence has kept the competitive scene alive longer than it would have lasted under pure neglect. But it is not a model to imitate uncritically. The conditions that made it necessary — a corporation that no longer wants to balance its own game — are not conditions any studio should aspire to. The Council is a workaround, not an ideal.

For your own game, the takeaway is humbler: take the parts of the model that work (visible reasoning, pro and community input, data-informed proposals) and reject the parts that do not (handing off responsibility, distributing accountability, letting partisan politics drive numbers). Run your balance process yourself, with the input of others, but with one designer or one small team holding the responsibility for outcomes. That is the structure that ships balanced games, with or without a council.

A Sidebar: The Avilo Problem

One of the more colorful arcs in the Council's history involves Avilo, a longtime Terran player and streamer who had been one of the loudest balance critics in the StarCraft II community for more than a decade. When the Council was formed, Avilo was eventually invited in. The invitation was controversial — Avilo had a history of public disagreements, race-loyal advocacy, and provocative streaming — and his inclusion told the community something specific about the Council's composition: this was not going to be a sanitized panel of polite voices. The vocal critics were going to be inside.

The arc that followed is instructive. Avilo's positions inside the Council were not radically different from his positions outside it; he advocated for Terran, he criticized Zerg-heavy patches, he argued forcefully and at length. But his presence inside changed the dynamics. Other Council members had to rebut his arguments rather than dismiss them. The Terran perspective got formal representation in the deliberation, and the patches that emerged did, on average, reflect the Terran case more than they would have without his presence. Whether this was good or bad depends on whether you think Terran was actually under-represented in the prior balance philosophy. Avilo himself eventually left the Council in 2024 amid further controversies, but the precedent he set — that a vocal community critic could become a formal participant — was a real shift in how Blizzard related to its loudest voices.

The lesson for indie studios: when you bring critics into the tent, they do not stop being critics. They become internal critics, with all the friction and all the productive challenge that implies. This is sometimes the right call — it deflates conspiracy theories, it raises the rigor of internal debate, it transforms outside opposition into inside opposition. It is sometimes the wrong call — it amplifies disruptive voices, it can paralyze decision-making, it creates problems that did not exist when the critic was outside. There is no universal right answer; the question is what your specific community needs at your specific moment.

A Counter-Example: Riot's Internal Approach

It is worth contrasting StarCraft II's Council with League of Legends's approach. Riot has never formally handed balance authority to the community. Pro players and content creators are consulted constantly, but the decision-making remains internal. The team is large enough — dozens of designers, analysts, and engineers — that they do not need community labor to balance the game. They have the bandwidth to do it themselves.

The result is a balance process with clearer accountability, faster decision-making, and a single design vision running through the patches. The downside is the loss of community ownership; players know that Riot decides, and they argue with Riot rather than within their own community.

Both models have produced long-running, vibrant competitive games. The point is not that one model is correct. The point is that the structure of who decides shapes the patches that result. StarCraft's Council patches feel like consensus documents; League's patches feel like authored design statements. Neither is intrinsically better — they reflect the games' different needs and the studios' different capacities.

The Final Lesson

The Balance Council exists because Blizzard could no longer afford the alternative. The Council is what you do when the original development team has moved on but the game's competitive scene wants to keep going. As a model for new games, it is suboptimal — the right approach to balance is to invest in it from the beginning, with a small dedicated team that has the data, the authority, and the accountability to ship coherent patches. As a model for legacy games, the Council is a workable compromise — better than abandonment, not as good as continued investment.

For your own progressive project, the takeaway is straightforward. You are the balance team. You have the data (your playtests, your spreadsheets), the authority (your project), and the accountability (your players). Use them. Do not reach for a council until you have exhausted your own capacity to balance the game yourself, and even then, structure the council so that someone — you — remains accountable for the outcomes. The Balance Council is what you build when you have run out of other options. Until then, do the work.

🎯 Discussion Question: If you were a small indie studio with a competitive game and a passionate community, would you form a balance council? What rules would you put in place? Who would and would not be on it? How would you handle the situation where the council's vote and your own design judgment disagree? And, perhaps most importantly: would you want a notorious, vocal critic of your game to be on the council, knowing what you now know about the Avilo arc?