CHAPTER 136: The Hidden Story and the Man Who Said ‘Again’ (Patreon)
Content
CHAPTER 136: The Hidden Story and the Man Who Said ‘Again’
George gave Torres the most counterintuitive instruction of his career on a Tuesday in May 2009 in the story room of Townsend Street.
"Write a complete story. With characters, motivations, arcs, tragedies. Then hide it."
Torres looked at him like a writer who has just been asked to build a house and then bury it. He understood perfectly, and he needed a moment to accept that what he understood was real.
"Put fragments in the item descriptions," George went on. "Put clues in the architecture of the levels. Put cryptic dialogue in the NPCs. The player who wants the story will have to look for it. The one who doesn't can ignore it completely and keep killing monsters."
Torres processed the instruction during ten seconds of silence George respected, because he knew Torres needed silence to think the way Lena needed music and Marcus a blank surface. Then Torres said:
"You want me to write a story no one is going to read in full?"
"I want you to write a story everyone is going to want to complete."
* * *
Dark Souls had no cinematics.
Nor did it have expository dialogue where an NPC explained the history of the world to the player for five minutes while the player waited for it to end so he could keep playing. It had no narrator. No flashbacks. No dream sequences where the protagonist's memories revealed the past. It lacked all the tools the games of 2009 used to tell stories.
What it had was items. Two hundred items with descriptions of two or three lines each.
Torres wrote each description as a fragment of narrative poetry. Each sword, each ring, each armor, each shield had a text that revealed a piece of the world without explaining it. The player who killed the first boss, the Asylum Demon, received an item: "Soul of the Asylum Demon." The description said: "Soul of the demon that guarded the asylum of the undead. It was once a guardian of the flame. Now it is a shadow of what it was." Two lines that revealed the monster had been someone, that it had guarded something, and that what it guarded had turned it into the thing the player had just killed.
Every item was like that. Two hundred fragments of a story the player assembled like a puzzle whose pieces arrived scattered across a world that didn't tell you where they were or how they fit, with no box and no final image to guide them. Some pieces fit immediately: the ring of a dead knight whose description mentioned the same war as another item, and suddenly the player understood that two items found in two different zones told the same story from two perspectives. Other pieces didn't fit until the player found a third one hours later. And some never fit, leaving gaps the community would debate for years.
"The gaps are deliberate," George told Torres when he expressed the concern that some fragments connected to nothing. "A story that's fully understood doesn't generate conversation. A story with gaps generates theories. The theories generate community. The community is what keeps a game alive after everyone has finished it."
Torres understood. And he began to write the history of Lordran like an archaeologist who buries his finds instead of displaying them, far from the screenwriter who simply tells a story.
* * *
The story Torres buried was that of a civilization that had fallen.
The gods had kindled the First Flame that kept the world in an age of light. The flame was fading. The gods had sacrificed some to feed the flame: they had burned them alive so their souls would serve as fuel. The sacrificed had become the monsters that populated Lordran. And the player was a resurrected dead, an undead marked by the Darksign whose fate was to decide whether to feed the flame with his own soul or let it fade and begin an age of dark.
But none of that was said directly. The player who completed the game without reading a single item description received the minimal version: a broken world, bosses to kill, a flame at the end. The player who read every description, who spoke with every NPC, who observed every detail of the architecture, received a tragedy: the story of gods who had created suffering to stay in power and of mortals sacrificed to feed a lie of eternal light.
Torres wrote the story in layers. The surface layer was action: the player fought, died, improved, fought again. The middle layer was mystery: fragments of lore that suggested something larger was happening. The deep layer was philosophy: the question of whether maintaining the light justified the suffering that fed it, and whether the dark, which everyone feared, was really worse than a light bought with sacrifice.
"Each player is going to reach a different layer," Torres said. "The casual one stays on the surface. The curious one reaches the mystery. The obsessive one reaches the philosophy. And all three finish the game satisfied because each layer is a complete experience."
George nodded. It was exactly the structure he remembered from other versions of these stories made by other people in his earlier life: a game that worked like a mine with three levels of depth, where most players stayed on the surface and where the ones who dug found something the others didn't even know existed. And the ones who dug were the ones who made the videos with titles like "The True Lore of Dark Souls" and "Gwyn's Sacrifice Explained" that kept the game alive in the cultural conversation for years after its release.
The NPCs complemented the items. Torres wrote 20 characters who spoke in cryptic fragments: lines that seemed like nonsense the first time the player heard them and that acquired meaning when he found the item or the zone that gave them context. Solaire, the knight who searched for "his own sun" with a joy that seemed like madness in a world where there was no reason for joy. Siegmeyer, the fat knight who feigned bravery to hide a fear only the player discovered if he followed his questline to the end. Quelana, the pyromancer who knew more than she said and who only revealed the truth if the player asked her the right questions in the right order.
Each NPC had a questline the player could complete or lose. Completing it required talking to the NPC at specific moments, in specific places, without having done certain things that closed the line forever. The player who killed an NPC by accident, or by choice, lost his questline permanently. There was no way to recover it except to start the game over.
"Writing cryptic dialogue is harder than writing clear dialogue," Torres said at the end of May, when he finished the 20 NPCs with their questlines and their fragments of lore. "Because every word has to say two things: what the character says and what he hides. In The Witcher, Yennefer says one thing and means another. In Dark Souls, everyone says one thing and means another. It's a whole world of Yennefers."
George laughed. Torres didn't. Torres was serious: writing a world where the truth was hidden behind every line was exhausting in a way that writing a world where the truth was on the surface wasn't. The Witcher asked Torres to write complex characters. Dark Souls asked him to write a complex world. And a world was bigger than any character.
* * *
George needed someone to run Team Souls day to day.
He couldn't do it himself. Team Witcher consumed his mornings, his afternoons, and a good part of his nights. The Velen quests were in production, Yennefer's dialogue was being recorded, the alchemy system needed constant calibration. George spent twelve hours a day on the ground floor of Townsend Street with Team Witcher and had no hours left to be on the upper floor with Team Souls the way a director needed to be: present every hour of every day, making the small decisions George couldn't make because he was in another room designing quests with Torres or calibrating the combat with Elena.
George interviewed 12 candidates in May and June. Project directors from studios in San Francisco, Los Angeles, Seattle. Senior programmers who wanted to move into direction. Producers from big studios who wanted a small one. All of them had impressive resumes. All of them had experience. And none of them understood what George wanted from Dark Souls.
All of them proposed adding accessibility. All of them suggested an easy mode. All of them said that a game without a map was "hostile to the user." All of them used phrases like "broadening the player base" and "lowering the barrier to entry" and "optimizing first-day retention," phrases that sounded reasonable and that were exactly the opposite of what Dark Souls needed. Dark Souls wanted to deepen the base instead of broadening it. It wanted the barrier to be the game itself. It wanted the player who stayed after the first day to stay forever.
George was about to widen the search to Japanese studios when Marcus Webb suggested a name George knew but hadn't considered:
"Kenji Nakamura."
Kenji was the Japanese 3D modeler who had been Marcus's freelance mentor for three years when Marcus was a junior artist learning to do 3D. Ex-Pixar Tokyo. Japanese. He had left Pixar to work as a freelancer in the video game industry and had spent three years hopping between projects as an art and technical direction consultant.
"Kenji isn't a project director," George said. "He's an artist."
"Kenji is an artist who directs," Marcus said. "At Pixar he directed teams of 20 people. As a freelancer he's led the production of three games from start to finish. He doesn't do PowerPoints. He doesn't schedule unnecessary meetings. He sits with the team, works with the team, and if something isn't right, he redoes it with his own hands until it is. He's the most meticulous person I know."
George called Kenji that afternoon. He described Dark Souls in fifteen minutes: the philosophy of difficulty, Lordran, death as a teacher, the environmental narrative, the bosses. Fifteen minutes of George speaking without interruption, something unusual because George wasn't one for long monologues, but Dark Souls required fifteen minutes to describe, because they were fifteen minutes of ideas that couldn't be separated without losing their meaning.
Kenji listened in silence. He didn't interrupt. He asked no questions during the fifteen minutes. When George finished, there were five seconds of silence on the line. Then Kenji said a sentence in Japanese that he afterward translated:
"Difficulty is the purest form of respect. If you tell the player he can do something easily, you're telling him his time is worth nothing. If you tell him he's going to have to work, you're telling him the result is worth the effort."
George hired him on the spot.
* * *
Kenji started at Team Souls the first week of June 2009.
He was quiet, precise, and demanding in a way that needed no volume. He didn't shout. He didn't push with deadlines or threats or the artificial urgency of someone who believes pressure produces quality. Kenji believed the opposite: that quality produced its own pressure, an internal pressure each artist and each programmer felt when he looked at his work and knew it wasn't finished. His role was to create the standard the pressure was reaching for.
He looked at the work of every person on the team and knew when something was finished and when it only looked finished. That difference separated good games from extraordinary ones, and Kenji lived in it like a guard patrolling a border no one else could see. A 3D model any other director would have approved, Kenji returned with a single word:
"Again."
He didn't explain what was wrong. He gave no detailed instructions on how to fix it. He said "again" and waited for the artist or the programmer to find the problem himself. Because finding the problem was as important as fixing it: a team that depended on the director to identify the mistakes was a team that didn't grow. A team that found its own mistakes improved with every iteration.
At first, the team got frustrated. An animator who received an "again" with no explanation didn't know what to look for. But the uncertainty lasted a day. The next day, the animator looked at his work with fresh eyes and saw what Kenji had seen: a frame where the weight of the blow didn't land, a transition between animations that was technically correct but not fluid, a movement that looked right but didn't feel right. That difference between looking right and feeling right was the border Kenji patrolled.
In two weeks, the team stopped getting frustrated and began to anticipate. The artists reviewed their own work before showing it to Kenji, looking for what Kenji was going to find, trying to reach the standard before he said "again." The work that reached Kenji was better every day. And when something arrived and Kenji didn't say "again" but instead nodded once, the artist felt something no verbal praise could produce: the certainty that his work had reached a standard that needed no words to be recognized.
George visited Team Souls on Tuesdays and Thursdays. Every visit found the game better than the last. Better through the accumulation of small corrections Kenji drew out of the team, more than through big leaps, with the patience of a sculptor who removes material instead of adding it. A texture with a little more detail. An animation with one less frame of transition. A light effect 5% warmer. Each correction was invisible on its own. The sum was visible.
"How's it going?" George asked every Tuesday.
"Better," Kenji answered every Tuesday. Without explaining how much better or in what. Just "better." And that was enough. Because "better" said by Kenji meant the game was closer to what it had to be, and that the distance between what it was and what it had to be shrank with every "again" Kenji said and with every review the team did before he asked for it.
George watched Kenji work one Thursday in July at seven in the evening, when most of Team Souls had already left. Kenji was sitting in front of his monitor reviewing the textures of Firelink Shrine with the attention of someone looking at a painting in a museum: without hurry, without agenda, with only the determination to see everything there was to see. And George thought he had found exactly what he needed: a man who understood that difficulty was respect, that "again" was a form of love, and that the difference between good and right was what made a game last for years in the memory of players, far beyond a few months.
It was the first time George had delegated the direction of a game. And the person he had delegated it to was someone who directed by saying a single word.
Again.
End of Chapter 136