Patch Notes

Jae-won did not sleep that night.

He sat at the desk in his one-room apartment in Gwanak-gu—a space that a generous person might call cozy and a realistic person would call a closet with plumbing—and filled seventeen pages in the notes app with everything he could remember. The layout of the corridors. The patrol patterns of the Glitch Crawlers. The exact wording of every system notification. The sensation of the Core Fragment, which he could still feel in the back of his skull like a pebble lodged in the folds of his brain.

At 3:14 AM, he made ramyeon. At 3:47 AM, he ate it cold because he'd gotten distracted trying to draw the circuit-vein topology from memory. At 4:22 AM, he discovered that if he concentrated—really concentrated, with the kind of focused attention that usually only manifested during the final hours of a regression test marathon—he could make his status panel appear.

It materialized in his peripheral vision first, a translucent blue shimmer that solidified when he looked directly at it:

╔══════════════════════════════════════╗ ║ SYSTEM OVERRIDE — USER INTERFACE ║ ╠══════════════════════════════════════╣ ║ Name: Kim Jae-won ║ ║ Class: Unassigned ║ ║ Level: 1 ║ ║ HP: 120/120 ║ ║ MP: 65/65 ║ ║ STR: 9 DEX: 12 INT: 20 ║ ║ WIS: 13 CON: 10 CHA: 7 ║ ║ Unallocated Points: 0 ║ ║ ║ ║ Skills: Climbing (Lv.1) ║ ║ Observe (Lv.1) ║ ║ Analyze (Lv.1) ║ ║ Passive: Pattern Recognition ║ ║ Titles: Improvised Demolition ║ ║ Debug Access: Level 1/10 ║ ╚══════════════════════════════════════╝

The panel was visible only to him. He confirmed this by standing in front of the bathroom mirror and noting that the blue glow did not appear in his reflection. He confirmed it again by calling it up while standing at the window—no passersby on the street below reacted to the floating holographic interface hovering next to the face of a twenty-six-year-old man in his underwear.

He also confirmed that the status panel cast no shadows, emitted no measurable light (his phone camera saw nothing), and could not be touched by any object other than his own fingers. It existed on a layer of reality that was his alone.

> BUG REPORT #002 > Product: System Override v0.1 > Severity: Medium > Reporter: Kim Jae-won (User, Level 1) > > Summary: User interface persists outside of active System zone. Panel is visible to user only. No physical interaction with real-world objects. > > Expected Behavior: UI should only appear in System zones (if system is zone-locked). > > Actual Behavior: UI accessible anywhere. Appears to be permanently bound to user's perceptual layer. > > Notes: This is either a feature or a significant scope leak. System may not distinguish between 'in-zone' and 'out-of-zone' states for UI rendering. Alternatively, the user IS the zone. Investigate. > > Priority: P2 > Status: Open

At 5:30 AM, the counter in the back of his mind read 18:21:47. He tried to analyze it with the [Analyze] skill and got a result that made him sit down hard on his bed.

> ANALYSIS: System Activation Timer > Type: Global Event Timer > Function: Countdown to next spatial merge event. > Current interval: 24 hours (base rate). > Note: Interval may decrease based on world state variables. Debug level insufficient to access variable list.

"The interval can decrease," Jae-won said to his empty apartment. "So it's not a fixed daily thing. The merges could come faster."

He added this to his notes. Then he added a new section: UNKNOWNS.

1. Who or what built System Override? 2. Am I the only user? 3. What triggers the spatial merges? 4. What happens when the system reaches v1.0? 5. Is the system hostile, neutral, or designed with user survival in mind? 6. Why did it give me debug access? 7. Can I die in the real world from system-related injuries?

The last question was the one he kept coming back to. His HP had dropped by 2 points from the fall off the shelf, and those 2 points had regenerated by the time he got home—1 point per hour, apparently, which he'd confirmed by watching the number tick up. But did HP loss in the system correspond to actual physical damage? Would reaching 0 HP kill him? The tutorial quest had stated "Death (Permanent)" as the failure condition, which was the most concerning parenthetical he'd ever read.

At 6:15 AM, his alarm went off. Wednesday. Work.

He stared at the ceiling. The idea of going to Nexion Interactive and spending eight to twelve hours testing whether an NPC's idle animation clipped through a barrel felt absurd. He had just survived a dimensional merge. He had a stat panel. He had killed a creature made of corrupted data by throwing his company laptop at a ceiling.

But he also had rent due in nine days and a bank account that laughed at the concept of savings.

He showered, dressed, and caught the 7:20 AM train. Line 2. The same line.

The train was aggressively normal. Rush-hour crowds pressed him into a corner near the door, and he spent the ride with his face approximately four centimeters from a businessman's shoulder, breathing in cologne and anxiety. The fluorescent lights hummed. The stations arrived and departed on schedule. At no point did the windows go black or the intercom start speaking in alien languages.

But [Pattern Recognition] was active. And it showed him things.

Small things. A hairline crack in the subway tile at Sadang station that pulsed, faintly, with the same blue light as the circuit veins from last night. A flicker in the LED display above the doors—too fast for normal eyes, but his INT 20 passive caught it—that resolved, for a single frame, into system text: [NODE DETECTED]. A woman standing near the center of the car who had, for exactly one-half of one second, a translucent blue outline around her silhouette.

Jae-won forced himself to look away. If the system was leaking into reality, or reality was leaking into the system, then looking too closely at the seams might attract attention. Whose attention, he didn't know. But the tutorial had been labeled v0.1. Software in v0.1 was unstable, full of unintended behaviors, and often actively hostile to users who poked too hard at the boundaries.

He arrived at Nexion Interactive at 8:04 AM, four minutes late. Nobody noticed. Nobody ever noticed.

The office occupied two floors of a building in Pangyo—Korea's Silicon Valley, a planned city of glass towers and optimism that had aged poorly. Nexion's floor had the particular atmosphere of a company that had been circling the drain for long enough that everyone had stopped pretending the drain wasn't there. Half the desks were empty, claimed by the last round of layoffs. The remaining staff moved through their routines with the grim efficiency of soldiers who'd accepted the siege was lost but hadn't yet received permission to retreat.

Jae-won's desk was in the QA corner—a cluster of four workstations separated from the developers by a low partition that someone had optimistically covered in sticky notes reading "COMMUNICATION IS KEY" and "WE SHIP QUALITY." Of his three QA colleagues, only one was present: Yoon Sera, who was twenty-four, perpetually caffeinated, and in possession of the kind of focused intensity that made her either an excellent tester or a future supervillain.

"You look like you slept in a dumpster," Sera said without looking up from her screen.

"Didn't sleep."

"The crafting regression?"

"Something like that."

He sat down and logged in. Thirty-seven unread Slack messages. Two from his team lead, Park Jihoon, both marked urgent. He opened the first one.

@park_jihoon: Jae-won, marketing confirmed the patch announcement for Friday. Crafting overhaul regression needs to be DONE by Thursday noon. No exceptions. I know the code is rough but we need results.

The second message was from twenty minutes ago.

@park_jihoon: Also: your laptop isn't showing on the asset tracker. Did you bring it in?

Jae-won looked at his messenger bag. The bag that no longer contained a company laptop because that laptop was buried under obsidian rubble in a dimensional pocket that existed beneath Seoul's subway system.

"Sera."

"What."

"Hypothetically, if you lost a company laptop in a way that was impossible to explain, what would you tell IT?"

Sera finally looked at him. She had the expression of someone performing a risk assessment. "Hypothetically?"

"Completely hypothetically."

"I'd say it was stolen. File a police report. They never follow up on those, and IT just orders a replacement."

"Right. Stolen. From the subway."

"Classic."

He sent a message to IT about a stolen laptop—the lie tasted strange, though less strange than the truth would have—and turned his attention to the crafting overhaul regression suite. Chronofall Online's crafting system was a module of approximately forty thousand lines of code that had been written by three different developers over two years, none of whom had commented their work, all of whom had since left the company. Testing it was like performing an autopsy on a creature that had been assembled from parts of several different animals.

But today, something was different.

[Pattern Recognition] was still active. It was, as far as he could tell, always active—a passive overlay on his perception that highlighted anomalies and inconsistencies. And it worked on code.

He was reading through the crafting interaction handler—a function that governed what happened when a player combined two items—when the passive triggered. A section of code pulsed with a faint highlight in his vision. Not the blue of the system UI, but a soft amber, like a warning light. He focused on it.

The highlighted section was a type coercion. The function expected an integer for item quantity but received the value from a text field without validation. In most cases, JavaScript's loose typing would handle it silently. But if a player typed a non-numeric character—a period, a comma, a Korean character accidentally left in the input—the function would fail silently, producing a null that cascaded through three subsequent calculations and ultimately caused the loot table to desync.

Jae-won had been staring at this code for two weeks. He'd been looking for the source of the loot table desync for two weeks. And now, in approximately four seconds, [Pattern Recognition] had found it.

He sat very still.

Then he activated [Analyze] on the code. Not through the system UI—he couldn't exactly project a holographic panel in the middle of the office—but by focusing the same mental process he'd used in the transit hub. The skill activated. He felt a faint drain on his MP, and information arranged itself in his mind with a clarity that was almost physical.

> ANALYSIS: crafting_interaction_handler.js > Anomaly: Line 247 — Implicit type coercion of user input. > Root cause: Missing parseInt() wrapper on quantity field. > Impact: Cascading null propagation → loot_table_sync.js → inventory_manager.js → client desync. > Fix complexity: Trivial. Single-line change. > Related issues: 14 additional instances of missing input validation in crafting module.

Fourteen additional instances. He activated [Analyze] again, broader this time, feeding it the entire crafting module's structure as he scrolled through the files. The skill consumed 5 MP per activation, and he had 65 total, but the information it returned was worth orders of magnitude more than the cost.

In forty minutes, he found and documented all fourteen instances. He wrote the bug reports with a specificity and confidence that would have taken him days of manual testing. Each report included the exact line number, root cause, impact chain, and recommended fix.

He submitted them and leaned back in his chair. His MP was down to 30/65. The regeneration rate outside of system zones seemed slower—maybe 1 per ten minutes, based on the trickle he'd been watching. But the skills worked. The system's abilities functioned in the real world.

The implications were staggering.

Sera leaned over the partition. "Did you just submit fifteen crafting bugs in forty minutes?"

"Yes."

"It took you two weeks to find three before today. What changed?"

"Coffee," Jae-won said. "Really good coffee."

Sera's eyes narrowed. She was too good a tester to accept a clearly insufficient explanation, but she was also too professional to push when there were deadlines. She returned to her screen. Jae-won could feel her suspicion like a physical weight.

He spent the rest of the morning using [Analyze] sparingly—one activation per hour, enough to let his MP regenerate between uses. Each activation revealed structural issues in the codebase that would have taken hours to find through conventional testing. By noon, he'd submitted twenty-three bug reports, more than his typical weekly output.

Park Jihoon appeared at his desk at 12:15, looking like a man who'd just seen a magic trick and was trying to decide whether to applaud or call security.

"Jae-won. The bug reports."

"Yes?"

"They're good. They're really good. The devs confirmed seven of them already. The loot table desync fix—they said that single line change resolved a bug that's been in the tracker for three months."

"It was just there in the code. I'm surprised nobody caught it sooner."

Jihoon studied him. "Are you feeling alright?"

"I'm fine. Why?"

"You look like you haven't slept, you lost your laptop on the subway, and you just turned in the most productive morning of work I've seen from any QA tester in five years." Jihoon paused. "I'm trying to decide if you're having a breakthrough or a breakdown."

"Can't it be both?"

Jihoon didn't laugh. He was a serious man who managed a QA team at a dying company and had the particular exhaustion of someone who cared about quality in an environment that had decided quality was a luxury. "Just keep it up," he said. "If the crafting regression is clean by Thursday, we might actually ship on time. And that might be enough to keep the lights on for another quarter."

He walked away. Jae-won watched him go and felt an unfamiliar pang of something that might have been guilt. The bug reports were real. The fixes were correct. But the method was a cheat—a literal system exploit that gave him capabilities no normal tester had. Was it dishonest? Was it the same as using performance-enhancing drugs in sports?

He shelved the ethical dilemma. There would be time for philosophy when he wasn't facing a Friday deadline and a 24-hour countdown to his next encounter with an alternate dimension.

Lunch was a convenience store triangle kimbap eaten at his desk. Sera ate with him, as she usually did, maintaining a companionable silence that was one of the things Jae-won appreciated most about her. She didn't fill quiet with noise. She understood that sometimes silence was a feature, not a bug.

"Sera."

"What."

"Have you ever found a bug that made you question the entire architecture of the system?"

She chewed thoughtfully. "Every Tuesday."

"I mean a really fundamental one. Not a logic error or a missing null check. Something that made you think the system was designed to fail. Or designed to be something other than what it appeared to be."

Sera set down her kimbap. "You're being weird today."

"I know."

"Weirder than usual."

"I know that too."

She was quiet for a moment. Then: "Last year, I was testing the social interaction module. Friend lists, guilds, chat. Standard stuff. But I found this buried function—no comments, no documentation, no references anywhere in the design docs. It was monitoring player communication patterns. Not content—not reading messages—but metadata. Who talked to whom, how often, what time of day, response latency. Building a social graph."

"That could be for matchmaking."

"That's what the devs said when I flagged it. But the function wasn't connected to the matchmaking system. It was connected to nothing. It just... collected data and stored it in a table that nothing else referenced. A dead-end function that was actively running."

"What did you do?"

"Filed the bug report. They closed it as 'by design' with no further explanation. I pushed back. They told me to focus on the items in the sprint." She shrugged. "Sometimes systems have pieces that don't belong. Legacy code, abandoned features, undocumented experiments. Not everything in a codebase has a purpose. Some of it is just... residue."

Jae-won nodded. But he was thinking about the System Log he'd read in the transit hub—the clean, precise entries that tracked the spatial merge in real time. That wasn't residue. That was infrastructure.

"What if it wasn't residue?" he said. "What if the piece you found was part of a different system entirely? One running on top of the one you were supposed to be testing?"

Sera gave him a look. "Then I'd say someone owed me a much bigger paycheck. And probably an NDA."

The afternoon passed in a blur of regression testing. Jae-won rationed his [Analyze] activations, using the skill only for the most complex interaction chains and relying on his natural abilities—augmented by INT 20 and [Pattern Recognition]—for the rest. Even without active skill use, the passive bonus was transformative. Code that had been opaque to him yesterday now revealed its structure at a glance. He could trace dependency chains in his head, hold multiple state machines in working memory simultaneously, and spot off-by-one errors from across the room.

By 5:00 PM, the crafting overhaul regression suite was ninety percent complete. He'd found thirty-one bugs, six of which were critical, and the development team was already patching the highest-priority fixes. Park Jihoon had stopped asking if he was okay and started asking if he wanted a raise—which, at Nexion Interactive, was a joke, but a well-intentioned one.

Jae-won stayed late. Not for the regression suite—that could wait until tomorrow—but because he wanted the office empty.

By 8:00 PM, only the overnight security guard remained. Jae-won sat at his desk in the darkened QA corner, the blue glow of his monitor the only light, and pulled up his system panel.

HP: 120/120. MP: 63/65. Two points still regenerating from his last [Analyze]. The timer in the back of his mind read 04:07:22. A little over four hours until the next activation.

He opened the System Log. With debug access, he could see entries that shouldn't have been visible to a normal user. He'd been checking periodically throughout the day, and the log had been updating in real time.

> [06:15:33] User KJW-001 — Biometric status: Sleep-deprived. HP regeneration rate reduced by 20% until rest threshold met. > [07:21:04] User KJW-001 — Zone transit: Seoul Metro Line 2. Merge residue detected at 3 nodes. Passive scan complete. > [07:21:04] System note: Merge residue consistent with increasing spatial instability. Next merge event may generate higher-difficulty zone. > [08:04:17] User KJW-001 — Entered non-System structure (Nexion Interactive). No zone generation. Passive monitoring active. > [08:47:33] User KJW-001 — Skill [Analyze] used on non-System target (JavaScript source code). Efficiency: 94%. Note: User's professional domain knowledge provides significant synergy with analytical skills. > [12:15:01] System note: User KJW-001 performance metrics exceed expected baseline by 340%. Flagging for advanced class compatibility assessment.

Jae-won read the last entry three times. "Advanced class compatibility assessment." The system wasn't just tracking him—it was evaluating him. His performance today, his use of skills in a professional context, his efficiency metrics—all of it was being measured against some internal benchmark.

And he was exceeding it by 340%.

He scrolled further. Most entries were routine—passive scans, biometric updates, MP regeneration logs. But near the bottom, timestamped twenty minutes ago, was something different.

> [19:41:07] Global event: Spatial instability index increased to 0.7 (threshold: 1.0). Contributing factors: 14 active users, 3 unresolved zone collapses, 1 Core Fragment removed from sublevel architecture. > [19:41:07] System note: Core Fragment removal by User KJW-001 has weakened structural integrity of Sublevel-7 transit hub. Adjacent sublevels may experience bleed-through. > [19:41:08] Projected next merge: Seoul Metropolitan Area. Zone difficulty: D (increased from E due to instability).

Fourteen active users.

Jae-won's hands went still on the keyboard. He read the number again. Fourteen. He wasn't the only one. There were thirteen other people—in Seoul, presumably, or at least in the metropolitan area—who had the same system, the same stats, the same countdown timer ticking in the backs of their minds.

And three unresolved zone collapses. His collapse in the transit hub was one of them. Had other users caused the other two? Or had they happened naturally—symptoms of a system that was, as the log stated, becoming increasingly unstable?

He opened a new note.

> BUG REPORT #003 > Product: System Override v0.1 > Severity: Critical > Reporter: Kim Jae-won (User, Level 1) > > Summary: System supports multiple concurrent users (at least 14). No user communication channel exists. No indication of user locations or identities. In a system with permanent death, the inability to coordinate with other users is a critical design flaw. > > Expected Behavior: Multi-user system should provide basic communication or awareness features. > > Actual Behavior: Users are completely isolated. No party system, no global chat, no map markers. > > Notes: The absence of communication features may be intentional (competitive design) or an omission (v0.1 incomplete feature set). The system's spatial instability is affected by user actions (e.g., Core Fragment removal). Without coordination, users may inadvertently increase global danger through independent actions. > > Also concerning: zone difficulty for next merge has been upgraded from E to D. My actions directly contributed to this escalation. > > Priority: P0 > Status: Open

He saved the note and sat back. The office was silent except for the hum of his monitor and the distant drone of the building's ventilation. In three hours and forty-seven minutes, reality would fold again. The subway—or wherever the system decided to anchor—would merge with another sublevel, and this time it would be harder. Difficulty D instead of E. Because he'd taken the Core Fragment. Because he'd collapsed a ceiling.

Every action had consequences. Every exploit had side effects. He knew this. It was the first rule of QA: poking at systems changes them.

He needed a plan.

Step one: Class selection. The system had promised it upon the next activation, and classes in any RPG defined the trajectory of a character's growth. He needed to choose intelligently, which meant understanding his options before the timer hit zero.

He activated [Analyze] on the class selection notification, focusing on the deferred reward.

> ANALYSIS: Class Selection (Pending) > Available upon next System activation. > Selection criteria: Based on user's demonstrated aptitudes, stat distribution, and actions during tutorial. > User KJW-001 profile: High INT, moderate WIS/DEX, action history emphasizes observation, analysis, environmental exploitation, and minimal direct combat. > Projected class options: [Insufficient debug access to preview. Raise Debug Access to Level 3 for class tree visibility.]

Debug level insufficient. He needed Level 3 to see his options in advance, and he was at Level 1. The Core Fragment had granted the access, but leveling it up presumably required either more fragments or some other progression mechanism.

Step two: Prepare for Difficulty D. He'd barely survived Difficulty E with improvisation and a thrown laptop. He didn't have a laptop anymore. His combat stats were mediocre. His only offensive option was the half-eaten energy bar in his bag, which restored HP but did not, as far as he knew, deal damage.

He needed equipment. The system recognized his real-world items—the laptop had been catalogued as an improvised weapon with blunt damage. What other real-world objects might have system-relevant properties?

He activated [Analyze] on objects around his desk. His monitor: "No combat value. Too heavy to wield effectively." His keyboard: "Improvised weapon. DMG: 1-3. Fragile." His stapler: "Improvised weapon. DMG: 1-2. Blunt. Ammunition: 127 staples (Piercing DMG: 0-1 each)." His coffee mug: "Improvised weapon. DMG: 2-4. Fragile. Breaks on impact."

Nothing useful. The system categorized everyday objects as improvised weapons with terrible stats because they were, in fact, terrible weapons. He needed something purpose-built.

But where did you buy weapons in Seoul at 8 PM on a Wednesday?

The answer, as it turned out, was the internet.

Jae-won opened his phone and searched for "self-defense equipment Korea." The results were a mix of pepper spray listings—legal for self-defense but probably useless against digital aberrations—and sporting goods. Baseball bats. Hiking poles. Tactical flashlights.

He activated [Analyze] on images of the products, testing whether the skill worked on photographs. It did, partially.

> ANALYSIS: Aluminum Baseball Bat (Image) > Projected System Classification: Weapon (Blunt, Two-Handed) > Estimated DMG: 12-18 > Weight: 0.9 kg > Durability: High > Note: Analysis from image only. Actual stats may vary. Physical inspection recommended.

Twelve to eighteen damage. Against a Glitch Crawler with 30 HP and a DEF of 3, that meant 9-15 effective damage per hit—two to three hits to kill. Against the underside vulnerability at DEF 1, even better. That was workable.

He ordered the bat for express morning delivery. Then, on impulse, he ordered a tactical flashlight ("Projected: Utility item. Illumination: 1200 lumens. May disorient light-sensitive enemies.") and a set of knee and elbow pads ("Projected: Armor (Light). DEF +1-2. Reduces fall damage.").

Total cost: 87,000 won. His bank account protested, but his survival instinct overruled it.

Step three: Understand the other users. Fourteen people in Seoul with system access. Were they all from the tutorial? Had they all gotten their own version of the transit hub? Were any of them also, right now, sitting in empty offices reading debug logs and ordering baseball bats online?

The system log had mentioned a spatial instability index of 0.7 out of 1.0. Three unresolved zone collapses. Fourteen active users. If the instability was tied to user actions, and users had no way to coordinate, then the system was essentially a tragedy of the commons: everyone acting in rational self-interest would collectively drive the instability toward 1.0, at which point... what? A larger merge? A permanent merge? System crash?

He didn't have enough data. He needed more debug access, which meant he needed to level up, which meant he needed to survive the next activation.

The timer read 03:12:08.

Jae-won packed his bag—empty now except for his phone, wallet, the half-eaten energy bar, and a newfound appreciation for the fragility of reality. He left the office, took the elevator down, and stepped out into the November night.

Pangyo at 9 PM was a ghost town of office buildings and convenience stores. The air was cold, carrying the particular crispness of late autumn in Korea, and the sky above the light pollution was the color of static. Jae-won walked to the nearest GS25, bought two more energy bars ("Consumable. Restores 5 HP each." — he checked with [Analyze]), a bottle of water ("Consumable. Removes Dehydration debuff."), and a roll of electrical tape ("Utility. Can be used for repairs, bindings, or marking.").

He took the subway home. Line 2 again, because avoiding it felt like cowardice, and because [Pattern Recognition] was picking up more merge residue than it had that morning. The hairline cracks in the tile at Sadang station were brighter. The system text that flickered across the LED display appeared more frequently—[NODE DETECTED], [SPATIAL INTEGRITY: 0.71], [USER PROXIMITY: 340m].

User proximity: 340 meters.

Jae-won froze, hand on the subway pole. Another user. Three hundred forty meters away. On the same train, or in the same station, or somewhere on the street above. Someone else with a stat panel and a countdown and a list of questions they couldn't answer.

He looked around the car. Rush hour was over, and the passengers were sparse: a woman in a business suit reading a tablet, a teenager with headphones and a school bag, a man in construction clothes sleeping with his head against the window. None of them showed the faint blue outline he'd noticed on the woman that morning. None of them had the look of someone who'd recently fought digital monsters in a subway tunnel.

But then, neither did he. He looked like a tired twenty-six-year-old in a cheap jacket, which was exactly what he was.

The proximity reading flickered and changed: 280m. Getting closer. The other user was moving, and their trajectory was converging with his.

A new entry appeared in his System Log:

> [21:14:33] Proximity alert: User KJW-001 within detection range of User LSR-004. Mutual detection possible at <100m with [Observe] Lv.2+ or [Analyze] Lv.2+.

LSR-004. Another user designation. He couldn't identify them at his current skill levels—he'd need [Observe] or [Analyze] at Level 2, and both were still at Level 1. But the fact that the system had flagged the proximity meant it was tracking user-to-user distances. Fourteen users in a metropolitan area of twenty-five million people, and the system had noticed when two of them came within a few hundred meters.

That felt intentional.

The train arrived at Gwanak. Jae-won stepped off, watching the proximity counter. 310m. Moving away now. The other user hadn't gotten off at his stop.

He walked home through the quiet residential streets, past fried chicken shops and karaoke rooms leaking light and noise into the darkness. His apartment building was a squat concrete tower that had been new in the 1990s and had aged the way most Korean apartment buildings aged—with a kind of pragmatic indifference, neither beautiful nor ugly, merely persistent.

He climbed four flights of stairs because the elevator made sounds that he was now too attuned to ambient noise to ignore. His apartment was the same one-room box it had been that morning: a desk, a bed, a kitchenette, a bathroom barely large enough to turn around in. He locked the door, set the energy bars on the desk, and sat on his bed.

The timer read 02:44:51.

He should sleep. The debug log had noted that sleep deprivation reduced his HP regeneration by twenty percent. But sleep felt impossible. The countdown was too present, too physical—a vibration in his bones that intensified as the number decreased.

He opened the notes app and started a new document. Not a bug report this time, but a design document—the kind he'd write at work when documenting a system's behavior for new QA hires.

> SYSTEM OVERRIDE v0.1 — BEHAVIORAL ANALYSIS (DRAFT) > Author: Kim Jae-won > > 1. CORE MECHANICS > - Stat-based progression system (STR, DEX, INT, WIS, CON, CHA) > - Stats generated from biometric/cognitive assessment of real-world user > - Action-based skill acquisition (no preset skill trees) > - Loot/rewards tied to zone completion and bonus objectives > - Permanent death (unconfirmed for real-world body; confirmed for system status) > > 2. WORLD STRUCTURE > - Reality merges with 'sublevels' on a timed cycle (currently 24 hours) > - Merge creates temporary zones overlaid on real-world locations > - Zones have difficulty ratings (E, D, C, B, A, S?) > - User actions affect zone stability and subsequent merge difficulty > - 'Merge residue' persists after zone collapse, visible with Pattern Recognition > > 3. USER ECOSYSTEM > - Minimum 14 active users (possibly more; debug access may not show all) > - Users are unaware of each other (no communication features) > - System tracks user proximity but does not facilitate contact > - Each user has a unique designation (format: [XXX]-[NNN]) > > 4. PROGRESSION PATH > - Level 0 → 1 achieved via tutorial completion > - Class selection unlocked at Level 1 (pending next activation) > - Debug Access appears to be unique reward (or very rare) > - Core Fragment grants permanent stat boost + unique skill tree > > 5. OPEN QUESTIONS > - What is the system's purpose? > - Who are the other users? > - What happens at spatial instability index 1.0? > - Is there a way to communicate with other users? > - What is the end state? Does the system have a win condition? > - If I die in-system, do I die in reality? > > 6. WORKING HYPOTHESIS > The system is not a game. Games are designed for entertainment, with difficulty curves that accommodate user growth. This system escalates difficulty based on user actions, punishes exploration with increased instability, and provides no tutorial beyond 'don't die.' This is either: > (a) A test — measuring user adaptability under extreme conditions > (b) A draft — an incomplete system still under active development (v0.1 supports this) > (c) A parasite — a system overlaying reality for its own purposes, using humans as processing nodes > > My QA instinct says (b). The version number, the debug access, the system logs — these are development artifacts. Someone is building this, and they left the tools in the build. > > I intend to use those tools.

He saved the document. The timer read 01:58:33.

Jae-won lay back on his bed and stared at the ceiling. The HP regeneration penalty for sleep deprivation was real, and he could feel it—a subtle sluggishness in his limbs, a fog at the edges of his enhanced perception. He needed to rest, even if real sleep was impossible.

He closed his eyes. Not to sleep, but to think. To let [Pattern Recognition] process everything he'd learned today, building connections in the background like a search algorithm indexing a new dataset.

The system had called him "not what it expected." It had flagged him for "advanced class compatibility assessment." His performance metrics exceeded the baseline by 340%. He was, by the system's own measures, an outlier—a user who treated the apocalyptic overlay on reality not as a crisis to survive but as a codebase to audit.

Maybe that was the exploit. Not a glitch in the combat mechanics or a loophole in the zone layout, but a fundamental misalignment between what the system expected its users to be and what Jae-won actually was. The system expected fighters, survivors, heroes—people who would swing swords and dodge monsters and follow the progression path as designed.

It had gotten a QA tester. Someone whose entire professional existence was built around the assumption that systems had bugs, that rules had exceptions, and that the most important feature of any program was the one the developers didn't know about.

His phone buzzed. A Slack message from Sera.

@yoon_sera: Hey. I know it's late. But I looked into that function I told you about at lunch—the social graph collector in the Chronofall social module. I pulled it up again tonight. It's been updated. Someone pushed changes to it three days ago. The function is no longer collecting player communication metadata.

A pause. Then:

@yoon_sera: It's collecting player location data. GPS coordinates. In real time.

Jae-won sat up. The drowsiness evaporated. He stared at the message, read it twice, and felt [Pattern Recognition] fire like a silent alarm.

Chronofall Online. A game made by Nexion Interactive. A game that was hemorrhaging players and running on spaghetti code. A game that had a hidden function collecting real-time GPS data from its remaining playerbase.

Fourteen active System Override users in Seoul.

An unknown number of Chronofall Online players with GPS tracking enabled without their knowledge.

Jae-won typed a reply with steady hands.

@kim_jaewon: Don't touch that function. Don't tell anyone else about it. Can you get me a copy of the code and the commit history?

@yoon_sera: Why?

@kim_jaewon: I think it might be connected to something bigger.

@yoon_sera: Connected to what?

He hesitated. The cursor blinked. The timer in the back of his mind ticked down: 01:42:17. In one hour and forty-two minutes, reality would fold again, and he'd be fighting creatures in a dimension that shouldn't exist, armed with energy bars and electrical tape.

@kim_jaewon: I don't know yet. But I intend to find out.

He set the phone down. Then he picked it up again and added one more entry to his bug report file.

> BUG REPORT #004 > Product: System Override v0.1 / Chronofall Online (possible cross-contamination) > Severity: Critical > Reporter: Kim Jae-won (User, Level 1) > > Summary: Hidden GPS tracking function in Chronofall Online codebase may be related to System Override user detection/targeting. Correlation between game studio product and reality-altering system is unexplained and deeply concerning. > > Steps to Reproduce: > 1. Be a QA tester at the game studio that may or may not be connected to an interdimensional system. > 2. Have a colleague who actually reads legacy code. > > Expected Behavior: Game studio makes bad games. Reality remains real. > > Actual Behavior: Game studio may be a front for, or connected to, the infrastructure of a system that is rewriting the rules of existence. > > Notes: This could be coincidence. Chronofall has 200,000+ active players. GPS tracking could be mundane (analytics, advertising). But the timing—system activation coinciding with recent code changes—warrants investigation. > > If this is what I think it is, then the answer to 'Who built System Override?' might be sitting two floors above my desk. > > Priority: P0 > Status: Open — Investigating

The timer ticked.

01:38:44.

Jae-won got up, checked his bag—energy bars, water, electrical tape, phone—and laced his shoes. The baseball bat wouldn't arrive until morning. He'd have to face whatever came next with what he had.

But he had something better than a weapon. He had a thread. A connection between the system that was eating reality and the failing game studio where he spent his days. A seam in the architecture where two systems met, imperfect and exploitable.

He was a QA tester. Finding seams was what he did.

The countdown continued. The night pressed against his window. And somewhere in Seoul, thirteen other users waited for the same moment, each of them alone, each of them unaware that the answers they were looking for might be buried in the spaghetti code of a game that nobody played anymore.

Jae-won sat on the floor of his apartment, back against the wall, and watched the timer count down to the next merge. He did not close his eyes. He did not sleep.

He planned.