The War Nobody Remembered

I came to Final Fantasy Tactics for the wrong reasons. Or what turned out to be the smaller reasons. I came because someone told me you could build your party however you wanted — that the job system let you turn a white mage into a knight or a thief into a summoner, that the combinations were essentially limitless, that you could spend hours before a battle ever happened just deciding who your people were going to be. That sounded like the kind of game I wanted. I had no idea what else it was going to give me.

The Freedom of the Grid

The job system in Final Fantasy Tactics is one of the finest mechanical achievements in the history of the genre. Each character can be assigned a primary job — Knight, Archer, White Mage, Black Mage, Monk, Thief, Summoner, Geomancer, and dozens more — and as they gain experience in each class they unlock abilities that can be carried into any other class. A Knight who has trained as a White Mage can heal. A Monk who has mastered Geomancy brings elemental power to every punch. The combinations multiply until the party you are fielding looks nothing like the party anyone else would have built.

This was not incidental to my experience of the game. It was where I lived, in the hours between story missions — testing, refining, rebuilding. Discovering that a particular combination broke something open in a way I hadn't anticipated and then pulling back, adjusting, trying a different angle. The tactical battles themselves were the test of whatever theory I had been developing in the menu screens, and winning felt like proof of an argument I had been making to nobody but myself.

What I didn't notice at first, because I was so absorbed in the mechanics, was that the story was quietly doing something I wasn't prepared for. That it had been doing it since the opening screen. That by the time I looked up from the job menu, I was already inside something much larger than a tactical RPG.

A War About Politics, Then About Something Worse

Final Fantasy Tactics begins as a war story. Two noble houses compete for control of the kingdom of Ivalice, each backing a different claimant to the throne, each pulling mercenaries and knights and political allies into their orbit. You are Ramza Beoulve, son of one of the kingdom's most respected military families, a young man who believes in the order he was born into and expects it to deserve that belief.

It does not deserve it. This becomes clear slowly, then all at once. The noble houses are corrupt. The church is not what it presents itself as. The war everyone is fighting — the one you were told has a righteous side — has no righteous side. It has only people using other people, all the way down. The story that seemed to be about which faction would win reveals itself to be about something more uncomfortable: the systems that powerful institutions build to perpetuate themselves, and what happens to the people who discover the truth underneath them. It is the same argument that Persona 5 Royal would make decades later in a Tokyo high school, and that Neverwinter Nights made through a justice system that worked exactly as designed and reached the wrong conclusion.

The Church of Glabados is the game's real villain — not a general or a duke but an institution centuries old that has been shaping wars and crowning kings and writing history in its own image long before Ramza was born. Fighting it is not a matter of defeating an army. It is a matter of facing something that has convinced the entire world of its own legitimacy. Something that controls not just what people do but what they believe is true.

For a PS1 game in 1997 this was astonishing. Not subtle — Final Fantasy Tactics is not subtle — but genuinely ambitious. It wanted to say something about power and how power sustains itself and what it costs to stand against something that has decided what the truth is. Most games of its era had villains who wanted to destroy the world. This one had a villain that had already won, centuries ago, and was simply maintaining its victory.

Ramza and Delita — The Same Road, Two Directions

Ramza begins the game with his closest friend, Delita Heiral. They are students together, sparring partners, easy with each other in the way people are when they trust someone completely. Delita is common-born in a world that cares enormously about birth. Ramza is noble-born and has never been made to feel the weight of that distinction until events force him to see what it actually means.

Then something happens that separates them. Not a disagreement, not a betrayal between them — something the world does to both of them that breaks them differently. Ramza turns away from the system that failed him, fights against it, tries to repair what he can for people who cannot repair it themselves. Delita turns toward the system, learns its rules, decides to beat it at its own game. It is the same fork that Aribeth faced when the institution she served did something unforgivable — and the same question of which direction a person walks when the thing they believed in proves itself unworthy of belief.

By the end of the game, history records Delita as the hero who ended the war and united the kingdom. Ramza's name was erased from every official record. The truth of what he did — the demon he actually stopped, the manipulation he actually uncovered — was buried so thoroughly that it was considered myth for centuries. A historian discovers the real account much later and is killed for it. What you played through was the version of events that was never supposed to survive.

This is not a subtext. It is the game's explicit argument, delivered in its framing story. And it lands with a force that the straightforward battle between good and evil never could, because it is not about whether the right side won. It is about whether the right side was even legible to the world watching. Whether doing the right thing, in a system designed to erase it, leaves any trace at all.

What the Job System Was Actually Saying

I came to this game for the job system. I spent hours in it, building parties, theorising combinations, finding satisfaction in the freedom it offered. And only later — thinking about it properly, in the way you think about games years after you've played them — did I understand what the job system was doing in relation to the story.

Ramza is, mechanically, defined by his ability to change. His Squire class is the foundation, the starting point, the thing he was before everything else — but it grows in ways the game's other special characters do not. He can become almost anything. He carries abilities from every class he has mastered. He is, by the end of the game, something the job system's categories can't fully contain — a person who has been through too much to fit neatly into any single identity.

And that is precisely who he is in the story. Not a knight or a hero or a noble or a revolutionary. All of those things, at different moments, for different reasons, always returning to something fundamental that none of those titles quite captures. A person who kept choosing the harder thing, over and over, even when the easier thing was right there and nobody would have blamed him for taking it.

I was so absorbed in the freedom of building my party that I didn't notice the story was using that same freedom to build its protagonist in front of me. That the hours I spent in the job menu were, in a small way, the experience of being Ramza — the gradual accumulation of capability and loss and wisdom that makes a person into someone who can face what the final chapters require.

The Hero History Forgot

There is something that has stayed with me about Final Fantasy Tactics that I don't think about often but feel consistently — a low, persistent note beneath everything else the game gives you. The knowledge, built into the framing story from the very beginning, that what you are playing is a true account that was suppressed. That the world inside the game decided this was not the history it wanted to tell. That Ramza was inconvenient — too honest, too principled, too unwilling to let the institution have the last word — and so the institution simply wrote him out.

Most RPGs end with the hero celebrated. The credits roll over a world that knows what was done and by whom. Final Fantasy Tactics ends with its hero forgotten, its truth buried, its victory invisible to the civilization that benefited from it. The world you saved does not know you saved it. The story you lived is classified. Radiata Stories understood the same thing — that the world keeps moving after the story ends, indifferent to what it cost the people who made that movement possible.

I came for the job system. I came for the freedom of building something exactly as I wanted it to be. I got all of that. And then the game waited until I was fully invested — until these people and this world had become real to me through hours of strategy and planning and caring — and it told me that the world doesn't always notice the people who do the right thing. That history is written by the people who remain, and the people who remain are not always the ones who deserved to.

That is not a comfortable thing to carry. It is the kind of thing that a game about giant mechs or a chosen hero or a world-ending threat would never have the architecture to say. Final Fantasy Tactics said it quietly, in between battles, underneath the story about succession and church politics and demonic stones.

I still think about Ramza. Not often. But when I do it's with something that isn't quite sadness — something more specific than that. The feeling of recognising a kind of person you hope to be, in a story designed to show you exactly what that costs.