A case study in room design, pacing, waves, and audio-visual identity
BSc (Hons) Game Design & Development
What happened in it, and what came just before it?
How rooms, timers, multipliers and belts shape a run of an arcade game.
Plan rooms with an intensity curve and a teach, test, twist structure.
Combine enemy roles and difficulty dials so each room asks one clear question.
Use colour, contrast and sound so a busy screen stays readable.
Rooms, timer, multiplier, belts, modes
The room as a unit; curves at every scale
Enemy roles, mini-bosses, difficulty dials
Readability, identity, comparison
Design a five-room sequence
Fast loops feed slow ones; multipliers and ranks are rewards.
Tension then release; each peak a little higher; checkpoints.
Micro-mechanics, juice and feedback in the hands.
One endless arena where pressure keeps rising.
Same genre, same launch month, opposite structure. Mutant Storm cuts the arena into 89 authored rooms, so the designer decides what happens, and in what order.
Two people, 89 rooms, one very bright screen
Mutant Storm Empire (2007): four worlds, rooms joined into one seamless space.
Search: Mutant Storm Reloaded gameplay. Two minutes is enough.
Each room is a short, sealed challenge: kill everything before the timer runs out. Time left over becomes points.
Around it, a slower loop: survive more rooms and the multiplier and belt climb.
×2 · ×3 · ×4
Rises the longer you go without losing a life. Combined with the time bonus, it rewards fast and safe, which pull against each other.
0% → 700%, one belt per 100%, starting at white
Twenty rooms without dying to move up. Higher belts: faster, harder enemies and better scoring. Lose a life and you can drop a belt.
The belt is difficulty earned by performance: the game only gets harder when you've shown you can cope.
GDnD wiki · Risk/RewardShort rooms make every room a closure point: a natural place to stop, retry, practise and compare scores.
GDnD wiki · Closure PointsWhat happens to the cost of dying, and to "one more go"?
What can you control that an endless arena can't?
What do you lose? What has to be built 89 times?
The room is the unit you design. The sequence is the experience.
| Decision | Question | In a twin-stick room |
|---|---|---|
| The space | What shape is the arena? | Open floor, pillars to hide behind, a narrow corridor, walls that box you in |
| Initial conditions | What's there when you enter? | Where enemies start, where you start, any pickups |
| The challenges | Which enemies, in what order? | Spawn waves: who comes first, from where, how fast |
| Termination | How does it end? | All enemies dead (win) or timer and lives gone (lose) |
| Aesthetics | How does it look and sound? | Colour palette, background pattern, music intensity |
Every room opens with something to react to.
Busy rooms, then calmer ones; busy waves, then a lull.
Each set of rooms builds to its hardest room.
The new enemy alone, in an open room, with time to watch it.
Mixed with enemies you know. Can you handle it now?
A tight room, turrets, or a combination that changes the answer.
A final room or mini-boss that uses everything, then release.
In a sequence of rooms, the new idea should always arrive when the screen is calm.
GDnD wiki · Smooth Learning CurvesA visible countdown makes the goal urgent. No camping in a safe corner.
Time left becomes points: speed is scored, not just survived.
A shorter timer makes the same room harder, without adding a single enemy.
Tune the timer per room: generous for teach, tight for test.
GDnD wiki · Time LimitsEach enemy asks the player a different question
Slow, predictable target. Rewards aim and keeps the multiplier ticking.
asks: aimComes straight at you. Forces you to move while you shoot.
asks: moveStationary; controls part of the room. Makes space dangerous.
asks: routeMany weak enemies at once. Tests crowd control.
asks: sweepNeeds many hits and a strategy. Holds the room's climax.
asks: planA good wave combines two or three questions. A great room asks them in a new order.
GDnD wiki · Challenge TypesA flash or sound where enemies will appear, never on top of the player.
A second to breathe and reposition: the valley in the curve.
On a kill count or a time, so fast players see the next wave sooner.
Every big attack has a visible wind-up: a glow, a pause, a sound.
A vulnerability the player can find, so it's a puzzle as well as a fight.
Behaviour changes at a damage threshold: a mini-closure inside the room.
A mini-boss at the end of a set of rooms should ask for the skills those rooms just practised.
If it needs something new, that's a twist, and it needs a tell.
| Dial | What changes | How it feels |
|---|---|---|
| Count | More enemies at once | Busier, more to track |
| Speed | Enemies move or fire faster | Less time to react (higher belts do this) |
| Mix | Roles combined that conflict | Harder decisions, not just harder aiming |
| Spawn timing | Waves overlap, shorter lulls | No time to breathe |
| Space | Walls, corridors, less room | Movement becomes the challenge |
| Timer | Less time to clear | Forces aggression and risk |
| Resources | No power-ups, fewer bombs | Skill alone (Tally mode) |
Psychedelic, but never unreadable
The background stays dark and low-contrast; anything that can hurt you is bright.
One colour per enemy family, so you can read a threat out of the corner of your eye.
Geometric, alien silhouettes: clarity over detail at speed.
Style is a promise to the player. Readability is what keeps it.
GDnD wiki · Colour Theory FundamentalsElectronic, pulsing, rhythmic: matches the speed of play and sets the urgency.
Each enemy type has its own sounds; bigger enemies sound deeper and more ominous.
Power-ups, belts, multipliers and time bonuses each get a short, distinct sound.
Vertical remixing: add or remove layers of one loop as intensity rises. Horizontal resequencing: jump to a different section at the end of a phrase. Both let a room's music build to its mini-boss.
| Mutant Storm Reloaded | Geometry Wars: Retro Evolved (Week 9) | |
|---|---|---|
| Space | 89 authored rooms, each with its own layout and look | One arena, the whole game |
| Pacing | Designed, room by room, by the designers | Pressure rises the longer you survive |
| Difficulty | Belts, earned by surviving rooms | Escalates within each run |
| Failure | Lose a room; checkpoints every 10 | Lose the run |
| Strength | Control, variety, teaching | Emergence, purity, "one more go" |
Neither is better. Choose authored or emergent pacing on purpose.
Short rooms make failure cheap and every room a closure point to retry, practise and score.
Interest curves are fractal: run, set of rooms, room, wave.
Teach, test, twist, conclude: new ideas arrive when the screen is calm.
Build waves from roles and turn one or two difficulty dials at a time.
Style must stay readable: dark ground, bright threats, a sound for every danger.
Design a sequence that introduces one new enemy
Paper first. Use the planner to check the curve, not to design it.
GDnD wiki · Arcade Classics as Learning Projects| Enemy · weight | Room 1 | Room 2 | Room 3 | Room 4 | Room 5 |
|---|
Role: swarm-maker: kill it carelessly and the room fills up.
Tell: it bulges and flickers before it splits.
Look: green hexagon; halves are smaller, paler hexagons.
Sound: a wet "pop" that rises in pitch with each split.
| Room | Role | Mix | Dial turned |
|---|---|---|---|
| 1 | Teach | 2 splitters, open room | Timer 60 s, generous |
| 2 | Test | 3 splitters, 4 drifters, 1 chaser | Mix: aim vs move |
| 3 | Breather | 6 drifters, a multiplier pickup | Count down, reward up |
| 4 | Twist | 3 splitters inside a ring of 4 turrets | Space: halves fill a small room |
| 5 | Finale | Mini-boss that spawns splitters, 3 chasers | Higher belt: halves split again |
One thing that works.
One room where you'd die without knowing why, and the fix.
Would you press retry?
“In our sequence, the player first meets the new enemy in room …, because ….”
One sentence each, before you leave.
Adams, E. (2014) Fundamentals of Game Design. 3rd edn. Berkeley, CA: New Riders.
Bizarre Creations (2005) Geometry Wars: Retro Evolved [Xbox 360]. Microsoft Game Studios.
Björk, S. and Holopainen, J. (2005) Patterns in Game Design. Hingham, MA: Charles River Media.
Brown, M. (2015) 'Super Mario 3D World's 4 step level design', Game Maker's Toolkit [YouTube].
PomPom Games (2002) Mutant Storm [PC]. PomPom Games.
PomPom Games (2005) Mutant Storm Reloaded [Xbox 360]. Microsoft.
Schell, J. (2008) The Art of Game Design: A Book of Lenses. Burlington, MA: Morgan Kaufmann.
Wikipedia (n.d.) 'Mutant Storm Reloaded'. Available at: https://en.wikipedia.org/wiki/Mutant_Storm_Reloaded (Accessed: 10 October 2026).
Level Design · Interest Curves · Smooth Learning Curves
Closure Points · Time Limits · Risk/Reward · Game Loops
Boss Monsters · Challenge Types · Difficulty
VFX Value and Colour · Colour Theory Fundamentals · Interactive Music Techniques · Music in Games