Kohlingen called Locke a thief. Every citizen of that small northwestern village saw a pickpocket in a blue bandana — everyone except Rachel, and she had been dead since before the game began. Locke calls himself a treasure hunter, corrects anyone who says otherwise, and the game quietly needles him for it: his battle command is Steal. But the word matters to him more than the joke lets on, because exactly one person ever said it to his face and meant it.
Rachel is the wound under every Locke scene — the vow he makes to a stranger in a mine, the fight he picks over a woman he barely knows, the relic he chases across a broken world. Follow her, and a character most players file under “the bandana guy who steals” turns into the most quietly grief-stricken person in the party. Here is the shape of it.
The treasure hunter nobody else believed
The word came from his father first. Locke was raised by a man who travelled the world hunting treasure, and when his father died, Locke kept the title. Kohlingen didn’t honour it. To the town he was a light-fingered drifter, and the game never fully lets him off the hook — his signature skill is Steal, and a Thief Glove upgrades it into Mug. He protests the label anyway, every single time, because the label was never really about the loot. It was about who he wanted to be.
Rachel was the one person who used his word without a smirk. She called him a treasure hunter and meant it, and that recognition is the thing that let him carry the name with any pride at all. Her father saw the same pickpocket the rest of the town saw and refused to let Locke near her. So Locke did the most Locke thing imaginable: he set out to prove the word true. He would take Rachel to find a real treasure and come back as someone her father couldn’t turn away.
It matters that Locke is the Returner least tied to any post — the free agent, the one who can drop everything and move, which is exactly why he is the one sent to shadow a fugitive girl in Narshe later on. But that lightness has a source. Everything that breaks in Locke’s life breaks because he needed one man to believe the name one woman had already given him.
The bridge, the amnesia, and the year he stayed away
The treasure hunt went wrong fast. Deep in a cavern, crossing a rope bridge, the planks gave way under Locke. Rachel lunged, shoved him back onto solid ground, and fell in his place. He went down after her and dragged her out, and she lived — but when she woke, her memory was gone. She didn’t fall because she was careless. She fell because she saved him. That inversion is the exact shape of his guilt for the rest of the game: she could catch him, and he could not catch her.
Then the second wound, worse than the first. Rachel’s father blamed Locke, threw him out of the house, and Rachel — with no memory of who he was — took her father’s side and asked the stranger to leave. A man in town told Locke the kindest thing he could do was disappear, so she could build a new life without him hovering at the edge of it. So he left. He put her recovery ahead of his own heart and walked out of Kohlingen. In the moment, it reads as the selfless choice. It is also the decision he will spend the entire game trying to take back.
The cellar in Kohlingen
He came back a year too late. When Locke finally returned, the Empire had already been to Kohlingen, and the raid had killed Rachel. The cruelest detail is the timing of her memory: it came back right at the end, just before she died, long enough for her to remember him, say his name, and leave a message for a man who wasn’t there — if he ever came home, tell him she loved him. Locke walked into that a year late, and the guilt closed over him. He had left to protect her, and leaving is what put her in the path of the raid. His private grief and the war he now fights were welded together in that single morning.
He couldn’t bury her. Instead he found the strange old man on the edge of town, the one the villagers avoid, and paid him to preserve her body — an herbal concoction that keeps her exactly as she was, laid out on a cellar bed, surrounded by flowers. The house upstairs sits empty; the town whispers it’s haunted. And the man who keeps her still talks about her the way you’d talk about stored treasure, pleased with his own craft, certain she’ll never age a day. Sit with that for a second. The town’s thief has one treasure in all the world, and it’s a body in a basement he pays a stranger to guard. That grief is the engine of the whole character — it drives him into the Returners, and it sends him chasing a rumour: a relic, somewhere, that can raise the dead.
“I won’t leave you until your memory returns”
Watch what he says in Narshe. Long before any of that backstory is spelled out, Locke pulls a girl out of the hands of Imperial soldiers in the Narshe mines. She has just been freed from a mind-control crown, and her memory is gone. Locke asks if she has amnesia, and something in him locks into place — he makes her a promise no stranger has earned: “I won’t leave you until your memory returns!!”
That’s Terra, and the vow makes no sense as a response to a woman he met ninety seconds ago — until you know about Rachel. “Amnesia” is the trigger word. Terra’s blank memory drops Rachel straight into the scene, and the promise is aimed backward as much as forward. “I won’t leave you” is the apology for leaving amnesiac Rachel. “I’ll protect you” is the apology for failing to. He isn’t being chivalrous. He’s trying to re-run a scene that already ended badly, with the ending changed.
On a replay, listen for the vow repeating. The same protective reflex fires the moment Celes is in danger, and other characters clock it — teasing Locke about his complicated past. Once you’ve caught it, you can’t un-hear it: every “I’ll protect you” in the game is the same unfinished sentence, re-aimed.
The quiet tragedy is that the vow is always a little disproportionate, always a little too much for the woman actually standing in front of him — because it was never really meant for her.
The cracked stone that finally let go
The relic has a name: Phoenix. The legendary treasure Locke chases across a broken world is the magicite of the esper Phoenix — an esper whose power can revive the dead. In the World of Ruin he finally runs it down. The trail runs through a painting in Owzer’s mansion, which hides the clue that the treasure waits where the mountains form a star; the star turns out to be a range northwest of Tzen, and the cave beneath it is a two-party puzzle guarded by a Red Dragon. The party catches up with him in the deepest chamber, holding the stone at last. He has his hoard, too — the treasure hunter loots the place clean on the way out. But the magicite is old, and it’s cracked deep, and Locke already fears it might not be enough.
It isn’t. Laid on Rachel’s body back in Kohlingen, the stone glows, and she wakes — for a few seconds. Long enough to thank him. Long enough to tell him the one thing he has needed to hear for the whole game: let go of the guilt, cut the chain, and love the person already in his heart. Then she gives herself back to the Phoenix, reforms the stone to full strength, and is gone. He spent years and crossed a dead world for a treasure that hands him nothing to keep. That is the entire point of it.
There’s a reading of this scene that most English write-ups skip: the crack in the magicite was mercy, not failure. A full revival would have handed Locke a living Rachel and a debt he could never refuse — he’d have stayed with her out of obligation even if his heart had already moved on. The broken stone gives him the one thing a whole one couldn’t: a real goodbye, and permission to want a different life.
The treasure he actually found
Celes was there the whole time. While Locke was still chasing a dead woman, he was falling for a living one. Celes — the former Imperial general — gets close to him in the first half of the game, and then he nearly loses her over exactly the flaw Rachel left behind. When Kefka accuses Celes of being a spy, Locke hesitates one beat too long before he says he trusts her, and that hesitation costs him. A man who has already failed one woman is terrified of misplacing his faith in another. They reconcile later, in Thamasa, and the token that carries the whole thing is his bandana — the same blue cloth from the opening scene.
Here is the payoff the game has been building for hours. In the finale, as the tower comes down, Celes goes back for that dropped bandana and the floor gives way beneath her — and this time Locke catches the falling woman. The exact scene he lost on the bridge, run again, ending the other way.
“A person worth protecting.” — Locke, asked at the end what he has left to live for
The vow that began as guilt ends as a choice. And if you go back into the World of Ruin now, with Locke’s shape in your head, you’ll start seeing that the whole cast is built this way — everyone here is carrying one specific loss and learning to live around it. Celes at the cliff, Cyan and his letters, Shadow and his dreams. Locke just wears the seam where it shows. Round the party back up and watch for it, because Final Fantasy VI is a game about people rebuilding on top of what the world took from them, and Locke is the one who lets you see clearly what that costs — and what it gives back. In Kohlingen, the flowerbed that never once bloomed finally does.
Common Questions
Why does Locke want the Phoenix in FF6?
Because the Phoenix magicite can revive the dead, and Locke wants to bring Rachel back. It’s the legendary treasure he chases the entire game. When he finally uses it, the magicite is cracked, so it only revives her for a few moments — long enough for a goodbye, not a second life.
Does Rachel come back to life?
For a few seconds. The Phoenix magicite is old and cracked, so instead of a full revival Rachel wakes just long enough to thank Locke and tell him to let go and love again. Then she merges with the Phoenix to restore its power and passes for good. The brevity is the mercy — it gives Locke a farewell without trapping him in the past.
Does Locke end up with Celes?
The game implies it strongly without ever staging a wedding. The bandana she carries, Rachel’s blessing to love the person already in his heart, and the finale where Locke catches Celes as she falls all point the same way. It’s left as a clear implication rather than a spelled-out romance — which fits an ensemble where every pairing stays understated.
Was there something wrong with Locke and Rachel’s ages?
No — the “age 16” line people sometimes cite comes from a gravestone easter egg in Final Fantasy Tactics, not from Final Fantasy VI. The game itself never assigns Rachel an age. Treat the Tactics joke as a wink between titles, not canon.
Is Locke just a thief who calls himself a treasure hunter?
Both are true, and the tension is the point. His battle command really is Steal. But the title came from his father, a genuine treasure hunter, and Rachel is the one person who ever used it without mocking him. When Locke insists on “treasure hunter,” he’s defending the version of himself she believed in.