Wave Survival Design: Why the Gap Between Waves Matters More Than the Wave

Ask someone what they remember about a horde mode and they will describe the moment the last enemy dropped and the screen went quiet — the reload, the walk back to the ammunition, the few seconds of deciding where to stand next.

They will not describe wave eleven. Nobody remembers wave eleven. The wave is the thing that happens to you; the gap is where you happen to the game, and it is doing far more design work than its share of the running time suggests.

The gap is a designed object

A wave survival game has two states, and they ask for opposite things.

Inside a wave, you are executing. Attention is on immediate threats, the decisions are small and fast, and there is no time to reconsider your approach. Tension climbs.

Between waves, you are planning. You spend whatever the game gives you to spend, reposition, look at what is coming, and decide what the next few minutes are going to look like. Tension releases.

Neither state works without the other. Continuous tension is not more intense than alternating tension — it is less, because tension is measured against a baseline and a constant one becomes the baseline. This is why a game that never lets up ends up feeling monotonous rather than relentless, and why the players who complain about downtime would be the first to notice its absence.

The gap also carries all the strategy. A game where every decision is made under fire is a reflex test. Put a quiet window between waves and you have added a second, slower layer where the player forms intentions, and the wave then tests whether the intention was any good. That is a much richer structure for very little extra content.

Three escalation levers, in order of quality

Every wave survival game has to get harder. There are three ways to do it and they are not equally good.

Count: more of the same

The obvious lever. Wave one has some enemies, wave twelve has many more.

It is the weakest option, and it degrades in a specific way. Once the player has an answer to an enemy type, sending more of them tests only whether the answer scales. That is an attrition question — do you have enough damage, enough ammunition, enough health — and attrition questions are resolved by the numbers on your character sheet rather than by anything you do.

Count also has a hard ceiling that is not a design decision. Enough entities and the frame rate goes, which on a phone arrives sooner than on anything else.

Composition: different demands

The strongest lever. Rather than more enemies, introduce one that invalidates the current plan.

The classic shapes are worth naming because almost every horde game uses some subset:

• The fast one, which punishes the assumption that you can outrun the mass.
• The armoured one, which punishes damage spread thinly across many targets.
• The ranged one, which punishes kiting in a straight line, because distance stops being safety.
• The exploding one, which punishes killing things at close range and turns your own effectiveness against you.
• The support one, which buffs or heals others and makes target priority a real decision rather than "whatever is nearest."

Each of these forces a rebuild rather than a repeat. That is the property that keeps a game interesting past the point where the player has learned the basics, and it is why enemy variety matters more than enemy quantity for long-run engagement.

Compression: less recovery

The subtlest lever. Keep the waves the same and shorten the gap between them.

Compression works because it attacks the planning layer instead of the execution layer. A player who had time to reposition, heal and reload now has to choose one of the three. Nothing on screen got stronger; the player's ability to prepare got weaker, which reads as rising pressure without any visible change to the threat.

Used carelessly, compression is also the fastest way to make a game exhausting, because it removes the release half of the tension cycle. Most well-tuned games apply it in bursts and then hand a longer gap back.

Spawn placement is the difficulty dial nobody sees

Where enemies appear decides more about how hard a wave feels than what those enemies are.

The core problem every designer in this genre has to solve is the safe pocket. If threats always approach from a predictable direction, the optimal play is to retreat to the furthest defensible point and hold it. The game becomes stationary, the movement system stops mattering, and the whole thing collapses into a shooting gallery.

The standard fixes:

• Spawn on multiple sides, so there is no single direction to face.
• Spawn behind, which is the most disliked and the most effective. It converts holding a position into a losing strategy and forces continuous repositioning.
• Move the objective, so the safe spot stops being where you need to be.
• Degrade the pocket, by making cover destructible or resources finite so that camping has a shelf life.

Spawning behind the player is worth dwelling on because it is where the genre most often earns accusations of cheating. The difference between a good implementation and a bad one is entirely about information. A spawn that is telegraphed — a sound, a marker, an animation with a wind-up long enough to react to — is a demand that you keep checking your back, which is a skill. A spawn that materialises inside your escape route with no warning is not a demand, it is a coin flip.

This is the same fairness test that applies to projectile patterns: it telegraphs, it behaves consistently, and a survivable option existed before the threat committed. Break any of the three and the player learns nothing from dying.

The power curve and the window

Wave survival games are, underneath, a race between two curves: how fast the threat grows and how fast the player grows.

If the player curve is always below the threat curve, the game is a slow loss and nothing feels earned. If it is always above, there is no tension. What works is an oscillation, and the shape most games aim for is:

1. Early scarcity. You are underpowered and every resource matters. This teaches the systems, because you cannot brute-force anything.
2. The window. Your build comes together and for a few waves you are genuinely overpowered. This is the payoff for every decision made so far, and a game that never grants it feels like work.
3. The overtake. Escalation catches up and passes you. The window closes. What you built is now merely adequate, and the run is decided by how well you play rather than by what you picked.

The timing of step two is most of what separates a satisfying horde game from a grinding one. Too early and the middle of the run is boring. Too late and most players quit before they ever feel competent.

This is also why upgrade choice quality matters so much. A build assembled from options that genuinely exclude each other produces a different window each run — you were overpowered in a different way — which is the thing that makes a second run worth starting. How to make those choices well is a subject of its own, and it is where the run-based structure that horde games inherited came from.