Why do zerg need buildings if units come from larvae?

Why does a zerg colony need specialist structures when its units emerge from larvae? The apparent duplication comes from treating the place where a body forms as the whole production system.

Larvae supply the transforming bodies; the developing colony supplies the ability to make particular forms. That distinction explains the building requirement without assuming that every larva can produce every zerg creature immediately.

Enabling a unit is different from producing it

Blizzard’s StarCraft II production guide draws the distinction directly. Hatcheries generate larvae, which morph into units. Structures such as the spawning pool and roach warren enable particular transformations rather than produce those units themselves.

An official StarCraft II view of a hatchery and surrounding structures: production location and morph-enabling functions belong to different parts of the colony. © Blizzard Entertainment. Image source ↗

The larva is therefore where the new body takes shape, not a replacement for everything the colony must develop. Removing the structures from that picture removes the functions that make the available forms possible. One common starting body does not imply one common production requirement.

The original game’s Hydralisk Den entry gives a concrete example: the structure enables larvae to become hydralisks and supplies genetic information for additional abilities. It has a role even though the hydralisk does not walk out of the den as a newly trained soldier.

What about the genes already inside the larva?

That objection comes from real official wording. The original Larva entry describes genetic information for the other zerg breeds inside larvae. But the same entry also describes a young colony with only basic forms available, followed by an expanding genetic repertoire as new structures develop.

Blizzard’s original StarCraft larva portrait, shown at its native size. © Blizzard Entertainment. Image source ↗

The useful distinction is between broad transformative capacity and the repertoire a particular colony can currently use. That is a reading of the two statements together, not an official molecular explanation. The entry does not establish a complete archive with a building-operated permission switch, nor does it specify that the missing genes exist only inside the structures.

There is another wrinkle: drones themselves become living structures. A body produced from a larva can become part of the colony’s production infrastructure. This makes the system more interconnected than a collection of separate factories, but it still does not tell us exactly where every sequence is stored or how it travels.

A shared starting point has exceptions

The StarCraft II guide says that most units come from larval morphing. It explicitly separates queens, which are produced at the hatchery without consuming a larva, and transformations of existing units, such as an Overlord becoming an Overseer.

Those examples matter because a statement about the larva’s genetic versatility is not a complete genealogy of every zerg entity. Nor should an original-game lore description be used to infer every later game’s production route.

The building requirement reflects a division of functions within the colony: a place for a body to transform and developed structures that enable particular forms. The broader question of how different zerg evolve leads into other paths of zerg evolution.