Loading field map
In StarCraft, a build order is a predetermined sequence of actions—usually unit-producing structures, unit production, and worker assignment—that a player executes in the opening minutes of a match. An opening is the broader strategic plan that the build order serves: it commits the player to a particular economy, technology path, or military timing. The subfield of build orders and openings studies how these sequences are designed, executed, and countered. Its central question is deceptively simple: given the map, your race, and the opponent's known or suspected race, what should you do first, and why?
The stakes of this question are high and immediate. In StarCraft, small early advantages compound. A worker built ten seconds earlier mines for the entire game; a barracks completed before the opponent's produces its first Marine in time to punish an expand. Conversely, a greedy opening that saves resources for an early economy can be lethal if the opponent attacks early with a military force. Build orders are therefore the game's first line of decision-making: they determine whether you arrive at the mid-game with an advantage, a deficit, or a roughly even position. Because the game's unit and structure costs are deterministic, the early game is closer to a solved optimization problem than any later phase, which is why build orders are studied with near-mathematical care.
The modern study of build orders emerged with competitive StarCraft in the late 1990s, but its roots lie in the real-time strategy genre's earlier conventions. In the first StarCraft (1998), players discovered effective sequences through trial and error, sharing them on bulletin boards and early fan sites. The professional scene in South Korea, which developed rapidly after the game's release, accelerated this process: professional players and their coaches refined openings through systematic practice, and broadcasted matches made novel builds visible to a mass audience. The successor title, StarCraft II (2010), inherited this culture. Its online ladder system, replay-sharing features, and large streaming audience meant that the life cycle of a new opening—from professional discovery to widespread adoption—shortened dramatically.
Important conceptual shifts occurred over time. Early thinking treated openings as fixed scripts to execute "on time"—that is, making each production cycle without delay. As the player base matured, the emphasis shifted from execution to adaptation: knowing not only your own build but also how to read the opponent's opening from scouting information, and how to adjust. A further shift came with data analysis. Replay databases and statistical tools allowed players to evaluate openings by win rate across thousands of games, adding an empirical layer to what had been primarily a craft of intuition and practice. Today, the field is a mixture of craft knowledge, game theory, and data science, with professional teams employing analysts who tag and aggregate replays to identify trends.
Three broad approaches organize the field. They are not mutually exclusive; most serious players use all three, but they represent different answers to the question of how to reason about openings.
The scripted approach treats a build order as a precise sequence to be memorized and executed flawlessly. Its organizing assumption is that the early game is a race against the clock, and that any deviation from the optimal sequence costs time and resources. This approach dominated early competitive play and remains the foundation of learning the game. Its central method is repetition: using a practice mode or custom game to hit benchmark timings—the moment your first combat unit appears, the moment your expansion is operational, the moment your technology completes. The scripted approach's strength is reliability; its weakness is rigidity. A player who has memorized one sequence can be caught off guard by an opponent who diverges from their own expected script. Because of this, pure scripting is now seen as necessary but insufficient; it is the grammar of the opening, not the strategy.
The reactive approach focuses on information and contingency. Here, the opening is not a fixed sequence but a plan with decision points: you execute a general framework, scout the opponent, and branch your actions based on what you see. The organizing assumption is that the opponent is a thinking agent who will respond to your actions, and that reading their choices is more valuable than executing any single ideal sequence. The method involves carefully chosen scouting timings—sending a worker or an early unit to the opponent's base at a moment when it will reveal key information—and a set of prepared responses to common opponent builds. The reactive approach's strength is robustness: it handles a wide range of opponent strategies without panicking. Its weakness is that it requires deep game knowledge and practiced decision-making; a player who understands what to do in response to each scout but cannot execute the response cleanly will still lose. It also risks information overload: too many branches to remember, too many signals to interpret.
The principled approach seeks general rules that explain why some openings work and others fail, rather than memorizing sequences or preparing contingencies. Its organizing assumption is that the game's economy and production mechanics create stable trade-offs—for example, between spending resources on workers (economy) versus military units (safety), or between building an expansion (long-term income) versus additional production structures (short-term output). A principled player reasons from these trade-offs: "If my opponent is likely to expand early, I can get away with a greedy build; if they tend to pressure early, I need safety." The method is abstract and analytical, often using economic models, timing comparisons, and post-game analysis rather than in-game practice. This approach's strength is transferability: it allows a player to improvise when no memorized build applies. Its weakness is imprecision: the general rules do not specify exact actions, and a player who reasons correctly but executes sloppily will lose to a well-drilled opponent following a script.
These approaches are best understood as layers rather than rival schools. A typical professional player's preparation combines all three: choose a principled framework (e.g., "I will open with a fast expansion against Zerg because the map has a safe third base"), refine it into a scripted build order with exact timings, and develop reactive contingency plans based on scouting. The relationships among them are complementary: the principled approach generates the plan, the scripted approach makes it executable, and the reactive approach protects it from disruption.
There are also genuine tensions. A player who relies too heavily on scripting can become predictable, and sophisticated opponents will exploit that predictability. A player who is too reactive may fall behind in macro—the continuous production of workers, units, and structures—because every reactive choice costs attention and time. The principled approach, while elegant, can fail when the game's meta-game (the prevailing strategies of the moment) shifts, because the principles were derived from assumptions that no longer hold. These tensions are not resolved; they are managed through practice, review, and adaptation.
The contemporary landscape of build orders and openings is characterized by several stable features. First, there is a distinction between standard openings, which aim for a solid, flexible position and are used in most games, and all-in or timing attacks, which commit most or all resources to a single attack that must succeed to win. The choice between them is a fundamental strategic decision, and both have enduring roles. Standard openings are the default because they avoid catastrophic losses; all-ins are used to punish a specific read on the opponent or to force a win in a position where your standard play is weaker.
Second, openings are race-specific and matchup-specific. Each race—Terran, Protoss, Zerg—has distinct production mechanics, worker economics, and early military options. A build order that works for Terran does not transfer to Protoss, and within a race, an opening that works against Zerg may be unsound against Terran. The matchup is the primary unit of analysis: the field's practical knowledge is organized as nine pairwise sets of openings (Terran vs. Protoss, Terran vs. Zerg, and so on).
Third, the opening-midgame boundary is a consistent source of difficulty. An opening determines the position at roughly the first five to eight minutes of play, but the game continues. A player who wins the opening—in the sense of reaching a position with an economic or military advantage—can still lose if they transition poorly to the mid-game. The study of openings therefore always includes the question of what comes next, and many openings are evaluated not only on their immediate effect but on the quality of the mid-game position they produce.
Fourth, the field is renewed continuously through meta-game cycles. When a new opening becomes popular, players develop counters; when the counters become popular, players develop counters to the counters, or revive previously abandoned builds that exploit the new popular ones. This dynamic is not a linear progression but an ongoing oscillation, and it means that no opening is permanently "best." The empirical study of win rates and the theoretical study of game mechanics feed into this cycle, with professional players and high-level amateurs experimenting and pushing the boundaries of what is considered viable.
Finally, the role of practice and data collection deserves emphasis. The serious study of openings is inseparable from deliberate practice: executing, reviewing replays, identifying mistakes, and adjusting. The tools for this have improved over time, but the core method is unchanged. A player who understands the principles and can execute the scripts must still sit down, play dozens or hundreds of games with an opening, and build the muscle memory and situational awareness that no written guide can provide. The field is thus a discipline in a literal sense: a body of knowledge that only becomes active through trained performance.