Chain Reaction
Shoot linked nodes in order before each one's timer runs out.
Tests: Aim, timing, a little memory
Case study · Systems design
A two-player arcade shooter where one player can only hit Fire targets and the other only Ice.
>3x
player turnover in playtests
3:15
to beat the game, down from 5–5.5 minutes
1–2 min
typical run, down from 5 to 6 minutes
8–12
in-person playtest sessions
Shoot linked nodes in order before each one's timer runs out.
Tests: Aim, timing, a little memory
Shoot enemies before they land.
Tests: Reaction speed, aim, target priority
Clear columns from the front before each timer bar empties.
Tests: Timing, pattern memory
The camera moves on a rail while enemies drift in, giving players active downtime.
1st minigame run
Teaches the game and gates new players.
Chain Reaction
Raining Enemies
Stacked Enemies
2nd minigame run
The same three, harder, to prove mastery.
Chain Reaction
Raining Enemies
Stacked Enemies
The camera moving on the rail between minigames.
5–5.5 min → 3:15
8 Jun · inherited
21 Jul · shipped
0.2 to 0.3 s faster per visit
1st visit
2nd visit
Coin flips → rules
8 Jun · coin flips
21 Jul · alternating
Fire, player one Ice, player two
Before
Every target a coin flip
One possible deal. Nothing stops four in a row.
Chain Reaction, first visit
Strict alternation
Always opens on Fire and carries over from one chain to the next.
Chain Reaction, second visit
Alternation in pairs
Same rule with the streak length set to 2.
Raining Enemies
Free rolls, never three in a row
After two of a colour the next is forced to the other.
The front row is always split
8 Jun · per column
21 Jul · per row
| Stack 1 | Stack 2 | Stack 3 | |
|---|---|---|---|
| Front | Fire | Ice | Fire |
| Row 2 | Ice | Fire | Ice |
| Row 3 | Fire | Fire | Ice |
| Row 4 | Ice | Ice | Fire |
A runaway curve, straightened
Shrinking the gapSpawns per second
| Enemies per second | 0 s | 5 s | 10 s | 15 s |
|---|---|---|---|---|
| Shrinking the gap | 1.05 | 1.43 | 2.22 | 3.33 |
| Spawns per second | 1.25 | 1.88 | 2.50 | 3.13 |
25%, and it stays 25%
No tutorial mode needed

Step 1
0:31
Rail, after the first Chain Reaction

Step 2
0:42
Raining Enemies
Times from the start of play in one run of the final build.
After three fails on the same chain, the game moves the pair on, so no one spends a whole run stuck in one place.
Each new system went in with the old behaviour one checkbox away, so I could play both back to back before committing.
Where runs ended in the final weeks of playtesting.
Wall 1
0:30
Chain Reaction
Passed by the 2nd–3rd play
Wall 2
0:50
Raining Enemies
Passed by the 7th–9th play
Wall 3
1:45
Chain Reaction, 2nd visit
Usually not passed by the 12th play
Win
3:15
Victory
Reached rarely
Chain Reaction, first node
Chain Reaction, each later node
Stacked Enemies, each enemy
Raining Enemies, fall speed
4.0 became 5.4
Raining Enemies, spawn rate at the start
1.0 per second became 1.25 per second
Timer cut on each return visit
none became 0.2 to 0.3 s
Shielded rain enemies
20%, flat became 25%, plus 15 points per visit
Fails before a chain is skipped
no limit became 3
| Setting | Before | After |
|---|---|---|
| Raining Enemies, fall speed | 4.0 | 5.4 |
| Raining Enemies, spawn rate at the start | 1.0 per second | 1.25 per second |
| Timer cut on each return visit | none | 0.2 to 0.3 s |
| Shielded rain enemies | 20%, flat | 25%, plus 15 points per visit |
| Fails before a chain is skipped | no limit | 3 |
At handover I left a tuning guide in the project's README: every dial by minigame, split into what changes within a minigame and what changes on each visit.
I built Easy, Intermediate and Hard and cut them in the final week: no time to tune three levels well. The per-visit ramp they sat on stayed.
Switched off with a bypass on its trigger rather than deleted, so it can come back.
On 16 July one pasted-in file silently dropped the spawn-rate work and started Raining Enemies twice. Three reverts later, I put features back one at a time.
Moving the rain closer put the outer spawn points off screen, and those enemies still cost health. Spawns now get checked against the camera's view.
Players feel enemies per second, not seconds between enemies.
In co-op, who gets the next target is part of the difficulty.
A scripted first encounter did the job a tutorial mode would have.
The first streak-breaker felt right and quietly changed the shield rate.
Playing old and new back to back settled questions faster than arguing them.
Replacing whole files at once was fast until it wasn't.