NEStalgia

← All episodes

Cover art for Advanced Dungeons and Dragons: Heroes of the Lance

421 · Advanced Dungeons and Dragons: Heroes of the Lance

March 27, 2026 · 56 min · transcript available

Support NEStalgia directly by becoming a member of our Patreon at https://www.patreon.com/Nestalgia  Members at the $5 and above level get access to our brand new show NEStalgia Bytes. A look at the famicom games you can play without any Japanese knowledge! For More NEStalgia, visit www.NEStalgiacast.com

  • Vanquish the ancient black dragon Khisanth (Kye-santh) or you are doomed to failure!
  • 0) Cold Open (30 to 60 seconds)
  • Hook: “This is an AD&D game on NES where the most important move is… switching characters.”
    • Context for listeners: Most people expect turn-based rules or a deep RPG. This game is an action dungeon crawl that uses the party as its system.
  • Thesis: Heroes of the Lance is ambitious, messy, and fascinating because it tries to turn a famous D&D story party into a side-scrolling survival game.
    • Why you say this up front: It frames the whole episode so every later detail feels like proof, not random trivia.
  • Follow-up questions
  • If you saw “Advanced Dungeons and Dragons” on a NES shelf, what genre would you assume before you ever pressed Start?
  • Is “ambitious but messy” your favorite kind of retro episode, or your nightmare?
  • 1) General Overview (what it is, why it is unique)
  • 1A) The simple pitch (one sentence)
  • A party-based side-scrolling dungeon crawl set in Dragonlance, where you guide eight heroes through a ruined city to retrieve a sacred relic and beat a dragon.
    • Context: This gives listeners a mental box. Everything else is detail inside that box.
  • 1B) The three things that make it unique
  • You do not create characters. You control a famous cast.
    • Context: This is Dragonlance’s big identity. You are playing “the Companions,” not “your guy.”
  • The game’s RPG decisions are not leveling and gear. They are formation and swapping.
    • Context: The “RPG brain” of this game is: who is in front, who is safe, who can solve the current problem.
  • The dungeon is basically the whole game.
    • Context: This is not “world map, towns, quests.” It is one place, explored room-by-room.
  • Follow-up questions
  • Does a fixed cast feel more like you are inside a novel, or more like you lost the best part of D&D, making your own hero?
  • When a game is “one giant dungeon,” does that sound focused and cool, or repetitive and exhausting?
  • 2) Core Concepts Primer (teach the listener the nouns before using them)
  • This section is intentionally short and friendly. You are making sure everyone is on the same page.
  • 2A) What is Dragonlance, in plain terms
  • Dragonlance is a D&D setting that leans hard into story and an ensemble of heroes.
    • Context: Think of it as “D&D as an ongoing fantasy saga,” not a random adventuring sandbox.
  • 2B) What is Xak Tsaroth
  • Xak Tsaroth is a ruined, half-sunken city that functions as the dungeon.
    • Context: When you say “Xak Tsaroth” later, it simply means “the giant dungeon place we are exploring.”
  • 2C) What are the Disks of Mishakal
  • The Disks are the sacred relic you are trying to recover.
    • Context: This is the plot engine. You go down, grab them, escape.
  • 2D) Who is Khisanth
  • Khisanth is the black dragon guarding the relic and your end goal fight.
    • Context: This is the boss you are building toward.
  • Follow-up questions
  • Does that premise feel like classic fantasy comfort food, or does it already feel too “lore heavy” for an NES action game?
  • Would you rather the game explain this inside play, or is reading the manual part of the period charm?
  • 3) Recap of the Franchise (up to release, but framed for why this game exists)
  • 3A) D&D games in this era were genre roulette
  • In the late 80s and early 90s, “AD&D” on the box did not guarantee a specific gameplay style.
    • Context: Some were deep computer RPGs, some were action experiments. This is one of the experiments.
  • 3B) Why Dragonlance was an attractive license
  • Dragonlance comes with a built-in cast and set-piece story beats.
    • Context: That makes it easy to adapt into a game where you control named heroes without needing character creation.
  • 3C) Why the NES version feels a little odd historically
  • The NES port arrives after the concept already existed elsewhere, so it can feel like an older design landing late on the system.
    • Context: This helps explain why it may feel out of step next to smoother later-era NES action games.
  • Follow-up questions
  • Do you judge this as “an NES game,” or as “a port of an older design that happened to land on NES”?
  • Is the Dragonlance name helping the game, or setting expectations it cannot meet?
  • 4) Story and Objective (now that listeners know the nouns)
  • 4A) The story, told like a campfire summary
  • A party of heroes descends into a ruined city to recover a sacred relic tied to the return of divine power.
    • Context: Even if you do not know the setting, it is basically “quest for holy artifact.”
  • A black dragon stands between them and the relic.
    • Context: Classic dungeon structure. Everything funnels toward the dragon.
  • 4B) The objective, stated as “what you are trying to do in play”
  • Explore deeper, survive long enough, keep the party functional, reach the dragon, claim the relic.
    • Context: This is the gameplay version of the plot.
  • Follow-up questions
  • Does the game feel like it is telling this story as you play, or does it feel like the story is something you bring with you?
  • In a game like this, do you care more about narrative clarity or mechanical clarity?
  • 5) Core Gameplay Loop (simple, then “what that really means”)
  • 5A) The simple loop
  • Enter rooms, move through hazards, fight monsters, choose the right hero for the situation, repeat deeper into the dungeon.
    • Context: Keep it high-level first so listeners can follow.
  • 5B) What makes that loop different from a normal action game
  • You are not just controlling one character. You are managing a party’s health and roles in real time.
    • Context: The loop includes logistics. That is the identity.
  • The game asks you to pause and make decisions through menus.
    • Context: This is where some players feel “strategy,” and others feel “friction.”
  • Follow-up questions
  • Does pausing to manage the party make you feel like a commander, or does it break the flow?
  • When you swap heroes, do you feel smart, or do you feel like the game made you do it?
  • 6) Gameplay Elements (only the notable, game-specific stuff, introduced in a teachable order)
  • 6A) Party formation and the “front row” concept
  • Not everyone is equally safe. Who is in front matters.
    • Context: Think of the party like a moving formation. You can rotate who takes the punishment.
  • This creates a mini-game of triage.
    • Context: You are constantly deciding whether to protect fragile utility characters or expose them to use their abilities.
  • Follow-up questions
  • Did you naturally learn to rotate the front line, or did the game punish you into learning it?
  • Is “escort eight people through a dungeon” a cool idea, or inherently frustrating?
  • 6B) Swapping heroes is the real “combat system”
  • Instead of deep movesets, the depth is “who should be leading right now.”
    • Context: The correct answer changes room to room: melee safety, ranged control, magic utility, healing.
  • This is why the game feels tactical even when the action is simple.
    • Context: The tactics live in selection, not execution.
  • Follow-up questions
  • Which situations made you swap most often: flying enemies, cramped corridors, boss moments, or pure desperation?
  • Would fewer characters with deeper mechanics have been better, or would that ruin the “party” premise?
  • 6C) Resources are limited, and that changes your personality as a player
  • Magic and special tools feel scarce, so you start thinking in terms of conservation.
    • Context: The game quietly trains you to hoard, then tests you to spend.
  • That tension is a big part of the difficulty reputation.
    • Context: You can lose because you spent too much early or because you refused to spend at all.
  • Follow-up questions
  • Are you a hoarder or a spender in retro games, and did this game punish your default style?
  • Did the game ever communicate “this is the moment to use the good stuff,” or did you guess?
  • 6D) Navigation and hazards are not side issues, they are the main conflict
  • Pits and awkward rooms can be deadlier than enemies.
    • Context: This is a dungeon survival game wearing action clothes.
  • The dungeon layout becomes something you learn like a language.
    • Context: Once you understand how it connects, it feels less like chaos and more like a place.
  • Follow-up questions
  • Did you ever hit the point where the dungeon felt legible, or did it stay confusing?
  • What is the game’s real villain: monsters, geometry, or the interface?
  • 6E) The “story artifact as victory condition” moment
  • The Blue Crystal Staff is not just lore. It is central to the ending.
    • Context: This is the most Dragonlance-flavored design choice in the whole game: the holy object matters mechanically.
  • Follow-up questions
  • Do you like when a story item becomes a hard mechanical requirement?
  • Is it satisfying because it is faithful, or annoying because it narrows your options?
  • 7) Extra Layer 1: Companion Mechanics (introduced as “roles,” not a character dump)
  • Instead of listing eight bios, frame it as “how the game wants you to think about your party.”
  • 7A) The party as four functional buckets
  • Frontline anchors: characters you trust to lead through danger
    • Context: These are your “I do not want to die to random hits” picks.
  • Ranged stabilizers: characters who keep fights safer by controlling distance
    • Context: On NES, range often equals safety, especially in cramped rooms.
  • Utility casters: characters who solve problems rather than trade hits
    • Context: Their value is not raw damage. It is the right tool at the right time.
  • The linchpin: the character tied to the game’s most important story mechanic
    • Context: This is the “if this goes wrong, the endgame gets weird” character.
  • 7B) Quick “why you swap to them” spotlights (one line each, in listener-friendly terms)
  • Use this as a rapid segment, almost like a sports roster.
  • Goldmoon: your healer and story key. When things fall apart, she is how you get another chance.
  • Raistlin: your problem-solver. When brute force stops working, he is the pivot.
  • Caramon / Sturm types: your “walk into danger” leaders. They keep the party alive by being reliable.
  • Tanis / Riverwind types: your “safe damage” switch. They smooth out messy rooms.
  • Flint: the practical brawler with a bit of ranged flexibility.
  • Tasslehoff: the weird utility pick, the one you use when you want coverage at multiple distances.
  • Follow-up questions
  • Did you end up playing this as “a party game,” or did you basically main one or two characters and treat the rest as extra lives?
  • Which Companion felt surprisingly useful, and which felt like dead weight?
  • 8) Extra Layer 2: Xak Tsaroth Beat Map (how the dungeon “story” escalates)
  • This is a pacing tool for your episode, so you can describe progression without doing a walkthrough.
  • 8A) Beat 1: Orientation (learning the game’s language)
  • Early Xak Tsaroth is about comprehension, not mastery.
    • Context: You are learning what matters: exits, hazards, swapping, formation.
  • Follow-up questions
  • At what point did you realize this was not a normal action game?
  • 8B) Beat 2: Attrition (the game’s real difficulty shows up)
  • Midgame is where resource drain and navigation mistakes compound.
    • Context: This is where the “party management” idea becomes stressful rather than cool.
  • Follow-up questions
  • Does the midgame feel like fair pressure, or like it snowballs in a way that feels doomed?
  • 8C) Beat 3: Requirement (the game reveals what it truly cares about)
  • Late game is where the story artifact becomes the mechanical centerpiece.
    • Context: This is the “Dragonlance module” moment. The plot object is the solution.
  • Follow-up questions
  • Does the ending feel like payoff, or like a rule check you were not properly prepared for?
  • 9) Sequels and Spinoffs (quick list, each with a clean hook)
  • Frame this as “Dragonlance is a setting, not a genre.”
  • Dragons of Flame: more of the Silver Box approach, continuing the storyline with similar DNA.
  • Shadow Sorcerer: still in that lineage, but it shifts the feel and priorities.
  • War of the Lance: the zoomed-out war strategy take, for people who want the setting’s conflict at scale.
  • DragonStrike (NES): dragon-riding action fantasy, closer to the box-art promise some people expected from Heroes.
  • Champions of Krynn (Gold Box): the rules-driven party CRPG version, for those who want “AD&D as a campaign.”
  • Follow-up questions
  • After playing this, what would you want next: more action weirdness, or the “real RPG” version?
  • If NEStalgia covered only one other Dragonlance game, which genre would make the best contrast episode?
← Best of 1990Fun House →