Tuning a survivor-like means playing every survivor-like you can get your hands on. Not for inspiration, exactly — the genre's silhouette is solved, the core loop is everyone's at this point — but as a reference set. When a level-up choice in FOXFIRE feels flat, the question is whether Vampire Survivors would have made the same choice feel like a reward. When the run pacing dips at minute eight, the question is whether Halls of Torment would have ramped the threat sooner.
Five games we keep going back to, and what each one teaches us when we put it on a screen next to FOXFIRE.
Vampire Survivors — the auto-fire rhythm
The reference everyone names because it's the reference everyone has played. Luca Galante's original is still the cleanest study of how to make weapons feel like they're firing themselves for the player rather than at the screen. The audio cue per shot is doing more than most devs notice; the projectile arcs sing because there's almost no input contention competing for the player's attention.
What we take: pacing of the first three minutes. Vampire Survivors introduces a new system every thirty seconds for the first stretch of a run — weapons fire, enemies arrive, XP appears, level-up offers a choice, more enemies, evolution chimes hint at depth — and the player never feels lost because each system arrives as a single new thing to read. We've spent more time than is reasonable trying to match that learning curve in FOXFIRE's tutorial run.
What we don't take: the frictionless WASD. Vampire Survivors works because movement is a state machine; FOXFIRE is the bet that survivor-like fans want the version where movement is a system. That bet might be wrong. We won't know until launch.
Brotato — build depth as the only progression
Brotato's secret is that every weapon in the roster is a different verb. The Pistol is positioning, the Minigun is commitment, the Slingshot is patience. There's no "weak weapon" the player has to suffer through — just a weapon whose grammar hasn't matched the run yet. The Brotato roster is a study in how few words a designer needs to make a sentence interesting.
What we take: the principle that every weapon in FOXFIRE should be the answer to a different question. The Mining Laser is for the player who wants to hold a corridor. The Ballistic Gun is for the player who likes to read crowd density. The Anchor is for the player who can't stop accelerating and wants to make the wake count. If a weapon doesn't earn a different verb than the other eighteen, we cut it.
What we don't take: the arena. Brotato runs are static spaces with timers; FOXFIRE runs are travel. The space changes around the player as the FTL drive charges, and the late run is geographically different from the early run because the player has actually moved.
Nova Drift — the closest peer in mechanics
Nova Drift is the survivor-like FOXFIRE gets compared to most often by anyone who has actually played both. Justin Pixelblade Stander built a thrust-based ship game where every system upgrade rewrites how the ship handles, and it's the closest thing to FOXFIRE's hull-as-toolkit philosophy in the live market.
What we take: the lesson that thrust physics doesn't have to be punishing. Nova Drift handles inertia generously — ships have enough damping that new players acclimate inside a run, and the high-skill ceiling reveals itself through modifier choices rather than pure piloting. FOXFIRE's Military hull is downstream of that lesson. We added rotation and damping to Military specifically because Nova Drift taught us that the alternative wasn't going to bring anyone with us.
What we don't take: the arena, again, and the modular ship. Nova Drift is a single ship the player customises through runs; FOXFIRE is five distinct hulls that don't share parts. Different shapes for different design goals.
Cobalt Core — run pacing within a roguelite
Cobalt Core isn't a survivor-like. It's here because nobody in the roguelite space has built better run-to-run momentum than Rocket Rat Games. The way the ship dialog timing escalates per node, the way each act ends on a beat that promises the next one, the way the final-act music change rewires the player's posture — this is run-pacing as a craft.
What we take: the principle that a run should know it's ending before the player does. FOXFIRE's last 100 seconds are the FTL escape window because we wanted the run's structural climax to be a beat the player feels, not just a final boss. Cobalt Core taught us that giving the player time to register the climax is more important than giving them a new mechanic at the climax.
What we don't take: the deckbuilder layer. Different game.
Halls of Torment — environmental density and threat reading
Halls of Torment is the survivor-like that holds up after the genre had time to refine itself. Chasing Carrots took the Vampire Survivors loop and re-tuned it around Diablo's visual language: the screen reads as a place rather than a backdrop, threats arrive with telegraphs the player has time to parse, and the build pressure forces decisions instead of just rewards.
What we take: the threat-reading model. FOXFIRE's offscreen indicators owe more to Halls of Torment's ranged threats than to any space-sim ancestor. The principle that "things you can't see should still be legible" is the central design constraint of FOXFIRE's HUD, and watching Halls of Torment's arrows fly in from offscreen is how we keep our own ones honest.
What we don't take: the dungeon. FOXFIRE's stages are open space; Halls of Torment's are walled rooms. Trade-offs at the spawn-design level cascade differently in each.
What this taught us this week
Two playtests ago, FOXFIRE's Stage 2 was leaving players in a quiet patch around the eight-minute mark. A combination of low spawn pressure, a too-spread-out level, and a level-up rhythm that had peaked too early. We weren't sure where the slack was coming from until we re-read what each of the five games above does with their minute-eight equivalent.
Vampire Survivors drops a new evolution prompt. Brotato escalates the wave intensity but not the wave count. Nova Drift opens a new system tier. Cobalt Core changes the music. Halls of Torment introduces an offscreen ranged threat that demands repositioning. Five different solutions to the same pacing problem.
What we ended up doing for Stage 2: introducing a beam artillery weapon that fires from offscreen, telegraphed across two beats, that the player has to actively hunt or actively dodge. Not exactly any of those five solutions; closer to Halls of Torment than the others. Three more playtests since and the eight-minute slack is gone.
That's the work. Play the genre, find the slack, ask what each peer would have done. Then build the version that fits the shape of the game you're already making.