A few weeks ago I wrote an article talking about the possibility of a Brood War Renaissance. It’s 2017, and Brood War is once again completely relevant to current events. This is not a wishful, “what if” piece. This is it, we’re actually on the trail. I have to wonder how many esports writers over the years have thought of this moment as a wild dream.
For so many esport writers and athletes, their passion for craft started with Brood War. Most went on to other games and other projects: League of Legends, Hearthstone, Overwatch. Yet Brood War was the starting point of that passion, and it’s for that reason it holds a sentimental place in the esport world. With that in mind, it’s a powerful experience to be here, writing about a game that meant so much to so many.
It is no secret that Brood War has a steep learning curve, even by StarCraft 2’s harsh standards. You’ve likely heard so much about it. What I’d like to talk about are the things they don’t tell you. The walls you run into that catch you off-guard.
You’ve heard so much about Brood War’s pathing issues that affect your ability to get around the map. But what you didn’t expect is the almost completely black screen you’re met with once you get into a game. Unlike StarCraft 2, which features a greyed out map from the start of the game, the maps in the original are completely black until you explore them for the first time in that game. This means that before you get into a game, it will be worthwhile to spend some time studying the map layouts.
A good starting point is just picking a single map, study it and play an AI game or two to get a feel for the terrain. Lost Temple and/or Luna are good options for their popularity. There’s a useful page worth looking at containing a list of the most popular maps in Brood War, courtesy Team Liquid.
Once you’re comfortable enough with a map that the black screen isn’t as much of an issue, try hosting a few games on it. If someone refuses to play you on a map you’re familiar with, just call them an LotV scrub and block them.
If you’ve done your research on Brood War, you’ve likely heard and perhaps even studied a few of the more famous builds. As commendable as that is, just forget them. At least for your first month. Macro in Brood War is an exceptionally complicated affair. Your first goal is to be able to start producing units. Rather than following a strict build order, just keep a priority list in mind and a general idea of what your end game strategy will be.
Of course, this is not to say Builds should never be used. Build Orders are especially important later down the line as you’re looking to refine your technique with pinpoint accuracy. But you’re better off avoiding them until you’re at least comfortable enough that you’re producing units at a steady pace.
Basic Defensive Tactics
Positioning in Brood War is everything. Even more than in StarCraft 2. In your early studies on maps, it’s important to identify choke points and open areas you’ll either want to hold or avoid depending on what race you’re playing. If you’re playing Protoss vs Zerg, for example, you’ll want to avoid straying in open areas or risk being surrounded. Furthermore, you’ll want to focus on positioning your units on choke-holds. With Zealots positioned at the bottom of the ramp and Dragoons holding the top. Zerg players will want to focus on baiting Protoss into open territory, usually by threatening map control.
It’s worth noting that in Brood War, attacking into high-ground from the low ground is suicide. This is due to units having a percentage chance of missing when attacking units at an elevated advantage. A final point, specifically for Protoss players, don’t be afraid to split your units. In StarCraft 2, Protoss can’t split units in the early game, but this couldn’t be more different in Brood War. Creating lines of defense is an important tactic for all races. Especially when making an attack into an enemy position, it’s good to have a defensive position held for your assault team to fall back to in case the attack goes badly.
Follow me on Twitter: @Stefan_SC2