The problem: a zombillion is a legibility threshold
In horde design, a zombillion is not a literal enemy count; it is the point where the player stops counting zombies and starts guessing at threats. That threshold matters because survival games depend on clean reads: which enemy is closest, which lane is open, and which attack can be dodged. A scene with 60 shamblers packed into a corridor can feel more lethal than 600 spread across a fog plane, because the second scene collapses into visual noise. The takeaway is blunt: designers should budget readable threats, not impressive body counts.
The cause: exponential waves meet linear attention
Many wave systems multiply enemy totals by a fixed factor each round, then add health and speed on top. The math looks manageable on a spreadsheet, but the player’s attention does not scale exponentially. Doubling a wave from 300 to 600 zombies can double draw calls, animation updates, collision checks, and audio sources while only marginally increasing perceived danger. Off-screen simulation and pooled assets can hide some cost, but they do not solve the central cause: waves are tuned to numeric escalation rather than to the decisions the player must make under pressure.
- Render cost: more bodies increase overdraw and animation load.
- Audio cost: overlapping groans flatten directional cues.
- Balance cost: health inflation turns a horde into a chore.
The consequence: a huge count can make the game smaller
When a wave crosses into zombillion territory, the design often loses the very features that make zombie combat tense. Players stop using cover because every direction is occupied; they stop aiming because individual targets no longer matter; they stop reading audio because the mix becomes a wall of noise. The result is a smaller game disguised as a bigger one: fewer meaningful choices, fewer identifiable enemy types, and fewer moments where skill changes the outcome. The same trade-off shows up in compact horde experiments such as zombillion, where the interesting test is not whether the engine can add another zero but whether the player can still spot a threat, a route, and a mistake.
The solution: cap active bodies and abstract the rest
A workable horde budget separates visible threats from simulated pressure. Keep 20 to 40 active zombies near the player, each with full animation and clear silhouettes; represent the rest as off-screen spawn pressure, distant silhouettes, or wave timers. Spawn in clusters with deliberate gaps, then use audio and lighting to mark the dangerous edge of the group. Example: a 1,000-zombie round can present 30 close-range enemies, 200 mid-range silhouettes, and 770 abstracted attackers hitting barricades. The takeaway is that a zombillion should be a narrative idea, not a rendering target; the player needs a readable slice of the horde, not the whole arithmetic.
