Chapter 7

# Chapter 7

Twelve hours.

That's what the sword-carrying stranger gave us. Twelve hours before the safe zone—the only place in this entire nightmare where people could sleep without one eye open—collapsed like a cheap tent in a hurricane.

"I'm going to need you to elaborate on that," I said, in the calm and measured tone of a man who was absolutely not calm or measured.

The woman sat down by our fire uninvited, which I respected. Power move. Ghost remained standing, flickering at the edges like a bad signal. Maya kept her hands glowing, because Maya believed in preparedness the way other people believed in gravity.

"Name's Reese," the woman said. "Captain Angela Reese. Or I was, before—" She waved a hand at the general state of everything. "Before."

"Military?"

"Marines. Two tours. Got out, went private sector, was running executive protection in Manhattan when the sky cracked open." She said it the way you'd describe a commute. Matter of fact. "I've been outside the zone for most of the last week. Moving between survivor groups, mapping enforcer patrols."

That got Ghost's attention. He resolidified, which for him was basically a standing ovation. "You've mapped them?"

Reese tapped her temple. "Up here. Haven't had the luxury of a desk and a notebook." She glanced at my tablet—battered, cracked, but still functional thanks to a System-generated charging station I'd jury-rigged from a car battery and what I was pretty sure used to be a toaster. "But you have."

"I'm a software engineer," I said. "Documentation is kind of my thing."

"I know. I read your file."

Record scratch. "My *file*?"

Reese's expression didn't change. "When your name lit up every System terminal in the district, I pulled what I could from the public-facing System logs. Kevin Park. Level 4. Analyst class. Zero combat skills. Seventeen documented System anomaly reports." She paused. "You've filed more bug reports against the apocalypse than most people have kills."

"I feel like you're judging me."

"I'm *impressed*. Most people saw the System notifications about you and decided you were either dangerous or crazy. I decided you might be useful." She leaned forward. "Because that twelve-hour window? It's not a guess. The enforcers have been seeding relay nodes around the safe zone perimeter for two days. I've watched them do it. Six nodes, evenly spaced, forming a hexagonal array."

Ghost went very still. "A suppression grid."

"Bingo." Reese looked at him. "You've seen one before?"

"Once. Outside the Columbia campus zone, three days ago. They set up the same pattern. Took about six hours to activate." Ghost's voice was barely a whisper. "When it went live, the safe zone barrier didn't just drop. It *inverted*. Instead of keeping monsters out, it locked everyone in. Then the enforcers walked through the front door."

Nobody spoke for a moment. The fire popped and hissed. Somewhere across the camp, someone was playing a guitar. A bad guitar. Badly. The mundane sounds of survival continuing while we sat here discussing the end of it.

"How many people were in the Columbia zone?" Maya asked. Her voice was steady but her hands had stopped glowing. That was worse. Maya's magic only went dark when she was genuinely scared.

"About two hundred."

"How many got out?"

Ghost didn't answer. Which was an answer.

I pulled up my notes. My hands were shaking slightly, which I ignored because acknowledging fear is the first step toward being paralyzed by it, and I had work to do. "Okay. Okay. Let me think." I started a new document. Titled it *Safe Zone Collapse — Prevention Options*. The title was optimistic but I needed the morale boost.

"The relay nodes," I said. "Can they be destroyed?"

"I tried," Reese said. "Hit one with everything I had. Enchanted steel, fire skills, the works. It regenerated in about ninety seconds. They're System-spawned objects—same tier as dungeon walls. You'd need something that can damage the System itself."

"Or exploit it," I murmured.

Everyone looked at me.

"The System has bugs," I said slowly, the idea forming as I spoke, which was either brilliant or catastrophic and I wouldn't know which until it was too late. "I've documented seventeen anomalies. Inconsistencies in how it processes certain interactions. What if we could introduce an error into the relay network? Not destroy the nodes—*corrupt* them."

Ghost sat down. Finally. "You want to hack the apocalypse."

"I've been filing bug reports. Might as well start submitting exploits."

Maya looked at me the way she always did when I proposed something simultaneously genius and suicidal—like she was already calculating how much healing it would take to keep me alive through the attempt. "How would that even work? You can't just open a command prompt on a relay node."

"Maybe not directly. But the System processes player actions through its rules engine. Every time we fight, loot, craft, trade—it's all interpreted. Validated. What if we could feed it an action that the relay node has to process but can't handle correctly?"

Reese was watching me with an expression I recognized from every stakeholder meeting I'd ever been in: the look of someone deciding whether the engineer was a wizard or a lunatic. "You've done something like this before."

"Sort of. In the hospital dungeon—that's where I got flagged—I discovered that the System's loot tables have a race condition. When two players try to claim the same item at the same exact tick, the System throws an unhandled exception and defaults to generating a new item from a fallback table. Items that shouldn't exist." I pulled up my anomaly log. "I got a wrench that does 340 damage from what was supposed to be a first-aid kit drop."

I held up the wrench in question. It looked ridiculous. It *was* ridiculous. It also hit like a freight train.

"The point is," I continued, "the System has seams. Every system does. The relay nodes have to interface with the safe zone barrier, and the barrier has to interface with the monster spawning logic, and all of it runs through the same core rules engine. If we can find the right seam—"

"We can make the whole thing choke," Ghost finished. There was something in his eyes I hadn't seen before. Something that might have been hope, if hope were a feral animal that had been living in the dark for too long.

"I need to see one of these nodes up close," I said. "Get a reading on its System properties. See what rules it's operating under."

"The nearest one is about three hundred meters outside the barrier," Reese said. "Northeast corner, near the old parking structure on Eighth Avenue."

"Great. So we just need to walk outside the safe zone, into enforcer-patrolled territory, to examine a piece of System infrastructure that the System really doesn't want us touching." I looked around the fire. "Anyone see a flaw in this plan? Besides all of it?"

"I'll get you there," Ghost said. "I can suppress our visibility signatures for about twenty minutes. Thirty if I push it."

"And I'll keep you alive when you inevitably get hurt doing something stupid," Maya said. She was already rummaging through her bag, pulling out healing supplies. Actual supplies—bandages, antiseptic, a bottle of ibuprofen—alongside the glowing vials of System-generated health potions. Maya believed in redundancy.

"I'll run overwatch," Reese said. "I've been through that sector. I know the patrol timing. There's a gap between sweeps—about eight minutes every forty-five. If we time it right, we can get in, let your boy here do his nerd thing, and get out."

"My *nerd thing* is going to save this camp."

"Sure. But first you have to survive it."

Fair point.

We spent the next two hours preparing. Ghost scouted the approach route, slipping in and out of visibility like he was channel surfing between dimensions. Reese sketched patrol patterns in the dirt with a stick, marking timing windows with the precision of someone who'd done this kind of operational planning before the world had a heads-up display. Maya organized her medical kit with the focused intensity of a surgeon prepping for a twelve-hour operation, which, knowing my luck, wasn't far off.

I sat with my tablet and my notes and tried to figure out how to crash a System relay node using nothing but game mechanics and sheer audacity.

The thing about software—and I was increasingly certain the System *was* software, or something analogous to it—is that it's only as robust as its edge cases. Main workflows? Tested to hell and back. Happy paths? Smooth as silk. But the weird stuff? The interactions nobody thought to test because who would *do* that? That's where the dragons lived.

Metaphorical dragons. We had enough literal ones.

I reviewed my anomaly log. Seventeen documented bugs, ranging from minor display glitches to the loot table race condition that had armed me with the world's most dangerous plumbing tool. Three of them involved the safe zone barrier specifically:

**Bug #4**: Barrier flickers when a player logs out while standing exactly on the boundary line. The System can't determine if the player is inside or outside, causing a brief rendering error.

**Bug #11**: Barrier collision detection fails against objects moving faster than the System's physics tick rate. I'd discovered this when a player with a maxed-out throwing skill chucked a rock through the barrier wall. The rock passed through. The monsters, thankfully, could not—their collision boxes were processed differently. But the principle was interesting.

**Bug #14**: Barrier status refreshes on a sixty-second cycle. For one tick at the top of each cycle, the barrier's permission table is writable. I'd only caught this because I'd been monitoring System traffic out of professional habit. The write window was less than a millisecond. Useless, practically speaking.

Unless you could slow the cycle down.

I stared at Bug #14 for a long time. Then I looked at Bug #11. Then at Bug #4.

Separately, they were curiosities. Footnotes. But together...

"I think I have something," I said.

The other three gathered around. I turned my tablet so they could see the screen, though I suspect only about thirty percent of what was on it would make sense to anyone who didn't dream in stack traces.

"The relay nodes need to sync with the barrier's permission table to invert it. That sync happens during the barrier's refresh cycle—once every sixty seconds, there's a tiny write window. The nodes will use that window to inject their inversion command." I drew a diagram on the screen with my finger. It looked like a toddler's art project, but the logic was sound. "If we can force the barrier to enter an error state right when the relay nodes try to sync, the write command will fail. And if it fails hard enough—if we can get it to throw an exception instead of failing gracefully—the nodes should enter a recovery loop."

"How long would that buy us?" Reese asked.

"Depends on the recovery logic. Could be minutes, could be hours. If we're really lucky and there's no error handling—which, given the other bugs I've found, isn't impossible—it could brick the nodes entirely."

"And how do we force the barrier into an error state?"

I looked at Ghost. "How fast can you move?"

He tilted his head. "Fast enough."

"Bug #4 says the barrier glitches when a player is exactly on the boundary during a logout event. Bug #11 says objects above a certain velocity break the collision detection. If Ghost crosses the barrier boundary at maximum speed at the exact moment the refresh cycle ticks—"

"The barrier won't know if he's inside or outside," Maya said, catching on. She was smarter than she let on. She was smarter than most of us let on. "It'll error out."

"And the relay nodes will try to write to a table that's mid-crash." I couldn't keep the grin off my face. It was the same grin I used to get when I found a critical bug in production—the one that said *I know exactly how broken this is and I know exactly how to break it worse*. "They'll choke on their own sync command."

Ghost was quiet for a moment. "This requires precision timing. I'd need to hit the boundary within a window of less than a second, at full speed, at the exact right moment in the cycle."

"Yes."

"And if I'm a fraction off?"

"You bounce off the barrier hard enough to probably kill you, and the relay nodes activate on schedule."

Ghost nodded slowly. "I've had worse odds."

"When?" Maya demanded.

"I'm trying to be encouraging."

Reese stood up. Brushed the dirt off her knees. "We need to move in four hours. Before dawn, while the patrol gap is widest. Everyone get what rest you can." She looked at me. "Park. You sure about this?"

I wasn't sure about anything. I was a Level 4 Analyst in a world that rewarded people who could swing swords and throw fireballs. My best weapon was a wrench and my most dangerous skill was reading error logs. I was proposing to crash a System defense network using the digital equivalent of dividing by zero.

But twelve hours. Two hundred people in this camp. Families. Kids. The guitar player who was still butchering some acoustic version of a pop song three fires over.

"I'm sure," I said.

Reese gave me a look that said she knew I was lying but respected the commitment. Then she walked off into the dark, hand resting on the hilt of her glowing sword.

Ghost dissolved into shadows with a nod that might have been a salute.

Maya stayed. She always stayed.

"You know this is insane," she said.

"Most good ideas are."

"This might not be a good idea, Kevin."

"Then it'll be an interesting one." I turned back to my tablet. Started a new document: *Operation Divide By Zero — Execution Plan v0.1*. "Get some sleep. I need to calculate the exact timing for the barrier cycle."

Maya didn't move. "When's the last time you slept?"

I thought about it. "What day is it?"

"Kevin."

"I'll sleep when the safe zone isn't about to implode."

She sighed. Reached into her bag and pulled out a granola bar—an actual pre-apocalypse granola bar, the kind with chocolate chips that tasted like cardboard even before the world ended. She set it next to me without a word.

Then her hand glowed green, just for a second. A gentle pulse of healing energy that washed over me like warm water. Not fixing anything broken—just pushing back the exhaustion. Buying me a few more hours of clarity.

"Don't die," she said. "I've invested too many healing resources in you."

"Wouldn't dream of it."

She left. I ate the granola bar. It tasted like sawdust and survival.

Then I got to work.

The tablet's screen glowed in the darkness, the only light in my corner of the camp. Numbers scrolled. Timing calculations refined. Bug reports cross-referenced with relay node specifications that I was half-inferring from Ghost's observations and half-guessing based on how the System had handled similar infrastructure.

At some point, a notification appeared in my status screen. New. Unfamiliar.

**[SYSTEM NOTICE: User Kevin_Park — Threat Assessment upgraded. Previous: MONITOR. Current: PRIORITIZE. Enforcer dispatch authorized.]**

I stared at it for a long time.

Then I minimized it and kept working.

Four hours. We had four hours to save two hundred people using math, a sprint, and the desperate hope that whoever had built this System had been just as bad at error handling as every developer I'd ever worked with.

In my experience, that was a pretty safe bet.