The Unreal Engine editor stared back at Adrian Mercer like a blank canvas mocking its painter.
His fingers hovered above the keyboard. Didn't move.
The cursor blinked. Patient. Indifferent. Completely unbothered by the fact that Adrian had absolutely no idea where to begin.
Bzzzt.
His phone lit up on the desk beside him. A loan repayment notification — cold, automated, merciless. The due date stamped at the bottom read five days from now.
Five days.
Just like that, every ounce of momentum he'd carried out of Vertex Games' building evaporated. The resignation letter. The speech. Warren's furious face. All of it suddenly felt very far away and very small compared to the number sitting in that notification.
Adrian slumped back in his chair and stared at the ceiling.
Okay. Real talk.
How exactly was one person supposed to build a playable Outlast demo from scratch?
He was a designer. A good one. But not this kind of good. Building even a rough vertical slice of a horror game required an engine programmer, an environment artist, a sound implementer, and about six months he didn't have. The Vault had handed him the design framework, the concept art, the sound philosophy — a complete blueprint for something that could genuinely shake this industry to its foundations.
A blueprint was worthless without someone who could actually build the structure.
It wasn't difficult.
It was impossible.
Adrian sat up.
One name had been sitting at the back of his mind since the moment he'd walked out of that office building. Patient. Quiet. Waiting to be acknowledged.
Ethan Cole.
If you asked any professor from their graduating year to name the single most technically gifted student they'd encountered in their career, the answer came back immediately, every time, without hesitation.
Ethan Cole.
The guy who'd rewritten a networking library during exam season just because the existing one offended his standards. The guy who treated complex distributed systems problems the way most people treated crossword puzzles — something to engage with casually, between other things, before lunch. Every ranking, every assessment, every technical benchmark their program threw at them — Ethan had cleared all of it with the relaxed energy of someone operating well below his actual ceiling.
Adrian was good. He'd always known he was good.
Ethan had still beaten him without appearing to try.
The worst part — the genuinely infuriating part — was that Adrian couldn't even hold it against him, because Ethan was also his closest friend.
The memory surfaced without warning.
A dorm room at the peak of summer. The kind of heat that made the air feel thick. The entire floor smelled like instant noodles and collective sleep deprivation. Adrian and Ethan were jammed in front of a single laptop, its cooling fan screaming, screen packed edge to edge with scrolling code.
"Right here —" Ethan had jabbed a finger at the monitor, glasses sliding down his nose, wearing that faded grey t-shirt he rotated through three times a week. "Recursive lock at this junction. That's it. Concurrency conflict — gone. No workaround, no patch. Fixed properly."
His eyes behind those lenses had been alive. Burning with the specific joy of someone who loved what they were doing right down to the core of it.
He'd leaned back afterward, arms behind his head, grinning at the water-stained ceiling.
"One day we start our own thing. Build something that actually means something. Something that shakes the whole industry."
Adrian picked up his phone.
He knew exactly where Ethan had ended up. The whole program knew. It was one of those stories that circulated as either inspiration or cautionary tale, depending on your mood when you heard it.
Ethan Cole — the most gifted programmer their university had produced in a generation — now maintained legacy server infrastructure at Nexus Interactive. One of the largest, most stable, most aggressively profitable tech corporations in the country. Great salary. Great benefits. Ironclad job security.
Every single day, he used a weapon forged to slay dragons to slice bread.
It was the kind of waste that made Adrian feel something between grief and rage every time he thought about it.
He dialed.
Four rings. Five. Six.
"...Hello?" Ethan's voice came through rough and hollowed — the precise texture of someone who'd been in back-to-back meetings since early morning and was now running on caffeine and sheer stubbornness. "Who is this?"
"It's Adrian."
A beat of silence.
"Oh — hey." The exhaustion didn't lift, but something behind it shifted slightly. "What's going on? I literally just got out of a sync meeting. Was about to put my head down for ten minutes."
The background noise told the story clearly — the constant overlapping rhythm of a large open-plan office. Keyboards. Muffled voices running through presentations. Someone's video call bleeding through a flimsy partition wall.
Adrian didn't ease into it. There was no version of this conversation where easing in helped.
"I quit my job today."
Silence.
"I want to make a game. I need your help to build it."
Five full seconds of complete silence.
Then — "Are you serious right now?"
"Yes."
"You quit Vertex?" Ethan's voice jumped an octave. "Today? You just — walked out?"
"Handed in the letter this afternoon."
"Adrian." Ethan exhaled the name like he was setting down something heavy. "What about rent? You've got maybe three months of savings, I know how you budget. What happens in month four?"
"Ethan—"
"No — just listen for one second." The exhaustion had sharpened into something almost urgent. The voice of someone applying brakes because they genuinely cared. "I can't be part of this. My mortgage alone is over ten thousand a month. One missed payment and I'm getting calls I don't want to receive. I have zero room for risk right now. Zero."
"No team. No funding. No publisher connections. No distribution. What exactly are you planning to build this on — enthusiasm?"
"I'm telling you this because I actually like you — go find another job. The market is rough. Don't turn yourself into a cautionary story."
Every word was accurate. Completely, brutally accurate.
Adrian had expected all of it and prepared for none of it to change his mind.
"I have an idea," he said. "A real one. Something that would hit this market like nothing it's ever seen before."
A short, tired laugh came down the line. The laugh of someone who'd heard passionate pitches from passionate people and watched most of them dissolve on contact with reality.
"An idea." Ethan said it flatly. "Adrian, I generate a hundred ideas before noon every day. Ideas cost nothing. Ideas don't cover mortgages. What are you actually offering?"
"Something better than an idea."
"...What does that mean?"
"Three weeks ago you posted about a bug," Adrian said, keeping his voice level. "Your server's data synchronization layer. Sporadic corruption under high concurrency, no traceable source. You said your whole backend team had been on it for nearly two weeks and nobody had cracked it."
The line went very quiet.
"Don't give me an answer about the studio yet. Don't say yes or no to anything. Just send me the problem documentation and the relevant code. Give me some time with it."
"...Some time."
"If I come back with a solution that actually works — not a patch, not a workaround, a genuine fix — then all I'm asking is one honest conversation. You sit down and hear me out. That's the entire deal."
A long pause. Longer than the others.
Adrian could almost hear the calculation running on the other end. The math of this is completely insane colliding against but if he somehow actually does it.
"That bug has had fourteen engineers working it for twelve days," Ethan said slowly. "Senior engineers. People who've been doing backend architecture for years. It's not a simple problem."
"I know."
"You're a game designer."
"I know what I am."
Another pause.
"This is a waste of time," Ethan muttered.
A beat.
"But fine. I'll send it over." His voice shifted back into pure skepticism, pulling away from whatever small opening had just appeared. "Don't force it, Adrian. If you look at it and realize you're out of your depth — just say so. No shame in that."
"Send me the code."
Click.
Adrian set the phone down.
He sat still for a long moment in the quiet of his apartment.
Then he let the System surface.
The blue interface bloomed across his vision — steady, precise, that same calm luminescence that still managed to feel slightly unreal no matter how many times he'd seen it now.
[ GAME VAULT SYSTEM ]
Host: Adrian Mercer
Studio: Not established
Reputation Points: 1,000
Vault Access: Tier C — Independent / Mid-Scale Titles
He didn't look at the game list.
His attention moved to a corner of the interface he hadn't properly explored — understated, easy to overlook if you weren't specifically hunting for it.
A search bar. Labeled simply:
[ TECHNICAL REPOSITORY ]
Adrian felt something click.
If the Vault truly contained everything from Earth's gaming civilization...
Then it wouldn't stop at games.
Games didn't exist in isolation. They existed on top of decades — generations — of accumulated technical innovation. Engine architecture. Network programming. Server infrastructure stress-tested by millions of concurrent players across years of live operation, refined through incident after incident until the solutions were close to airtight.
He typed.
[ High-concurrency server architecture ]
[ Distributed data synchronization ]
[ Atomic locking mechanisms — root cause resolution ]
[ Race condition diagnosis — underlying layer ]
The Repository opened.
Immediately a notification appeared beneath the search bar, quiet but firm:
[ Technical Repository Notice: Advanced solutions require baseline domain understanding. Full implementation depends on collaborator expertise. Host access limited to diagnostic and structural framework. ]
Adrian read it twice.
Clear enough. The Vault wasn't going to hand him working code he could paste and ship. It was giving him the understanding — the architecture, the reasoning, the map. Actually building the fix would need someone who could translate that map into real implementation.
It needed Ethan.
He started reading.
It wasn't immediate. The material was dense — not beyond him, but requiring real concentration, the kind where you lose track of the room around you and surface an hour later unsure where the time went. Time blurred as he worked. He traced the problem carefully through the Repository's frameworks, cross-referencing the logic, following the chain of cause and effect down through the synchronization layer to the exact point where the race condition was forming.
By the time he'd genuinely understood it — not just skimmed it, actually understood it — nearly an hour had passed.
But he had it.
Not a workaround. Not a clever patch that bought six months before the same issue resurfaced in a different form. A structural solution that addressed the root cause directly — the kind that, once implemented correctly, made the bug architecturally impossible to reproduce.
He wrote it up. Not code — he knew better than to pretend otherwise. A clear, precise breakdown. Diagnosis first. The exact mechanism generating the concurrency conflict. The specific synchronization point where the race condition formed. The locking architecture needed to resolve it, and crucially, why it worked where the approaches his team had already tried would keep failing. Implementation notes clean enough that any skilled backend engineer could follow them straight to a working fix.
When Ethan's email arrived with the documentation and code snippets, Adrian was already most of the way finished. He cross-referenced, verified, adjusted two small details where his framework and the actual codebase diverged.
Then he wrote the subject line.
Here's your fix. Test it and call me.
He hit send.
The apartment settled back into silence.
Adrian reached for his coffee. Cold. He drank it anyway and looked out the window at a city running its million separate races toward its million separate versions of success.
Somewhere across town, Warren was almost certainly making calls right now. Pulling strings. Building walls. Doing exactly what he'd promised.
And in a glass office building somewhere closer, Ethan Cole was about to open an email from a game designer — his unemployed, apparently-losing-his-mind game designer friend — that contained a solution to a problem fourteen senior engineers hadn't been able to crack in twelve days.
Adrian set the mug down.
The apartment was quiet.
Then —
His phone vibrated against the desk.
Ethan's name lit up the screen.