Zhang Wei pushed his desk against the door, then the filing cabinet, then the mini-fridge. Layered obstacles. Every game designer knew this: you did not build one tall wall—you built chokepoints that forced pathfinding retries. The creature in the hallway had to burn through geometry.
He stepped back. The barricade bought maybe forty seconds. Not a plan. A delay of execution.
The clawing had changed. Testing scratches had become purposeful strikes. The hollow-core door groaned. Through the thin wood, the wet breathing multiplied—one set of lungs had become two.
He looked at the patch notes still floating in his vision. Blue window, white text. He had been scrolling through them when the scratching intensified—three thousand lines of documentation formatted exactly like a software release. He had gotten to line 1,247 before the breathing changed.
The door cracked. The top hinge buckled outward. Through the widening gap, an orb of grey-white tissue where an eye should have been, pulsing, no pupil, no iris. It focused on him with the certainty of a targeting reticle.
Code Sight pulsed, red text sharpening from question marks into data:
ENTITY DETECTED: Grey Crawler HP: 45/45 LEVEL: 2 STR: 12 | DEX: 14 | CON: 10 TYPE: Hostile — Vermin Class DAMAGE RANGE: 8-14 per strike
Level 2. STR 12 against his 8. DEX 14 against his 10. It hit for 8-14 against his 90 HP. Six to eleven hits to die. The math was not complicated.
The second claw came through the gap and pulled. The door split down the middle. The filing cabinet tipped sideways, drawers spilling open. The creature squeezed through—hunched, quadrupedal, the size of a large dog but wrong in every proportion. Limbs bent backward at the knee. Skin the color of wet concrete. A ridge of bone ran from skull to spine where a mouth should have been.
It lunged. Zhang Wei grabbed his five-kilogram dumbbell—the only exercise equipment he owned—and threw it.
Not aimed. Reflexive. The weight clipped the creature's shoulder mid-leap.
-4
Four damage. Out of forty-five. Less than ten percent with a lucky hit, and now the creature was on his floor, scrambling for traction, orienting toward him.
He grabbed the fire extinguisher from the kitchenette wall. Red cylinder, two kilograms, Class B rated. The nozzle pointed forward. He squeezed the trigger.
White chemical spray hit the creature face-first. It shrieked—a grinding sound that vibrated in his molars—and recoiled. Code Sight updated: -2. Chemical irritant, temporary. Two damage. But the creature was blind now. It thrashed sideways, claws scraping his desk, and his right monitor—the one displaying the behavior tree—tipped off the edge and shattered on the floor.
Zhang Wei stepped forward and swung the extinguisher's steel base at the bone ridge on the creature's skull.
-11
It staggered. He hit it again. The ridge cracked.
-13
The creature's front legs gave out. It collapsed sideways, limbs twitching. The breathing—too-fast, double-rhythmed—slowed, gurgled, stopped.
Grey Crawler killed. XP gained: 25. Level Up! You are now Level 2.
The notification appeared in gold text. A chime sounded—not from any device, but directly in his hearing, injected into his auditory nerve like a private broadcast. A new window opened beneath it:
LEVEL 2 — STAT ALLOCATION +2 Stat Points available. Distribute points? (Yes/No)
He stared at the numbers. Two points. In any RPG, this was the build-defining choice. STR for fighting. DEX for speed. CON for survival.
He put one point in CON and one in DEX. Not because he wanted to fight. Because he wanted to survive long enough to understand.
STR: 8 | DEX: 11 | CON: 10 | INT: 16 | WIS: 14 | CHA: 11 HP: 100/100
Ten more hit points. The difference between dying in six hits and seven.
His phone buzzed. Notifications flooded the screen—WeChat messages, news alerts, missed calls. He read the nearest one. Mr. Zhou from downstairs: WHAT IS HAPPENING THERE IS SOMETHING IN THE HALLWAY IT LOOKS LIKE A RODENT BUT HUGE
The Building 3B group chat—muted for three months—had erupted:
THE THING ATE OLD LIU SOMEONE CALL THE POLICE I locked my door but it is scratching
He scrolled social media. Twitter was a cascade of identical posts from different cities, different countries. Blue windows. Floating text. Monsters in the streets. People thought it was a coordinated hack. A viral campaign. Nobody was using the word apocalypse yet.
He put the phone down and returned to the patch notes.
The document resumed its clinical breakdown. Monster taxonomy—Vermin Class, Beast Class, Horror Class, and a fourth category listed only as [REDACTED], grayed out as if the System had censored its own documentation. Spawn mechanics. Drop tables. AI behavior templates described with finite-state-machine language: patrol, investigate, pursue, disengage.
One section read:
NEW CONTENT: Hostile Entity Spawns Behavioral templates deployed across all global regions. Spawn rates calibrated to initial player density. Hostile entities do not possess respawn mechanics during Alpha Phase—death is permanent for both players and entities.
Monsters could die. They were not invincible. They were test subjects, and spawn rates targeted high-density zones. His building. Hundreds of people in six stories. The System's algorithm had chosen them.
Below the monster section: ENVIRONMENTAL MODIFICATIONS.
Real-world technology continues to function during Alpha Phase but will experience progressive degradation in subsequent patches. Legacy technology support is not guaranteed beyond Beta Phase.
Legacy technology. His monitors. His rig. Fifteen years of game development compressed into proprietary tools. The System was telling him his entire professional toolkit had an expiration date.
He scrolled to the end. The final section was four lines. Small text, almost an afterthought—a footer most users would scroll past. He did not scroll past.
Known Issues: None. This is working as intended. Deployment Author: Automated — Test Framework v1.0 Next deployment scheduled in 30 days.
He read it twice.
Known Issues: None. Every software deployment had known issues. Bugs were inevitable—categorized by severity, documented with workarounds, fixed in the next release. Saying "None" was either a lie or a statement from a system that considered this correct behavior.
This is working as intended. Not "acceptable." Not "temporary." Working as intended. The System was operating within its design parameters.
Deployment Author: Automated — Test Framework v1.0. Not a person. A test framework. Tests had subjects. Tests had hypotheses. Tests had someone reviewing the results.
Next deployment scheduled in 30 days. Monthly patch cycle. Same cadence as every live-service game he had ever worked on.
The patch notes dissolved on their own, fading like smoke. His apartment was dark except for the one surviving monitor, still displaying his game engine. The Lich King's wireframe hand still clipped through the floor.
Someone had built this. Written the patch notes, designed the stat curves, chosen the monster templates. And they had made it look like a deployment document. Not a prophecy. Not a divine edict. A deployment document—which meant it had an author. Which meant it could be understood.
Zhang Wei opened a blank text file and began to type:
Hypothesis: This is a beta test. Patch notes follow internal documentation structure for a controlled software rollout. "Known Issues: None" suggests operation within expected parameters. 30-day deployment cycle matches live-service cadence. Automated author tag indicates iterative design—patches generated by the system itself based on performance data. Humanity is a test subject.
Below his window, blue light pulsed in the street. Another System event. Code Sight did not reach that far—not yet, not at Level 2.
His phone buzzed. A message from an unknown number:
I am in 5B. The thing broke my door. I locked myself in the bathroom. Is anyone alive out there?
He typed back: 3B. I am alive. Stay in the bathroom.
Then he went back to the text file and kept writing.