Loading field map
A build order in Age of Empires II is a predetermined sequence of actions—typically covering the first several minutes of a game—that a player executes to reach a chosen economic or military configuration as efficiently as possible. The subfield of build orders encompasses the study, design, execution, and countering of these sequences. It is the practical bridge between the game's abstract mechanics and the concrete decisions a player makes before the first significant conflict or economic milestone.
The core question that build orders answer is: Given a desired goal, what is the most reliable way to allocate limited early-game resources (villager time, food, wood, gold, and the single Town Center that produces villagers) to achieve it? The stakes are high because early decisions compound. A few seconds of idle Town Center time, a misplaced farm, or a suboptimal villager distribution can delay a Feudal Age advance by a meaningful margin, which in turn determines who arrives at a key military technology or a defensive structure first.
The difficulty lies in the fact that the game begins with perfect information about one's own economy but almost none about the opponent's. A build order is therefore not a script that guarantees victory; it is a plan that optimizes for a specific scenario while remaining adaptable. The central tension in the field is between greed (investing in economy to gain a long-term advantage) and safety (investing in military or defenses to avoid being overrun early). Every build order is a bet on how the opponent will behave, and the field's evolution is largely a history of players learning to hedge those bets.
In the game's early competitive years, play was largely improvisational. Players understood basic principles—keep the Town Center producing villagers, gather food and wood, advance when you can afford it—but there was no shared vocabulary for precise sequences. The first major conceptual shift was the recognition that the early game could be treated as a mathematical optimization problem. The key variables were the number of villagers on each resource, the timing of the Feudal Age advance, and the order in which buildings were placed.
The breakthrough that created the modern subfield was the standardization of the opening. Players and analysts realized that a small set of "standard" openings—such as the 6-pool (a fast military rush) or the 28+2 (a slower, more economical advance)—could be defined by their villager count at the moment of advancing. This allowed for precise comparison: a player could say "I advanced at 21 population with 4 minutes 30 seconds on the clock," and another player could immediately understand the economic trade-offs involved. This numerical framing turned build orders from personal habits into a shared, testable body of knowledge.
The field is not organized by a single linear progression but by a set of enduring strategic paradigms that coexist and respond to one another. These are best understood as responses to the core greed-versus-safety problem.
The oldest and most fundamental paradigm is the economic opening, whose most famous expression is the Fast Castle. The goal is to reach the Castle Age (the third age) as quickly as possible, skipping or minimizing military production in the Feudal Age. The assumption is that the Castle Age's powerful technologies, unique units, and extra Town Centers provide a decisive advantage that outweighs the risk of being attacked while vulnerable.
The organizing method is strict resource prioritization. The player gathers only what is needed to advance, often delaying farms (which cost wood and require a steady food income) in favor of hunting and foraging. The key metric is the advance time, and the entire sequence is optimized to minimize it. The approach's strength is its economic payoff: a successful Fast Castle can produce a flood of villagers from multiple Town Centers, creating an insurmountable resource lead. Its weakness is its fragility: a well-timed Feudal rush can force the player to abandon the plan, spend resources on defense, and fall behind despite reaching Castle Age.
The direct counter-paradigm is the military opening, exemplified by the Feudal rush (often called a "flush"). Here, the player advances to the Feudal Age with a smaller economy but uses the early military units available in that age—archers, skirmishers, or men-at-arms—to attack the opponent before they can execute their own plan. The goal is not necessarily to destroy the opponent's base but to disrupt their economy, kill villagers, and force them to respond, thereby negating their economic advantage.
The organizing assumption is that disruption is cheaper than production. A small investment in military units can idle an opponent's villagers, force them to build defensive structures, or delay their advance. The method involves a different optimization: the player must balance the cost of the military units with the need to keep their own economy growing. The key metric is not advance time but military presence time—how quickly the first units arrive at the opponent's base. The approach's weakness is that if the rush fails to do meaningful damage, the rusher's own economy is smaller than the defender's, and they will fall behind in the mid-game.
Between these poles lies a large middle ground of hybrid approaches that acknowledge the uncertainty of the opponent's plan. These are not a single school but a family of strategies that aim to be robust rather than optimal. A common example is the drush (dark-age rush), which sends a few militia to harass the opponent while still advancing to Feudal Age on a near-economic schedule. Another is the wall-and-boom, which invests in defensive walls early, allowing the player to safely pursue an economic opening without the risk of a Feudal rush.
The organizing principle of these approaches is information management. The player makes a minimal, reversible commitment early (a few military units, a wall, a scout) to buy time to learn the opponent's plan, then commits to a more extreme strategy (economic or military) once the information is available. The method is less about optimizing a single sequence and more about designing a sequence with branching points—moments where the player can choose between different follow-ups based on what they have seen. The key metric is flexibility: how many different opponent strategies can this build order reasonably answer?
A crucial layer of complexity is that build orders are not universal. Each of the game's civilizations has unique bonuses, technologies, and unit rosters that change the optimal sequence. A civilization with a farming bonus (such as the Franks) can afford to place farms earlier; a civilization with a cheaper archery range (such as the Britons) can execute a Feudal archer rush more efficiently. Build orders are therefore always civilization-specific, and the field includes a large body of knowledge about which openings are viable for which civilizations.
Similarly, the map matters. On a map with abundant deer or sheep, a player can delay farms and advance faster; on a map with scarce resources, the same build order may fail. The subfield therefore distinguishes between standard map openings (designed for the most common resource distributions) and map-specific adaptations. This is not a separate school but a necessary qualification: a build order is always a statement about a specific civilization on a specific map against a specific opponent.
The current state of the field is characterized by a high degree of codification and refinement. The early-game sequences for most civilizations are well established, and the frontier has shifted to the transition between the opening and the mid-game. A modern build order is rarely a single sequence; it is a decision tree that specifies what to do in response to common opponent actions. The best players do not memorize a single path but internalize the logic of why each step is taken, allowing them to improvise within the framework.
Two developments have shaped the modern landscape. The first is the quantitative analysis of build orders using game data. By recording and analyzing thousands of games, analysts have identified which openings have the highest win rates at different skill levels, and which transitions are most robust. This has led to a convergence on a set of "meta" openings that are considered safe and strong, while also revealing that some historically popular openings are weaker than their reputation suggests.
The second is the professionalization of practice. Build orders are now taught through dedicated practice tools, community guides, and coaching. The field has a recognized canon of "standard" openings that every competitive player is expected to know, and a smaller set of "cheese" or "all-in" strategies that are risky but can catch an unprepared opponent off guard. The distinction between these is not always clear-cut; a strategy that is considered cheese at the highest level may be a standard, reliable opening at a lower level, where opponents are less able to punish its weaknesses.
The enduring debate in the field is not about which build order is "best" in the abstract—that question is meaningless without specifying the opponent, map, and skill level—but about how to balance optimization against adaptability. A perfectly optimized build order is fragile; a perfectly adaptable one is slow. The field's practitioners are constantly negotiating this trade-off, and the most respected players are those who can execute a precise sequence while remaining alert to the moment when it must be abandoned. This is the true skill of the subfield: not the memorization of a script, but the judgment to know when the script no longer applies.