Before the engine, the people. Brood War's technical decisions only make sense against the studio, the deadline, and the dial-up world it was born into.
Blizzard — a modest Irvine team fresh off Warcraft II and Diablo — set out to build a sci-fi RTS. The first build, at E3 1996, was mocked as "Warcraft in space." They scrapped the look and rebuilt.
A few names worth knowing — the design and tech leads whose decisions you'll see echoed in the code throughout this site.
Architected much of the engine, evolving the Warcraft codebase. The data-driven design you'll see — units, weapons, upgrades, and iscript animation bytecode all in external .dat files, not hardcoded — is what let a small team tune hundreds of unit interactions.
BW's depth is a design win, not just engineering: three races share one simulation yet feel like three games — why build orders are still being refined 25+ years on.
First StarCraft build shown at E3 to a lukewarm reception. Blizzard pulls it back and rebuilds the art and feel from scratch.
With Diablo, Blizzard ships free online play. The matchmaking + lockstep model that StarCraft will use is proven on dial-up.
Three asymmetric races, a 30-mission campaign, and a map editor. It sells in the millions and the modding scene ignites immediately.
New units, campaigns, and crucial balance changes. This becomes the competitive version for the next 20+ years.
A boom in PC bangs (internet cafés) after the Asian financial crisis turns BW into a televised, professional spectator sport with star players and broadcast leagues.
4K art over the same simulation. Determinism is so central that the original engine logic is preserved wholesale.
Vegard Mella (tscmoo) writes OpenBW — an independent, faithful reverse-engineering of the BW simulation. It runs headless on Linux and powers AI/ML research (TorchCraft) without Blizzard's executable. It's the source we quote throughout — but it is not Blizzard's code.
Active pro and amateur scenes, ongoing bot tournaments (SSCAIT), and preservation work keep a 1998 engine alive and dissectable.
Hold three facts in mind as you read the rest of this site, because every technical chapter traces back to them:
A 56k modem and high latency meant you could not stream game state. The only affordable thing to send was the handful of bytes describing a player's clicks.
Two players had different processors. For both to compute the identical game, the math had to be bit-for-bit reproducible — no floating point allowed in the simulation.
Those two pressures produce the entire architecture: lockstep to save bandwidth, fixed-point determinism to survive different hardware, and a desync checksum to catch it the instant anything goes wrong.