How A Forgotten Design Pitch Revealed Final Fantasy’s Roots

When game creators tidy their archives, they sometimes uncover more than just old paperwork. In late 2025, Final Fantasy creator Hironobu Sakaguchi shared something remarkable from his personal files: hand-drawn design plans from 1984, outlining his first game concept for Square on graph paper. The find is more than nostalgic ephemera; it offers a rare glimpse into how early Japanese PC adventures were envisioned and how many of the ideas that later powered Final Fantasy were already present in embryo.

Inspired by reporting from GamesRadar+ on Sakaguchi’s discovery, this article explores what those documents represent, how they connect to Square’s first published title, and why a handful of English text commands scribbled on graph paper still matter to game design in 2026.

The Rediscovered Pitch: A Snapshot of 1984 Game Design

Sakaguchi’s unearthed documents are essentially a complete pitch for an adventure game: story beats, command examples, maps, and doodles all captured by hand. From what can be seen in the images he posted, it’s a meticulous overview of a text-driven adventure with some visual elements, typical of early 1980s home computer titles.

Although the notes are primarily in Japanese, a few English command examples stand out. They describe a parser-based interface where the player types short verb–noun phrases to interact with the world. These commands are tied to specific outcomes that range from the dramatic to the playful, such as using a particular weapon on a dangerous animal or offering an item to a character in exchange for affection.

Fans and Japanese press quickly connected this pitch to The Death Trap, widely documented as both Sakaguchi’s first game and Square’s first commercial release in 1984. Official histories of Square Enix attribute the company’s beginnings on Japanese PCs in the early 1980s, before it transitioned to Famicom development and eventually created Final Fantasy in 1987.¹

What Makes the Document So Unusual?

• Graph paper layout: Rooms and scenes are mapped as grids, showing precise movement options and puzzle pathways.
• Mixed-language commands: While most notes are Japanese, some in-game commands appear in English, hinting at early international aspirations or stylistic flair.
• Flowchart-style design: The design doesn’t just list locations; it shows conditional outcomes and branching paths, signaling an early narrative design mindset.

For modern players used to engines and visual scripting tools, it’s a reminder that many early games were designed as literal diagrams, with every state change and possible command spelled out on paper before a single line of code was written.

Square’s First Steps: From PC Adventure to RPG Giant

The context for these notes is as important as the content. In 1984, Square was still a fledgling outfit focused on Japan’s domestic computer market. The company’s official history notes that the original Square Co., Ltd. was founded in the early 1980s as a subsidiary of a power line construction firm before spinning off as its own entity, with small experimental projects on NEC and other Japanese PCs paving the way for later console work.¹

Within that setting, an ambitious, story-focused adventure game was a logical bet. Western PCs had already seen landmark parser-based adventures from Sierra On-Line and Infocom, and Japanese developers were beginning to adopt and adapt the format. The rediscovered Sakaguchi pitch fits squarely into this trend: it’s a text adventure enhanced by diagrams and visuals, built to run on limited hardware but aiming for cinematic effect.

The Death Trap Connection

While Sakaguchi’s rediscovered pages don’t explicitly brand themselves with a title, they match what is known publicly about The Death Trap:

• Released in 1984 on Japanese PCs.
• Designed and directed by Hironobu Sakaguchi at Square.
• Structured as an adventure with menu or text-based input and illustrated scenes.

Japanese outlet Automaton and other observers highlighted these similarities, suggesting the rediscovered notes are essentially the original design proposal that set Square’s development pipeline in motion. If so, the graph paper isn’t just a curiosity—it’s a blueprint for the company’s first shipped game and, by extension, for its transition to the role-playing genre a few years later.

Text Parsers, Apples, and Lions: How Commands Defined Early Adventures

The most eye-catching details in Sakaguchi’s documents are the explicit command examples. 1980s adventure games often used “verb + object” structures that the parser had to recognize exactly. Something like OPEN DOOR or TAKE KEY wasn’t just a suggestion; it was a literal string match the game engine looked for in a list of allowed inputs.

In the rediscovered pitch, you can see this in how the designer writes out both the input and the expected result. Examples include:

• A benevolent action: giving a specific item to another character to trigger a positive scripted response.
• A violent action: using a particular weapon on a dangerous creature to advance the narrative.

Commands like these were common across the era’s text adventures, which rewarded players for experimenting with different verbs and nouns until the parser accepted something. Academic overviews of early digital games point out that this design model pushed players toward imaginative problem-solving but also created friction when the parser’s vocabulary was limited or opaque.²

Typical Command Types in Early Text Adventures

What’s striking in Sakaguchi’s notes is how carefully each of these interactions is mapped to a story outcome, reinforcing the idea that narrative consequence—not just mechanical puzzle-solving—was central to the design.

Hand-Drawn Maps and Flowcharts: Visualizing a Game Before Code

Beyond commands and descriptions, the newly surfaced pages are packed with diagrams. Rooms are boxes; doors are arrows; puzzles are annotated with conditions and notes. In some sections, the design shifts into full flowcharts, showing different paths depending on the player’s choices.

Why Graph Paper Mattered

Early game design relied heavily on physical media. Even in contemporary game design education, students are often encouraged to sketch systems on paper to focus on core logic before implementation. This tradition dates back to the 1970s and 80s, when designers had little choice but to plan on paper.² In Sakaguchi’s case, the rediscovered graphs illustrate several key practices:

• Spatial design: Mapping out rooms and connections ensured the adventure felt coherent, with a balance of exploration, combat, and puzzle spaces.
• Puzzle gating: Specific doors or sequences are clearly linked to items or commands, an early form of progression gating that RPGs still use.
• Failure and branching paths: Some routes end abruptly or loop back, signaling game-over states or alternate routes.

Flowcharts remain a staple in modern game development for designing quest logic, AI behavior trees, and narrative branches. The designs in the 1984 pitch are a direct ancestor of the visual scripting frameworks now standard in major engines like Unreal and Unity.

From Death Traps to Crystals: How These Ideas Echo in Final Fantasy

Although the rediscovered adventure predates Final Fantasy by several years, many of its core ideas can be traced forward into Sakaguchi’s later work. When the first Final Fantasy launched on the Famicom in 1987, it combined turn-based battles with exploration, but it also emphasized story, cinematic moments, and a strong sense of place—traits that Square has highlighted in its own historical retrospectives.¹

Design Threads That Carry Over

• Emphasis on story: Even as a text adventure, the 1984 design treats narrative beats as the main reward. The same philosophy drove the cinematic cutscenes and plot twists in early Final Fantasy titles.
• Scripted set pieces: Specific commands triggering dramatic events anticipate the later use of heavily scripted boss fights and narrative sequences.
• Clear spatial maps: Towns, dungeons, and overworld maps in Final Fantasy follow a similar logic to the graph-paper levels in the adventure concept.
• Character-driven interactions: Trading items, talking to NPCs, and making small choices that affect the story’s flavor all have roots in parser-based design.

By the early 1990s, Square had become known worldwide for blending RPG systems with cinematic storytelling, especially with releases like Final Fantasy IV and Final Fantasy VI. The rediscovered pitch underscores how this approach didn’t emerge suddenly in the late 80s—it was already taking shape in small PC projects years earlier.

Why Found Documents Matter to Game History

From a historical standpoint, Sakaguchi’s graph paper is a primary source: design documentation that captures thought processes before later revisions, localizations, and remakes. Game historians and preservationists argue that such materials are crucial for understanding how interactive media evolved, especially since many early commercial games have incomplete source code or lost assets.²

What We Learn from a Single Pitch

• Studio culture: The documents show how a young Square approached planning—detailed, diagram-driven, and heavily scripted.
• Technology constraints: The reliance on text commands and still images reflects the realities of 1980s PCs, where memory and CPU time were limited.
• Design priorities: Even under tight constraints, the pitch emphasizes narrative structure and player experience over pure technical showmanship.

These findings align with broader research into early Japanese game development, which notes that many designers in the 1980s drew on both Western adventure games and domestic visual novels, creating hybrid formats that eventually evolved into modern JRPGs.²

Lessons for Modern Developers and Players

For today’s designers, the rediscovered Sakaguchi pitch is more than a curiosity; it’s a practical case study. Stripped of modern tools and engines, it demonstrates how much of game design is still about clearly articulating rules, states, and player options.

Key Takeaways for Designers

• Start on paper: Mapping levels and story beats by hand forces clarity before implementation, reducing rework later.
• Define inputs and outputs: Listing possible actions and their consequences helps ensure that players receive consistent feedback.
• Embrace constraints: Working within strict limits, as 1980s developers did, can encourage creative problem-solving and tighter design.
• Document decisions: Flowcharts and notes become invaluable when revisiting a project after months—or decades.

For players, the discovery is a reminder that even the most expansive modern RPGs trace their lineage back to simple commands typed into a blinking prompt. That continuity gives extra resonance to revisiting early Square titles, whether through remasters, retro collections, or fan translations.

FAQ: Sakaguchi’s Rediscovered Game Plans

Was the rediscovered design document definitely for The Death Trap?

The design closely matches what is publicly documented about The Death Trap, Sakaguchi’s first game and Square’s first released title, including its 1984 timing and adventure-game structure. While the graph paper itself doesn’t print the title, Japanese media coverage and fans have connected the dots, making it highly likely that this pitch became the basis for that project.

Why are some of the commands written in English?

Early Japanese PC games often used English words or Roman characters in their interfaces. This was partly a stylistic choice and partly influenced by Western adventure games that Japanese developers were playing and studying. Using short English verbs also conserved space and matched the conventions of parser-based interfaces that favored concise commands.

How does this rediscovery relate to the creation of Final Fantasy?

The 1984 pitch shows that Sakaguchi was already thinking in terms of detailed story flow, precise player actions, and cinematic set pieces. Those same priorities later shaped the design of Final Fantasy on the Famicom, which Square and outside commentators have repeatedly identified as a turning point in the company’s focus on story-driven RPGs.^1,3

Are the original The Death Trap and its sequel officially available today?

As of recent reporting, there have been no widely released official modern ports or remasters of The Death Trap or its follow-up on contemporary platforms. Information about these titles largely comes from historical overviews, fan documentation, and scattered archival copies of their original PC releases.

Why do historians care so much about old design notes and pitches?

Because many early video games were built in small teams and on limited budgets, formal archives were rarely kept. Design notes like Sakaguchi’s provide rare insight into how decisions were made, how genres evolved, and how studios developed their creative identities. Historians treat such materials as primary sources, similar to early drafts or production sketches in other media.²