gamesbriefs
9:35in productionCh. 1 · The Quest Begins/ 9:35 · ceiling 15 min
RPG · Retro

Dragon Quest (video game)

Chunsoft · 1986

Dragon Quest doesn’t invent the RPG—it translates it into something a child could pick up and understand without a manual.

Dragon Quest (1986) is a single-player RPG developed by Chunsoft. It simplifies Western RPG conventions for console audiences. The player controls a young hero who must defeat the Dragonlord and retrieve the stolen Balls of Light. Progression relies on open exploration gated by enemy strength, turn-based combat with four commands, and stat growth tied to experience and name input. Save systems differ: passwords in Japan, battery-backed RAM in North America. Its design prioritises narrative clarity and incremental empowerment over mechanical complexity.

RPGRetroAbstractionAdolescenceHardwareAbstraction across the network →
Chapters & takeaways4
  1. 1:10
    The Quest Begins

    The game starts with a royal mandate: defeat the Dragonlord and recover the Balls of Light.

  2. 2:34
    How You Return

    Save systems split along regional lines—passwords in Japan, battery-backed RAM in North America.

  3. 3:58
    Name Is Stat

    Your hero’s name isn’t cosmetic—it determines starting stats and growth curves.

  4. 5:24
    Strength Through Scenarios

    Progress isn’t linear—it’s built through smaller, repeatable scenarios that raise your level and confidence.

Worth your time?

Yes. Play the whole thing.

3.5/ 5
What works
  • Its narrative-driven progression gives a clear objective from the start: defeat the Dragonlord and retrieve the stolen Balls of Light.
  • Smaller scenarios build strength incrementally.
  • Open-world exploration is gated intelligently—not by walls, but by escalating monster difficulty.
  • The name-to-stats mechanic adds personalisation without complexity.
What does not
  • It does not scale well to modern expectations of feedback, pacing, or clarity.
  • There is no map. No quest log. No visual distinction between safe and dangerous zones.
  • No explanation of stat growth beyond the name-input mechanic. No tutorial.
  • The password system breaks continuity. The combat lacks tactical depth beyond command selection and HP management.
Play it if
  • It is for players curious about RPG origins, willing to sit with abstraction and repetition.
  • It is for those who value worldbuilding through implication—town names, item descriptions, and enemy placements that suggest a larger world.
  • It is not for players who need constant feedback, visual variety, or mechanical novelty.
Skip it if
  • It is not for players who expect narrative payoff before the final act—or who dislike parsing cryptic NPC dialogue for progress.
The written brief2 min read

What the game is

A single-player role-playing game developed by Chunsoft in 1986. It is a foundational console RPG designed to introduce Japanese and North American audiences to the genre. It streamlines Western PC RPG conventions—no dice, no rulebooks, no party management—into a self-contained, hardware-constrained experience for the Famicom and NES.

How it actually plays

The player begins in King Lorik’s chamber in Tantegel Castle. A menu offers new quest, continue quest, or message speed adjustment. Continuing in Japan requires a password. The North American NES version saves to battery-backed RAM with delete or duplicate options. The hero’s name sets initial stats and growth. Combat is turn-based and first-person, with four commands: fight, run, spell, item. Exploration is open but gated by monster strength. Towns supply information, gear, and consumables. Inventory is limited. Dark areas require torches or light spells. Progression hinges on gathering intel, grinding experience, and upgrading gear.

What works

Its narrative-driven progression gives a clear objective from the start: defeat the Dragonlord and retrieve the stolen Balls of Light. Smaller scenarios build strength incrementally. Open-world exploration is gated intelligently—not by walls, but by escalating monster difficulty. The name-to-stats mechanic adds personalisation without complexity. The save system adapts regionally: passwords in Japan, battery-backed RAM in North America. Light sources create meaningful environmental stakes.

What does not

It does not scale well to modern expectations of feedback, pacing, or clarity. There is no map. No quest log. No visual distinction between safe and dangerous zones. No explanation of stat growth beyond the name-input mechanic. No tutorial. No mid-game guidance beyond townspeople’s fragmented hints. The password system breaks continuity. The combat lacks tactical depth beyond command selection and HP management.

Who it is for, and who it is not

It is for players curious about RPG origins, willing to sit with abstraction and repetition. It is for those who value worldbuilding through implication—town names, item descriptions, and enemy placements that suggest a larger world. It is not for players who need constant feedback, visual variety, or mechanical novelty. It is not for those who expect narrative payoff before the final act—or who dislike parsing cryptic NPC dialogue for progress.

Is it worth your time

Yes—if you want to feel how RPGs were made legible to console players for the first time. It asks for patience with slow pacing, repetition, and abstraction. It does not ask for reflexes, coordination, or multitasking. It rewards attention to dialogue, pattern recognition in enemy placement, and deliberate resource management. It is worth your time only if you accept its constraints as design choices, not flaws.

Same strand · RPG4 of 86
11:39
Borderlands (video game)Gearbox Software · 2009Borderlands (2009) is a role-playing shooter developed by Gearbox Software. It combines first-person shooter action with RPG systems—including four distinct Vault Hunters, branching skill trees, mission-driven progression, and a procedural loot engine generating over 15 million weapon and gear variations. Its cell-shaded-like art style gives Pandora a comic-book appearance. Players fight hostile wildlife and human forces on the fictional planet while seeking a fabled Vault.
8:27
Destiny (video game)Bungie · 2014Destiny is a server-dependent first-person shooter that structures player time around repeated group activities — strikes, raids, patrols, and PvP matches — all governed by Light-level gating and tied to Bungie.net infrastructure. Its strength lies in rhythmic, communal combat execution. Its weakness is systemic opacity and narrative detachment. It asks for consistency, not curiosity.
9:36
Diablo (video game)Blizzard · 1996Diablo (1996) is an action role-playing dungeon crawler developed by Blizzard North and published by Blizzard Entertainment for Windows. Players navigate procedurally generated levels using mouse-driven movement and keyboard-based spellcasting. Dungeon themes shape layout—catacombs feature long corridors, caves are non-linear. Quests are randomly assigned from tiers; only the final two are mandatory. Items degrade with use and are destroyed at zero durability. Griswold the Blacksmith repairs them for a fee; Warriors may self-repair at durability cost. Staves enable spellcasting without spell knowledge or mana. The game establishes a tight, friction-driven loop: explore, degrade, return, repeat—until the final two quests gate the end.
9:16
EarthBoundNintendo · 1994EarthBound is a 1994 Nintendo RPG that rejects the genre’s conventions: no overworld map, no random encounters, no top-down grid. Instead, it builds a seamless, oblique-projection world where enemies are visible NPCs, combat begins with spatial positioning, and progression is deliberately unstable. It asks players to read the environment, not the menu.
Up next in Games

Ecco the Dolphin (video game)

Sega · 1992 · 9:26

A dolphin doesn’t jump — it breaches. And Ecco makes you feel every tonne of water you displace.

Play nextBack to RPG
9:26