Guide

Horde survivor game design explained

The screen fills with hundreds of enemies while your weapons fire without you pressing a single attack button. You weave through the swarm, vacuuming glowing gems, and every level-up pauses time just long enough to pick whether tonight’s build leans into garlic auras or piercing magic wands. That is the horde survivor contract — also called bullet heaven — popularized by Vampire Survivors and cloned across mobile, PC, and console. Unlike classic twin-stick shooters where aim skill dominates, horde survivors sell positioning, buildcraft, and escalation spectacle. This guide covers subgenre variants, the move-collect-level core loop, auto-weapon and passive systems, XP magnetism and pick-screen UX, evolution recipes, spawn directors and performance budgets, meta-progression ethics, a Harbor Swarm worked example, subgenre decision tables, common pitfalls, and a production checklist alongside our twin-stick shooter guide, roguelike design primer, and object pooling fundamentals.

What defines a horde survivor

Horde survivors are top-down (or isometric) action games where the player controls movement only while weapons attack on timers or triggers. Runs are short, enemy counts are enormous, and power spikes come from stacking upgrades rather than manual execution. Players expect:

Auto-combat — weapons fire, orbit, or pulse without a dedicated attack input; skill is where you stand, not frame-perfect clicks.
Exponential on-screen chaos — enemy and projectile counts rise until the screen looks unplayable — then your build catches up and flips the power fantasy.
Interrupt-driven progression — level-ups pause or slow time and offer curated choices; chests and bosses deliver jackpot moments.
Session-friendly length — 15–30 minute runs fit commute and stream slots; endless modes are optional endgame.

Adjacent genres

Classic twin-stick shooters require manual aim; see our twin-stick guide for arena wave design. Roguelite deckbuilders share pick-one-of-three pacing but replace spatial positioning with hand management. Tower defense inverts agency — you place static towers instead of kiting a hero. Idle games remove reflex tests entirely. Horde survivors sit in the sweet spot: low input load, high visual payoff, meaningful build decisions.

Subgenres: timed survival, stage gauntlet, and hybrid roguelite

The Vampire Survivors formula is not the only viable structure. Pick your subgenre before balancing weapons — it changes spawn math, UI, and monetization.

Timed survival (bullet heaven classic)

A single arena, fixed duration (often 30 minutes), escalating waves until a final boss or death screen. Player power curves exponentially; the last five minutes should feel like a fireworks show. Examples: Vampire Survivors, Holocure. Design focus: clock pacing, evolution timing, and performance at peak density.

Stage gauntlet / room ladder

Discrete stages with shops or perk stations between waves. More roguelite DNA: mistakes carry across stages, rerolls cost currency, bosses gate advancement. Examples: Brotato (wave arenas), 20 Minutes Till Dawn. Design focus: inter-wave economy and build pivot tools.

Reverse bullet heaven / auto-battler hybrid

Minimal movement; positioning is grid or lane based while units auto-fight. Examples: some auto-battler modes, experimental mobile titles. Design focus: pre-run loadout and synergy UI rather than kiting skill.

Narrative or mission wrapper

Horde core loop inside quests, biomes, and unlockable characters. Retention comes from content gates, not just power creep. Risk: over-building story infrastructure before the 10-minute loop is fun.

The core loop: move, collect, level, escalate

Every horde survivor repeats this micro-loop hundreds of times per run:

Move — create safe pockets in the swarm; speed stats and dash cooldowns are primary defensive tools.
Collect — kill drops spawn XP gems (and gold, health, magnets); collection radius is a feel lever as important as DPS.
Level — XP threshold triggers pick screen; three (or four) options with rarity weights; duplicates level existing weapons.
Escalate — spawn director raises enemy HP, speed, and elite frequency; screen density is the difficulty clock.

Early loop cycles should complete in 5–15 seconds. If players run 30+ seconds without a level-up or chest in the first five minutes, the run feels sluggish — tune XP curves, not just spawn rate.

Input and accessibility

One-stick (or WASD-only) control is a feature, not a compromise. Support optional manual aim overlays for hybrid weapons, but default to movement-only. Mobile needs virtual stick dead zones and auto-pause on level-up. Colorblind-safe gem and projectile palettes are mandatory at bullet-heaven densities; see HUD readability principles.

Auto-weapons, passives, and evolution recipes

Weapons are the vocabulary of buildcraft. Each should have a distinct spatial pattern (orbit, cone, random strike, aura) and cadence (steady DPS vs burst).

Weapon categories

Orbitals — rings around the player; teach spacing without aim; scale with area and count.
Directed bursts — fire toward nearest enemy or movement vector; need target-priority rules to avoid feel RNG.
Ground effects — puddles, lightning fields; zone control rewards looping paths.
Summons — pets with independent AI; cap count early to protect performance.
Passives — move speed, cooldown reduction, pickup radius, armor; glue that makes weapons hit breakpoints.

Level caps and duplicate picks

Standard pattern: six to eight levels per weapon, duplicate picks on the level-up screen increase stats or add projectiles. Show level pips on the HUD so players plan evolutions. Hide max-level weapons from the pool to reduce dead offers.

Evolution / fusion combos

Signature jackpot: max-level weapon plus specific passive transforms into an evolved form (garlic plus pummarola, whip plus hollow heart). Recipes should be discoverable in-run via tooltips, not only wiki archaeology. Gate evolutions after the 10-minute mark so mid-run power spikes land when spawns intensify. Document all recipes in a codex unlocked permanently — meta knowledge is retention fuel.

XP gems, magnets, and pick-screen UX

Collection feel separates polished horde survivors from clones. Gems should snap toward the player with audible ticks; vacuum radius upgrades produce dopamine spikes.

XP economy tuning

Plot XP required per level on a gentle exponential. Early levels every few seconds; late levels every 30–60 seconds at peak intensity. Boss kills and treasure chests grant burst XP to guarantee a pick during breather beats. If players die before their first evolution, the curve is too slow or offers are too weak.

Level-up screen rules

Pause or heavy slow-mo — never punish reading; mobile needs full pause.
Three choices default — fourth slot as paid reroll or rare lucky draw.
Weighted rarity — commons fill gaps; rare weapons spike excitement; ban dead duplicates until weapons maxed.
Synergy hints — subtle icons showing evolution progress toward recipes.
Skip or banish — veteran players need opt-out of unwanted weapons to protect build identity.

Chests, bosses, and jackpot pacing

Timed elite waves or glowing bosses drop chests that roll multiple upgrades at once — the “screen clear” fantasy moment. Space major jackpots 5–8 minutes apart in a 30-minute run. Pair with juice: fanfare, brief invulnerability, and gem fountains.

Spawn directors, enemy roles, and performance

Horde survivors live or die on spawn algorithms and frame rate. A naive uniform random spawn feels unfair; a director script feels cinematic.

Director inputs

Track run time, player level, recent damage taken, kill rate, and current entity count. Raise spawn budget when the player is cruising; ease off after near-death to avoid death spirals. Cap simultaneous enemies and projectiles per platform tier.

Enemy roles at scale

Chaff swarms — low HP, teach vacuum loops and AoE value.
Runners — close distance fast; punish straight-line kiting.
Tanks — HP sponges that block gem pickup lanes.
Ranged — force micro-dodges even in auto-attack games.
Elites — telegraphed silhouettes, drop chests or bonus XP.

Technical budget

Use object pooling for enemies, gems, and bullets. Batch draw calls; simplify collision to circles. LOD enemy animations off-screen. Target 60 FPS on Switch and mid-tier phones with 300+ active enemies — document your entity ceiling in design specs. Hitches during level-up pause are acceptable; hitches during swarm peaks are not.

Meta-progression, characters, and monetization ethics

Between runs, players expect unlocks that widen possibility space without invalidating skill.

Character roster — each character skews starting weapon and passives; avoid strictly better characters.
Permanent stat coins — small bonuses (+5% move speed) are OK; +50% damage trivializes runs.
Stage and weapon unlocks — content gating beats raw power.
Achievement codex — evolution recipes, enemy bestiary, speedrun timers.

Monetization: sell characters, stages, and cosmetics. Do not sell in-run power rerolls that guarantee evolutions in ranked modes. Rewarded ads for continue-on-death are common on mobile but erode PC premium trust — segment by platform. See monetization ethics for broader guardrails.

Harbor Swarm worked example

Picture Harbor Swarm, a 25-minute timed horde survivor set on a foggy dockyard map with three vertical acts.

Act 1 (0–8 min) — chaff crabs and slow dockworkers; XP curve grants level every 12–20 seconds; first chest at 5:00 guarantees one evolution ingredient.
Weapon palette — six base weapons (harpoon line, lantern aura, gull orbit, tide wave, net trap, coin shotgun) plus four passives (magnet, cooldown, armor, move speed). Eight documented evolutions, e.g. max harpoon plus magnet becomes Chain Harpoon.
Act 2 (8–18 min) — runners and ranged seagulls; director caps 220 enemies on screen; elite crate-boss every 4 minutes.
Act 3 (18–25 min) — fog shrinks playable area inward; damage aura unless player stands in lantern light; final boss drops cosmetic skin, not power.
Meta — unlock two alternate starters after first clear; permanent coin shop caps at +10% pickup radius total.

This skeleton ships a complete loop with one map, one boss, and codex hooks for future biomes without rewriting core systems.

Subgenre decision table

Design goal	Prefer	Why
Maximum casual reach	Timed survival, movement-only	Low input load fits mobile and stream background play.
Deep build optimization	Stage gauntlet with shops	Inter-wave economy enables pivots and hard counters.
Esports or skill branding	Hybrid manual aim variant	Pure auto-attack caps skill expression ceiling.
Short viral demos	10-minute demo cap	Steam Next Fest players must hit evolution fantasy fast.
Live service seasons	Character and biome unlocks	Content drops beat permanent stat inflation.
Low art budget	Top-down 2D with pooled VFX	Readable silhouettes matter more than 3D fidelity.
Co-op couch play	Shared screen with split XP magnets	Double spawn budget; color-code player bullets.
Narrative IP tie-in	Mission wrapper plus codex	Story justifies character roster without new mechanics.

Common pitfalls

Dead level-up offers — maxed weapons still appearing waste dopamine; filter the pool dynamically.
Invisible evolution requirements — players quit when wiki-dependent combos never proc.
Spawn cliffs at fixed timestamps — minute-20 death walls feel scripted; scale with player power signals.
Performance collapse at peak — the power fantasy requires smooth FPS; cap entities ruthlessly.
Unreadable projectile soup — enemy shots must use a dedicated palette; player AoE can blur together.
Pay-to-win rerolls — ranked boards die instantly when wallets buy evolution guarantees.
No early evolution tease — if first evolution lands after minute 15, demos refund.
Copying Vampire Survivors numbers verbatim — tune to your enemy HP and weapon DPS, not someone else’s spreadsheet.

Production checklist

Pick subgenre (timed vs gauntlet) and document target run length.
Prototype one weapon to level 8 with readable VFX on minimum spec hardware.
Ship XP curve spreadsheet tied to kill rate at minute 1, 10, and 20.
Implement weighted level-up pool with duplicate filtering and skip option.
Author at least six evolution recipes with in-game codex entries.
Build spawn director with entity caps and post-damage breather easing.
Pool enemies, gems, and projectiles; profile at 300+ on-screen entities.
Add magnet pickup audio layers and chest jackpot fanfare.
Design two starter characters with distinct first-five-minute fantasies.
Gate monetization to cosmetics and content; no ranked power purchases.
Playtest full 25-minute run without leveling — if possible, curve is broken.
Record peak-density clip for store page; bullet heaven sells spectacle.

Key takeaways

Horde survivors trade aim skill for positioning, build planning, and escalation spectacle.
Auto-weapons, passives, and evolution recipes are the retention vocabulary — document them in a codex.
XP magnet feel and pick-screen fairness matter as much as spawn rates.
Spawn directors and entity caps are core design, not late optimization polish.
Monetize characters and stages; never sell guaranteed power in competitive modes.