LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

Gaming

StarCraft stopped its workers’ traffic jams by letting them pass through other units

Patrick Wyatt’s development account shows how one narrow exception kept the resource economy moving while pathfinding remained complicated.

Chris in a miner's jumpsuit carries a glowing blue crystal while a line of hovering harvester pods passes straight through one another.
Illustration: LockerGnome

StarCraft’s economy could grind to a halt because its workers were too good at getting in one another’s way. More harvesters meant more resources, until enough of them crowded the same route and stopped moving. Patrick Wyatt’s solution was to let harvesting workers ignore collisions with other units. The commute improved when traffic stopped being solid.

In his first-person development account, Wyatt describes players looking away to manage a battle or another base while their workers jammed up at home. Resource income stopped, and the build queue suffered. This was a pathfinding problem with consequences far beyond whether one little unit walked in a convincing line.

StarCraft inherited an engine shaped around tile-based terrain. The perspective and geometry had become more complicated, while units still needed to navigate through constrained space. Wyatt describes the movement system growing a large collection of special cases for extracting units from bad situations. Every new escape route could become another thing to understand.

Harvesting amplified the trouble because players naturally packed workers around valuable deposits. Outbound and returning units met head-on. With enough bodies in a small area, some could be trapped until the deposit disappeared. Adding workers to improve production could sabotage production instead, a remarkably thorough interpretation of diminishing returns.

Wyatt recalls deciding he couldn’t simply repair the whole problem. His exception applied while workers were heading to gather resources or returning with a load. Removing the collision interactions let them pass through traffic instead of negotiating every encounter. The account includes a correction broadening the description to other units, so the behavior shouldn’t be reduced to worker-versus-worker collisions alone.

The distinction between terrain and unit collision is useful here. The hack didn’t announce that workers could walk through every wall on the map. It changed how moving units obstructed the workers during a particular job. A narrow state-dependent rule addressed the economic bottleneck without requiring a complete replacement of movement.

That doesn’t make every shortcut equally wise. The story works because the problematic state was recognizable and the payoff could be observed: workers kept harvesting. A broad claim that collision checks were generally unnecessary would have thrown away the constraint that made this exception useful in the first place.

For players, the visible result is a familiar bit of StarCraft behavior with an engineering reason behind it. For anyone shipping software, it is a reminder that a small exception can become part of how users understand the product. Once strategies rely on that behavior, a later cleanup may change much more than the implementation.

Wyatt’s account leaves the larger pathfinding system looking exactly as awkward as a late project can be. The harvesters got a workable route through it, while the rest of the movement problem remained its own assignment.

The workers got right of way.

More Gaming

Every Gaming story →