Final Fantasy VII (1997): The RPG That Made a Generation Care

Final Fantasy VII arrived in Japan in January 1997 and in North America that September, Squaresoft’s first mainline entry on Sony’s PlayStation after four games built for Nintendo’s cartridge hardware, and its jump to CD-ROM changed what the series could afford to attempt: full-motion CGI cutscenes, an orchestral score too large for a cartridge, and a story willing to spend its opening hours as an eco-terrorist thriller before pivoting into cosmic horror. I was in my early twenties when it landed in the West, arcade and PC games having mostly been my territory until then, and FFVII is the game that made turn-based JRPGs feel like something worth an outsider’s attention rather than a niche import scene.

Materia: a class system built out of sockets, not levels

Every piece of equipment in FFVII has a fixed number of Materia slots, and Materia orbs — self-contained spheres granting spells, summons, or passive abilities — can be swapped freely between any character at any time. This decouples party role from fixed class in a way most contemporary RPGs didn’t attempt: any character can learn any spell simply by equipping the right orb and using it enough to level it up, meaning Cloud can be built as a black mage, Barret can carry White Materia and function as your primary healer, and the “correct” party composition is whatever combination of linked Materia pairs (a Support orb linked to an Attack orb triggering an additional effect on hit) the player has assembled rather than a role fixed at character creation. It’s a genuinely deep customisation system for 1997, flexible enough that two players’ playthroughs can produce meaningfully different parties from the same eight-character roster, and it’s the mechanical reason FFVII rewards a second playthrough rather than just a nostalgic return visit.

The Active Time Battle system’s tension

FFVII’s combat runs on the ATB system Square had been refining since Final Fantasy IV: each character has an individual gauge filling in real time, and choosing an action only becomes available once that gauge is full, meaning the fight keeps moving even while you’re deciding what to do. This produces a specific kind of pressure a fully turn-based system doesn’t: waiting too long to decide costs a turn to an enemy’s own filling gauge, and managing three characters’ independent timers while planning ahead for Limit Breaks (powerful special attacks that charge as characters take damage) turns even a straightforward random encounter into a small planning exercise under a visible clock. It’s neither fully real-time nor fully turn-based, and that hybrid position is exactly what let Square keep the strategic depth of a turn-based system while adding enough urgency that combat never felt as passive as its Nintendo-era predecessors.

Pre-rendered backgrounds solving a hardware problem into an aesthetic

The PlayStation’s polygon budget in 1997 couldn’t render detailed, fully 3D environments at a resolution or frame rate that looked good, so Square rendered static, pre-drawn background art for every location and composited low-polygon character models on top, with camera angles fixed per screen rather than freely rotating. This was a workaround for hardware limitations that became one of the game’s defining visual signatures — Midgar’s industrial sprawl, the Gold Saucer’s neon excess, Cosmo Canyon’s painted vistas all carry a level of artistic detail the polygon budget alone could never have afforded, at the cost of camera freedom later 3D RPGs would take for granted. It’s a trade every subsequent PlayStation-era Square RPG would keep making until hardware finally caught up, and it’s part of why FFVII’s world still reads as visually distinct decades on, blocky character models included.

Midgar as an opening act with something to say

The game’s first several hours, set entirely within Midgar’s plate-stratified industrial city, follow Cloud and the eco-terrorist group AVALANCHE bombing Mako reactors that are draining the planet’s life force for energy — an opening explicitly coded around resource extraction, corporate exploitation, and the human cost of an energy economy built on visibly diminishing a planet’s health. This grounded, politically legible opening act makes the story’s later swerve into ancient alien history and god-tier magic land harder than it would if the game had opened at that scale from the start; Midgar’s slums under the plate, its class stratification made physically literal in the city’s own architecture, give the eventual cosmic stakes a human floor to return to whenever the plot threatens to float away entirely.

What the Remake project reveals about the original by contrast

Final Fantasy VII Remake rebuilds just the Midgar section into a full standalone game with real-time action combat, and Final Fantasy VII Rebirth continues the story across the original’s overworld — the sheer scale of content Square is now willing to build from material the 1997 original compressed into a fraction of its runtime says something honest about how much world-building the original game implied rather than fully rendered. Playing the 1997 original after either Remake instalment reframes it less as a lesser, dated version of the same story and more as a different kind of artefact entirely: a game that trusted low-fidelity presentation and a reader’s imagination to fill gaps that a modern budget would rather render explicitly.

Summons and Limit Breaks as escalation, not just spectacle

FFVII’s Summon Materia — Knights of the Round, Bahamut, Ifrit and dozens more — each trigger an extended CGI set-piece before dealing damage, and while the animations became a genuine selling point of the era, the mechanical role summons play is more interesting than the spectacle alone: a summon consumes a full turn and significant MP for a large, guaranteed payoff, which turns the decision to summon into a real resource-allocation choice against simply attacking or casting a cheaper spell repeatedly. Limit Breaks work from the opposite direction, building automatically as a character takes damage rather than costing a resource, which means a fight going badly for the player simultaneously builds toward their most powerful tools — a feedback loop that keeps close, difficult fights tense rather than simply punishing, since the same damage draining your HP is filling the gauge that might turn the fight around.

The Gold Saucer and Square’s early sandbox instinct

The Gold Saucer, an amusement park built on a platform above the desert, houses an entire suite of minigames — chocobo racing, a Battle Square arena, a snowboarding sequence, a basketball minigame — most of which have no bearing on the main plot and exist purely as a break from the central story’s escalating stakes. Chocobo breeding, in particular, is a genuinely deep side-system in its own right: capturing and breeding chocobos through a multi-generational genetics-adjacent system unlocks late-game traversal options (chocobos capable of crossing water, mountains, or even the entire map) that meaningfully open up areas otherwise inaccessible. It’s an early example of a JRPG treating its side content as a genuine parallel game rather than filler, a design instinct Square would carry forward into plenty of its later catalogue.

Vagrant Story and the same studio’s other 1997-adjacent ambition

FFVII wasn’t Square’s only systems-heavy swing in this era. Vagrant Story, released a few years later from a different internal team, took the opposite approach to accessibility — dense, spreadsheet-deep combat math wrapped in a much smaller, more atmospheric package — and the contrast between the two says something real about Square’s output during this period: a studio confident enough in its RPG systems expertise to simultaneously chase mainstream accessibility with FFVII’s Materia and niche mechanical density with Vagrant Story’s weapon-condition math, rather than converging on one house style across its whole catalogue.

Spoilers below

Aerith’s death at the hands of Sephiroth in the Forgotten City, roughly two-thirds through the game, remains one of the most-discussed character deaths in the medium — delivered without a warning prompt, without a save-scum-friendly checkpoint immediately before it, and without the game offering any mechanism to prevent it regardless of player skill. It works because the preceding hours had built Aerith as more than a party utility slot: her Ancient (Cetra) heritage, her connection to the Lifestream, and her growing romantic tension with Cloud all made her death a genuine narrative rupture rather than a stat loss. The larger reveal underpinning the plot — that Sephiroth’s madness stems from Jenova, an alien entity mistaken by Shinra’s scientists for a Cetra specimen, whose cells were implanted into him and Cloud alike during Shinra’s Project S experiments — recontextualises Cloud’s own fractured memory: the heroic SOLDIER backstory Cloud believes about himself turns out to be a false memory adopted from his friend Zack Fair, who actually lived the events Cloud has been misremembering as his own. The ending’s Lifestream sequence, in which the planet’s collective consciousness intervenes against Sephiroth’s Meteor spell, is left visually and narratively ambiguous enough that decades of debate over whether humanity actually survives the epilogue’s final scene have never fully settled — an ambiguity the Remake trilogy has so far chosen to preserve rather than resolve.

The West’s introduction to a genre it had mostly ignored

Turn-based JRPGs had a real but niche following in North America and Europe before FFVII — earlier Final Fantasy entries and contemporaries had sold respectably without breaking into mainstream conversation. FFVII’s marketing budget, reportedly among the largest Sony had committed to any third-party title at that point in the PlayStation’s life, put the game in front of an audience that had never seriously considered a turn-based RPG worth the time a 30-plus-hour campaign demanded. The CGI opening cutscene, showing Aerith walking through Midgar’s neon-lit streets before pulling back to reveal Cloud’s arrival by train, was often the first thing curious buyers saw in a shop demo kiosk, and it did more to sell the genre’s potential to a Western audience unfamiliar with it than any specific mechanical pitch could have managed on its own.

The verdict

Judged purely as a product of its moment, FFVII’s presentation has aged the way all pre-rendered, fixed-camera 3D from this era eventually does — blocky, low-polygon character models standing awkwardly inside gorgeously painted backgrounds, a mismatch some players find charming and others find genuinely jarring on a modern screen. Judged as a systems design, it holds up far better: Materia’s socket-based flexibility still reads as a genuinely clever solution to the class-rigidity problem most contemporary RPGs hadn’t solved, and the ATB system’s ticking pressure remains a smarter compromise between real-time urgency and turn-based planning than plenty of RPGs manage even now. FFVII made a generation care because the systems (Materia’s flexibility, ATB’s ticking pressure) and the presentation (CGI ambition married to a story willing to open on class warfare before going cosmic) arrived at exactly the moment a new disc-based hardware generation made both possible for the first time, and it’s still the clearest evidence that a JRPG’s reputation can rest as much on what its systems let you build as on what its story tells you happened.