Enemy Design
Making meaningful opposition
Enemy design creates opponents that challenge, teach, and engage players through behaviour patterns, visual communication, and balanced difficulty.
Overview
Good enemy design serves multiple purposes simultaneously: challenge the player, teach mechanics, communicate clearly through visuals, vary the gameplay loop, and create memorable encounters. The Goomba’s simple walk pattern teaches Mario to jump in 5 seconds. The Cucco in Zelda teaches that retaliation has consequences. Pac-Man’s four ghosts teach that AI can have personality. Dark Souls bosses teach learnable rhythms with high stakes. Bad enemies frustrate; good enemies create stories players retell decades later.
Fast facts
- Purpose: Create meaningful gameplay opposition that serves the game’s design goals.
- Elements: Behaviour, visual design, audio cues, placement, telegraphing.
- Communication: Attacks should signal intent before connecting.
- Progression: Enemy complexity increases with player skill.
- Variety: Different enemies demand different strategies — homogeneous enemies bore quickly.
Design principles
The well-known principles of enemy design (drawn from designers like Mark Brown’s Game Maker’s Toolkit, Jonathan Blow, the Soulsborne school, et al.):
| Principle | Description | Example |
|---|---|---|
| Readable visuals | The enemy’s silhouette communicates threat type | Dark Souls — knights vs hollows vs giants are visually distinct |
| Telegraphed attacks | Attacks have a wind-up the player can recognise | Mega Man bosses, Souls bosses, Hollow Knight bosses |
| Fair feedback | When the player loses, they understand why | Spelunky — every death has a clear cause |
| Pattern learnability | Behaviour can be recognised and countered | Mega Man boss patterns, Pac-Man ghosts |
| Distinct roles | Each enemy fills a different gameplay niche | Doom — imp (basic), pinky (charging), revenant (rocket-tracking) |
| Counter-mechanics | Enemies push players to use specific tools | Zelda — bombs for these enemies, arrows for those |
| Escalating complexity | Later enemies combine earlier mechanics | Castlevania — bone tower above moving platform |
Designing for teaching
Enemies are the primary mechanic-teaching tool in many games:
- Goomba (SMB World 1-1) — teaches “jump” with no risk if you fail
- Koopa Troopa — teaches that some enemies survive jumping; introduces the shell
- Piranha Plant — teaches caution around pipes; you can’t always rush
- Lakitu — teaches the screen has a top edge that has stuff
- Bullet Bill — teaches that danger comes from off-screen
Mario’s first world teaches its core verb-set entirely through enemy encounter, with no text. This is the gold standard.
Behaviour archetypes
Most enemies fall into a small set of archetypes:
| Archetype | Behaviour | Examples |
|---|---|---|
| Walker | Patrol left/right, turn at edges | Goomba, Koopa, Octorok |
| Charger | Stand still until provoked, then rush | Pac-Man’s Blinky in chase mode, Doom’s Pinky |
| Ranger | Stay back, fire projectiles | Hammer Bro, Doom’s Imp |
| Patroller | Fixed patrol route | Castlevania medusa heads (sin-wave), most stealth-game guards |
| Ambusher | Hide until player approaches | Resident Evil’s lickers, Dark Souls mimics |
| Defender | Guard a specific position / object | Boss generals, gateway monsters |
| Mimicker | Copy player abilities | Mega Man X’s Mavericks, Smash clone characters |
| Shielder | Block from specific angles | Souls shielded enemies, Splash Woman |
| Boss | Multiple phases, learnable patterns | Almost any genre’s boss class |
Classic examples
| Game | Enemy | Why it works |
|---|---|---|
| Pac-Man | Four ghosts with personalities | Each ghost is a distinct AI; emergent interaction creates pressure |
| Super Mario Bros. | Goomba (basic), Koopa (shell), Hammer Bro (telegraphed range) | Teaches the move-set through encounter |
| Castlevania | Medusa Heads | The “frustrating” classic — sin-wave path forces precise timing |
| Metroid | Metroids themselves | Defining the eponymous threat with simple physics + power |
| Dark Souls | Crystal Lizard | Fleeing collectible — different verb (hunt) within combat verbs |
| Hollow Knight | False Knight, Mantis Lords | Telegraphed multi-stage bosses with fair learn-ability |
| Doom (1993) | Imp / Cacodemon / Pinky / Revenant | Each one demands different room positioning |
| Half-Life 2 | Headcrabs / Antlions / Combine soldiers | Distinct silhouettes, distinct counters |
| Bloodborne | Father Gascoigne | Multi-phase tutorial-boss teaching parry, dodge, transform |
Visual language
Effective enemies have distinctive silhouettes — recognisable in a crowd, at small size, in low-light. Designers test silhouettes against:
- Pure-black silhouette test — if you can recognise the enemy from outline alone, the silhouette is good
- Tiny-icon test — the silhouette must work at minimap scale
- Crowd test — multiple enemies of different types should be distinguishable at a glance
Colour reinforces silhouette: red = aggressive (Mario’s red Koopa), blue = ranged, green = poisonous, etc.
Audio cues
Enemy audio is nearly as important as visuals:
- Idle / patrol audio — lets players track unseen enemies (Cacodemon’s hiss, Souls knights’ clanking)
- Aggro audio — distinct sound when enemy notices player (Skyrim’s “by the hammer of Talos!” alert)
- Attack telegraph audio — the wind-up sound (Mega Man’s gun charge, Souls’ weapon swooshes)
- Death audio — satisfaction signal (Doom’s grunts, Mortal Kombat’s screams)
Modern design tools
| Approach | Description |
|---|---|
| Encounter design | Place enemies in groups that create combat puzzles |
| Wave design | Sequenced enemy spawns that escalate complexity |
| Roguelike spawning | Procedurally combine enemy types with constraints |
| AI directors | Left 4 Dead, Resident Evil 4 — dynamic spawning based on player state |