Case Study 21.2 — Hades: Relationship Progression Through Roguelike Repetition

Game: Hades (Supergiant Games, 2020) Director: Amir Rao Creative Director / Writer: Greg Kasavin Lead Voice Director: Darren Korb (also composer) Platforms: PC, Switch, PS4/PS5, Xbox One/Series, iOS Why it matters: Hades accomplished something most games assumed was structurally impossible: it told a deep, character-driven narrative inside a roguelike — a genre whose defining mechanic (restart from zero every run) had long been considered antithetical to storytelling. Supergiant's solution to this problem redefined what narrative in a systems-heavy game could look like. Hades won the Hugo Award for Best Video Game in 2021 — the first video game ever to do so — along with BAFTA, DICE, and countless Game of the Year awards. It is now the most cited example of how to integrate narrative and systems, and the reference text for any designer working on procedurally-heavy games with character ambition.

The Core Idea

Hades puts you in the shoes of Zagreus, the son of Hades, attempting to escape the Underworld. Each escape attempt is a run: you fight through four biomes, die (probably), and return to the House of Hades, the hub where you began. Then you try again.

This is a roguelike. The combat is roguelike. The upgrades reset every run. The biomes shuffle between attempts. Most narrative games that tried to integrate roguelike mechanics treated this repetition as a tension: how do we tell a story when the player restarts every hour? Supergiant inverted the problem. Repetition was not a storytelling obstacle; repetition was the story.

🎯 Tradeoff Spotlight: Most roguelikes accept that they cannot have deep narrative because players restart too often to maintain a through-line. Most narrative games accept that they cannot have roguelike replay because the narrative assumes unique progression. Supergiant's bet was that you could have both if you made repetition itself the narrative engine. Every death becomes a story beat. Every conversation progresses. Every run adds a little to the larger picture. The tradeoff is development cost (the writing volume is enormous) but the narrative payoff is a category-redefining game.

The Structure: Dialogue Per Run

Every time Zagreus dies, he returns to the House of Hades. In the House, he can talk to NPCs:

• Hades (his father), who is stern and disapproving
• Nyx (goddess of night, his true guardian), who is gentle
• Achilles (his trainer), who is wise and weary
• Hypnos (sleep god, hub greeter), who is comic relief
• Orpheus (court musician), who is depressed
• Dusa (gorgon housekeeper), who is anxious
• Cerberus (three-headed dog), who is goodest boy
• Meg, Dusa, Orpheus, Achilles — each with their own personal storylines

Outside the House, during runs, he can encounter:

• Olympians (Zeus, Athena, Artemis, Aphrodite, Ares, Demeter, Dionysus, Poseidon, Hermes) who grant boons and speak brief dialogue
• Mortal shades (Sisyphus, Eurydice, Patroclus) scattered across biomes
• Rival suitors (Megaera, Thanatos — potential romances)

Each NPC has dozens of dialogue exchanges. Each exchange advances a specific relationship arc. When you talk to Achilles the first time, he is formal and guarded. The fifteenth time, he shares his regrets about Patroclus. The fortieth time, he tells you about Patroclus in detail, and eventually asks for your help in a specific side quest. Every conversation is progression.

Why This Works

Three structural decisions make it work.

Conversations are fast. Most dialogue in Hades is 2-4 lines. You see it, you hear the voice-acted delivery, it ends, you can return for more when you like. The player's attention budget is respected. Unlike a BioWare conversation that demands five minutes of focus, a Hades exchange demands fifteen seconds. Players can have six or seven small dialogues between runs without fatigue.

Progression is gated by runs, not by meta-time. You do not get new Achilles dialogue by waiting around the hub. You get it by going on another run. Every run is an investment that yields both combat payout (resources, upgrades) and narrative payout (new conversations when you return). The gameplay-narrative loop is tight: play → die → return → talk → gain context → play again.

Nothing resets narratively. Your Zagreus keeps growing relationships across runs. You might be on escape attempt #47, and your relationship with Achilles is at relationship-level-47. The systems under the hood reset the run; the narrative systems keep progressing. The player never goes backward in their story.

💡 Intuition: The key insight is that roguelike systems and narrative systems can run on different clocks. The run is short and lossy. The narrative is long and additive. By separating these, Supergiant got the best of both genres — the thrill of roguelike combat and the depth of a narrative RPG. If you are designing a procedural or rogue-like-adjacent game, look for ways to make narrative systems persistent and run-systems resettable. The separation is what unlocks everything.

The Character Roster and Greg Kasavin's Voice Work

Greg Kasavin, Supergiant's creative director, wrote most of Hades's dialogue. His fingerprints are all over the craft:

Every god has a distinctive verbal tic. Zeus is grandiose and avuncular, booming about his "thunder." Aphrodite coos with languid sexual teasing. Artemis is blunt and solitary. Ares is thrilled by combat. Poseidon is bro-energy. Demeter is cold and mournful (it is always winter where she speaks). Dionysus is stoned. You can identify any of them from a single line.

Every god relates to Zagreus differently. They are all his distant family — nieces, aunts, uncles — and each has a different warmth-or-distance. Aphrodite flirts. Athena is protective. Artemis is curious. Demeter is suspicious (her daughter Persephone is Zagreus's mother, and the family history is... complicated). The relationships are not flat.

Conversations reference prior conversations. When Zagreus has done something for a god, they mention it. When he has failed them, they note it. The dialogue system tracks a running state that feels like memory.

The House NPCs each have their own storylines. Orpheus is depressed because he has lost Eurydice. His arc is you helping them reconcile, across many runs. Dusa's arc is about her growing confidence. Achilles's arc is about his reunion with Patroclus. Each is a small novella unfolding at the pace of your playthrough.

The Fates speak in song. Darren Korb's score integrates the Moirai's voices into musical themes. This is not technically "dialogue" but it is character through voice — and it is a uniquely Hades solution.

✅ Best Practice: Hades's companion writing exemplifies Rule 4 of the chapter (every character has a verbal tic). Supergiant did not treat verbal tic as an optional flourish; they treated it as foundational. Before any specific line was written, each god had a voice defined well enough that the writers could draft lines and know immediately whether each one was in-character. If you cannot describe your characters' voices in one sentence each, you do not yet know them well enough to write them.

Darren Korb's Voice Direction

Every line in Hades is voice-acted. The voice direction — by Darren Korb, who also composed the music — is exceptional. Korb cast actors who could carry distinct tones and then directed them to match the game's tone register: mythic but not pompous, dramatic but not self-serious, emotional but not saccharine.

Darren Korb himself voices Zagreus. Logan Cunningham (a Supergiant staple) voices Hades, Poseidon, and others. The ensemble pulls off an enormous quantity of dialogue without ever losing the through-line.

This is worth noting because most roguelikes are text-only or have minimal voice. Hades went all-in on voice and used it as a primary characterization tool. The result is that the game's NPCs feel like a cast rather than a roster.

The Romance System: Progression by Nectar and Ambrosia

Hades has a relationship system that looks, at first, like any BioWare romance. You talk to characters. You give them gifts (Nectar early; Ambrosia later for potential romance). Their relationship with Zagreus deepens.

But the system has distinctive properties:

You cannot rush it. Giving Achilles twenty bottles of Nectar in a single visit does not accelerate the relationship. Relationship progress is gated by runs and by narrative state. You have to live alongside these characters to know them.

Everyone can be approached. Every major NPC has Nectar-and-Ambrosia progression. You can pursue romance with Meg, Thanatos, or Dusa. You can pursue friendship with Achilles, Orpheus, and others. The system is not limited to a small pool of romanceable characters; it is the shape of all deep relationships in the game.

The romances are written with specificity. Thanatos's relationship with Zagreus is not a generic "we love each other now" — it is a delicate, complicated, slow romance between two beings who are both divine, both lonely in different ways, both wary of commitment. Meg is similar — an enemy who becomes a friend who becomes more, with each step earned.

Nothing is locked out. Unlike some games where choosing one romance locks the others, Hades lets Zagreus be romantically tied to Thanatos AND Meg simultaneously, with in-game acknowledgement of the polyamorous arrangement. This is handled with grace — the characters discuss it, agree to the situation, and it becomes an ongoing texture of the game rather than a checkbox.

📝 Note: The polyamorous romance in Hades was received positively by a large audience and is now a frequently-cited example of how game romance systems can break out of the "pick one and lose the others" pattern. It is not required for every game, but it demonstrates that the pattern is a design choice, not a structural necessity. Interrogate your defaults.

The Technical Architecture

Hades was built on Supergiant's proprietary engine (used across Bastion, Transistor, Pyre, Hades). The narrative system under the hood is a custom dialogue/trigger system that Kasavin's team designed specifically for the game's unique narrative needs.

Some design decisions worth noting:

Every line has a trigger condition. Lines are tagged with conditions — "if player has completed X," "if run count is Y," "if relationship Z is at N." The engine picks which line to play based on current state. This is a sophisticated extension of the flag-based system in this chapter's code examples.

Lines are ordered and priority-ranked. When multiple eligible lines exist, the engine picks one based on priority and shuffles variants to avoid repetition. Writers tag lines as "first-time important" vs. "ambient repeat" vs. "story-gated rare."

The writing volume is enormous. Estimates suggest 300,000+ words of dialogue across the game's 90+ NPCs. For an indie studio of ~25 people, this is an extraordinary amount of writing, all of it carefully voiced and integrated. It is also a massive production risk: if the volume is not matched by quality, the game collapses under its own weight.

Supergiant managed the volume with tight editorial control. Kasavin was the primary writer; the team worked closely with him. The voice of the game is coherent because one person was at the helm of most of the writing. This is the opposite approach from AAA studios (where dialogue is often divided across many writers) and it is worth thinking about.

The Meta-Narrative Loop

The deepest layer of Hades's design is the way narrative and gameplay create a single loop that is larger than either.

Early runs: Zagreus is defiant and inexperienced. He dies fast. Hades is angry. The House is chilly. Dialogue reflects this.

Mid runs: Zagreus is competent. He reaches further. Hades softens slightly. The House NPCs warm to him. He starts doing small favors for everyone.

Late runs: Zagreus routinely escapes the Underworld. The narrative reveals that his escapes are actually achieving a purpose — resolving old family wounds, bringing his mother back, reconciling his father. The mechanical act of repeating runs is what drives the story forward.

Past the "ending": The game continues. You keep doing runs. More relationships develop. A true ending unlocks after many more hours. The replayability of the roguelike becomes narrative replayability.

This is the integration. The roguelike loop is not a gameplay skeleton that the narrative is draped over. The roguelike loop IS the narrative. Zagreus's repeated attempts to escape are literally the story. Every run is a beat. Every death is a chapter break. Every return is a development.

🚪 Threshold Concept: What Hades demonstrates is that if you are bold enough to integrate rather than layer, your narrative and your systems can become the same thing. This is the deepest form of narrative design — where mechanics ARE story. You have seen this concept before (in the Part V introduction, in Celeste, Dark Souls, Breath of the Wild). Hades is its apotheosis in the roguelike genre. When you design your game, ask: is my narrative laid on top of my systems, or do my systems produce my narrative? The latter is harder, but the payoff is a game only you could have made.

Lessons for Your Game

Even if you are not making a roguelike, the design principles apply.

Short conversations beat long ones in systems-heavy games. Hades's 2-4-line exchanges fit around the combat without overwhelming it. If your game has significant non-narrative systems, keep individual dialogues short. Players will consume many short conversations but few long ones.

Tie narrative progression to gameplay actions. Hades gates new dialogue behind runs. Your game can gate new dialogue behind any recurring player action — combat encounters, explorations, item collections. Make the gameplay loop also a narrative loop.

Persistent narrative, resettable mechanics. This separation is powerful. Your run/round/match can be short-term and resettable. Your character arcs, world state, and relationships can be persistent. Players will love the combination.

Invest heavily in voice — verbal and casting. Hades would not work without Kasavin's writing or Korb's voice direction. Your equivalent might be textual voice craft. But do not skimp.

Make your relationship system generous. Hades lets you pursue many characters, in many configurations. Restrictive romance systems ("choose one, lose the rest") are a tradition, not a requirement. Consider giving the player more room.

Small details, many NPCs, tight coherence. Hades's cast is large but deeply coherent — everyone fits in the world, everyone has a relationship to every other character, everyone sounds like themselves. Size is fine if coherence is high.

The Postmortem

Supergiant published a series of postmortems on Hades's development, available through GDC Vault and YouTube. Core themes:

• The game was in Early Access for two years, with regular updates based on player feedback — narrative and mechanical.
• The team recognized early that the narrative system was a central competitive advantage and invested in it accordingly.
• Greg Kasavin's writing workflow was heavily collaborative with designers — narrative scope was adjusted based on what mechanics demanded.
• The team cut substantial content rather than shipping weak material, even in late development.

🎮 Play This: Do not just play Hades. Play it twice. The first playthrough should be organic — escape when you can, talk to people when you want. The second should be deliberate: take careful notes on who says what, when, based on what triggers. You will see the dialogue system working underneath every interaction. It will teach you more than this case study can.

Hades II (in Early Access as of this writing) extends the same design philosophy with a different cast. If you have finished Hades, Hades II is your homework.

Supergiant's achievement with Hades is a gift to every designer working on procedural or systems-heavy games. The integration pattern — narrative as the through-line of repetition — is one of the most important narrative-design innovations of the past decade. Study it. Learn from it. Let it change what you think is possible.