A wave in an arena game is not a hand-written list of monsters. It is a count drawn from a roster that grows as the run does, shaped by two rules that exist to keep the result fair. Knowing the schedule lets you predict what is coming from the wave number alone.
Count first, roster second
Two things grow across a run: how many creatures a wave contains, and which species are eligible to fill it.
The count is the simpler of the two. Sword Quest opens at three and adds roughly one and a half per wave, capping at fifteen. Castle Defender opens at four, adds about one and seven-tenths, and caps at sixteen.
The roster is where the interesting escalation happens, because a wave of eight goblins and a wave of eight mixed creatures are very different problems at identical size. That is why runs can feel as though they jumped in difficulty without the numbers changing much - something new entered the pool.
The unlock schedule
Species become eligible by wave number, and the schedule is identical in every game that uses the shared bestiary.
Goblins are available from the first wave. Bats join on wave two, slimes on wave three, wraiths on wave five, dragonlings on wave six and golems on wave seven.
Those last three are close together deliberately. Waves five to seven are where the game changes character, and a player who has been coasting on a single approach will find it stops working across about twenty seconds.
The practical value of knowing the schedule is preparation. If you are on wave six and holding a Shield you have not spent, wave seven is what you were saving it for.
- Wave 1: goblins only.
- Wave 2: bats join.
- Wave 3: slimes join.
- Wave 5: wraiths join.
- Wave 6: dragonlings join.
- Wave 7: golems join - the full roster.
Ad space reserved. See README.md to connect an ad unit.
The two fairness rules
Once the pool is set, the composer picks from it at random - but two constraints override the randomness, and both exist because playing the unconstrained version was worse.
The first: no more than one ranged creature per three in the wave. A player forced to close distance while two dragonlings fire from opposite sides has no route that is not a guess, and a guess is not a decision. Any excess dragonling rolled is replaced with a goblin.
The second: the first creature of every wave is always a goblin. A wave never opens with something you have not fought before, so the moment a new species appears you meet it with the rest of the wave already legible.
Both rules cost variety and buy readability, which is the trade this site makes almost everywhere.
The breather wave
Every fourth wave in Sword Quest - every fifth in Castle Defender - is cut to roughly fifty-five per cent of its normal size, and the between-wave card says so in as many words: a quiet stretch, collect what you can.
This is not generosity. Continuous escalation produces a specific and unpleasant effect: the player never gets to feel the improvement they made, because every wave is harder than the last regardless of how well they played.
The breather makes progress legible. A wave that felt impossible on wave four feels straightforward when a similar one arrives on wave eight, and that comparison is only possible because the curve dips.
For the player, the breather is the window for everything that is not fighting: sweeping up treasure you left behind, collecting a power-up you skipped, moving to a wall. Spending it fighting efficiently wastes the one wave that does not require it.
Reading a wave as it enters
Enemies spawn at the edges and walk in, which gives you two or three seconds of free information before anything is in range.
Three questions. How many are there? Where are they entering from - one side, or split? And is there anything that will not join the queue?
The third is the one that matters most. A dragonling hovers at range and a golem cannot be interrupted, so a wave containing either has to be planned differently from a wave of the same size containing neither.
Answer those three before the first enemy arrives and the rest of the wave is execution. Answer them afterwards and you are reacting to a situation you helped create.
Arrival order versus spawn order
Everything in a wave spawns at roughly the same moment, but nothing arrives together, because the six creatures move at very different speeds.
The order is fixed and worth memorising: bats at 158 pixels a second, goblins at 128, wraiths at 104, dragonlings at 96, slimes at 74 and golems at 52. A bat covers ground three times as fast as a golem.
That stagger is free structure. A mixed wave presents itself as a series of smaller problems rather than one large one, whereas a wave of all goblins arrives as a block - which is why early uniform waves can feel harder than later mixed ones of similar size.
The tactical use is to fight in arrival order rather than by threat level. Clearing bats aggressively while the slow half is still crossing converts a seven-creature wave into two three-creature ones.
Where waves come from in each game
Sword Quest is the purest version: a bounded arena, waves announced on a card, score from kills.
Castle Defender spawns along a lane toward a gate, so the composition question carries an extra term - what will reach the gate if I do nothing.
Knight Quest embeds waves in a room-based dungeon, so wave composition also determines whether the room is worth clearing or worth leaving.
Dragon Treasure uses a single boss instead of a wave, with adds composed from the same roster. The budget logic still applies to the adds, which is why the boss fight gets harder in a way that feels structured rather than arbitrary.
Why a bigger wave is not always a harder one
A wave of twelve identical goblins is not twelve problems. It is one problem repeated, solved by a single answer applied over and over - and once you have that answer, the wave contains no decisions at all.
Six creatures of five types present five different questions arriving at five different speeds, and the player has to switch between answers rather than repeat one. That is harder despite being half the size.
This is why the count cap exists at fifteen or sixteen. Past that point, adding bodies stops adding difficulty and starts adding only duration, which is the least interesting axis a fight can grow along.
It also explains the shape of a typical run. The middle waves are where raw numbers peak against a limited roster; the late ones are smaller relative to their roster and considerably more dangerous.
Key takeaways
- Two things grow: the count, and which species are eligible to fill it.
- Unlock schedule: goblins from wave one, bats two, slimes three, wraiths five, dragonlings six, golems seven.
- No more than one ranged creature per three, and every wave opens with a goblin.
- Every fourth wave in Sword Quest, every fifth in Castle Defender, is cut to about 55% size.
- Ask three questions before the first creature arrives: how many, from where, and what will not join the queue.
- Arrival order is by speed - bats 158, goblins 128, wraiths 104, dragonlings 96, slimes 74, golems 52.
Frequently asked questions
Why do waves suddenly get harder around wave five?
Because wraiths, dragonlings and golems all unlock between waves five and seven. That is where a single approach stops working, across about twenty seconds.
Is every fourth wave really easier?
In Sword Quest, yes - it is cut to roughly 55% of its normal size. Castle Defender does the same on every fifth wave. The between-wave card tells you when one is coming.
What should I do during a breather wave?
Everything that is not fighting: sweep up treasure you left behind, collect a power-up you skipped, and move to a wall before the next wave.
Can a wave be all dragonlings?
No. At most one in three creatures may be ranged; anything beyond that is replaced with a goblin, because closing distance under fire from two directions has no non-guess answer.
Why does every wave start with a goblin?
So that a wave never opens with a species you have not fought. When something new appears, the rest of the wave is already legible.