The Making of 'Deep Rock Galactic: Survivor' | Two Game Directors Tell Their Stories
summary
Prototype starts as Vampire Survivors + mining, built in days, scaled to a demo in ~11 months and then early access that draws million users first month. Key choices: keep the 30‑second drop‑pod timer despite vocal complaints (inspired mutators and risk/reward), banish dash to protect mining, add hazard difficulty tiers after player uptake, and replace visual clutter with a pushback mechanic. Community influences features via a small tester council and data‑scraped feedback; rapid changes sometimes backfire.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:23Game directors
- 3:08Talk title meaning
- 4:51Funday Games
- 5:36Survivor's birth
- 7:00Prototyping early dev
- 8:22Prototype to Steam Fest
- 9:27Creative ownership vs team
- 10:51IP owner collaboration
- 11:12Community reaction
- 11:56Early player feedback
- 13:20Drop pod timer debate
- 16:30Design pillars & IP
- 17:10Scaling million-player feedback
- 19:36Community vs game design
- 23:30When advice backfires
- 26:37Other production signals
- 27:19Dash mechanic debate
- 29:03Prototyping DLC ideas
- 30:49Hazard levels before release
- 32:54Balancing difficulty with IP
- 33:36Handing over director role
- 36:22Living roadmap challenges
- 39:54Q&A
related talks
29mDeep Rock Galactic Survivor – Fireside chat
58mCurrent challenges for game developers
43mGame Design lessons from designing Football, Tactics & Glory
49m"Age of Vaporum". What we've learned from the releases of 2 games and pitching process of the third.
01h 06mStorm Boy: The Game Game Director Postmortem
22mWhy mobile developers should focus on the meta game first
57mGameDev and Post Trauma
19mHow premium games can succeed