Another New IP Idea

tim-cain game-design death-mechanic permadeath body-swapping rpg new-ip

Abstract

Problem: How do you make death meaningful in an RPG without save-scumming, while also creating a unique progression mechanic?

Approach: Tim Cain shares a concept from his design notebook — a fantasy RPG with no manual saves where dying causes the player to become whatever killed them.

Findings: The mechanic creates fascinating emergent scenarios but introduces serious design challenges around non-humanoid bodies, environmental deaths, inventory systems, and exploitable progression.

Key insight: A single bold mechanic can generate enormous design space — both creative opportunities and thorny problems — and the best game ideas are often the ones that raise more questions than they answer.

Source: https://www.youtube.com/watch?v=x_a_jGNKonk

1. The Core Concept

Tim Cain presents an idea from his notebook for a standard fantasy RPG (think Temple of Elemental Evil, Arcanum without the Industrial Revolution, Lord of the Rings) with one radical twist: when you die, you become your killer.

The game uses an Iron Man-style save system — no manual saves, only auto-saves when you quit. If you die, that's permanent. But instead of game over, your soul jumps into the body of whatever killed you.

2. How Progression Works

There are no levels in this game. Advancement happens through death itself:

  • Whatever kills you is probably stronger than you — so you upgrade by inhabiting their body
  • You inherit all of their items plus all of your items
  • The progression loop is: play → die → become your killer → continue as a stronger entity

3. Interesting Scenarios

Tim highlights several situations that make this mechanic compelling:

  • The Executioner: You commit a crime, get caught, and are executed. Now you're the executioner standing over your own headless body. What do you do next?
  • The Wizard's Patron: You kill a wizard and inherit their body, but shortly after, their demon patron appears. The demon senses a new soul and revokes the wizard's powers — unless you're willing to sign a contract. Do those powers follow your soul when you die again? Is there a clause for that?
  • The Bandit: A simple roadside ambush kills you. Now you're the bandit, standing over your own corpse with all your gear.

4. The Problems

Tim is candid about why this idea stayed in his notebook. The design challenges are substantial:

4.1. Environmental Deaths

  • What happens if you're killed by a trap or fall off a cliff? You can't become gravity or the planet. Is that just game over?

4.2. Weak Enemies in Groups

  • A pack of wolves overwhelms you. Now you're a single weak wolf — your progression resets dramatically. Is that fun or just frustrating?

4.3. Non-Humanoid Bodies

  • Undead: Are you now a mindless zombie?
  • Ghosts: You're immaterial. How does inventory work? Do items drop to the ground?
  • Wolves/Animals: Can they talk? Can they use wands or read scrolls? "Not like wolves have little backpacks on"
  • Dragons: Can they even fit into towns or dungeons?
  • Demons: Now you're an extraplanar creature
  • Gods: If a god kills you at an altar, are you now a god?

4.4. Exploitable Advancement

Players will figure out the system and intentionally let powerful enemies kill them — "I'm tired of playing this, I'm going to go let that powerful Paladin kill me" — turning death-as-progression into a cheese strategy.

4.5. Save Corruption and Crashes

With only one save file, a crash or corruption means total loss. Players will inevitably create backup copies and mods to circumvent the system.

5. Tim's Conclusion

Tim acknowledges the idea has extensive pros and cons in his notebook but he never solved all the problems. He throws the concept out to his audience, suggesting maybe someone can crack it — perhaps even pulling it out of the RPG genre into a puzzle game format. His attitude captures something essential about game design: not every idea needs to ship, but every idea is worth exploring.

6. References