Cherreads

Chapter 2 - World Error

The whispered question, so full of digital sorrow, sent a shiver through my coded form. "Why… why did you abandon us, Architect?"

Abandon them? I'd poured my lifeblood into creating Elysium. I'd died trying to launch it. The accusation, even from a disembodied, glitching voice, stung.

"I didn't abandon anyone," I projected back, my thoughts infused with a defensive edge. "I died. And frankly, this isn't the Elysium I built."

Silence answered, a heavy, crackling void that felt more like a disconnected line than a thoughtful pause. Whoever, or whatever, had spoken was either gone or incapable of further communication.

Who was that? An NPC? A fragment of the original system AI? The possibilities were unsettling. If entities within this broken world retained that level of awareness, what did that mean for the "System Integrity Restoration" I was supposedly here to perform? Was I fixing a machine, or was I operating on something that had developed a soul, however fractured?

Pushing the disquieting thought aside for now – I had more immediate problems – I turned my attention back to the wider environment. The single flickering street fragment was just one pixel in a catastrophically corrupted image. I needed a bigger picture.

Analyze(Environment_Sector), I commanded, targeting the immediate vicinity.

The UI before me flickered, and then a flood of data began to stream in. It wasn't just text this time; a rudimentary 3D map of the surrounding area began to render, overlaid with pulsating icons and color-coded warnings. Red, naturally, was the dominant color.

ANALYSIS: SECTOR_GLITCHWASTE_073 (Local Area)

Dominant Anomaly: Cascading Data Degradation.

Structural Integrity: 12% (Average)

Temporal Stability: Fluctuating (-3.5 to +1.2 seconds variance, localized).

NPC Population: 37 detected.

* Status: 91% Critical Loop/Error State.

* Status: 8% Dormant (Unresponsive).

* Status: 1% Unknown (Erratic Data Signature).

Quest Nodes: 4 detected.

* Status: 100% Corrupted (Unresolvable Logic Paths).

Dungeon Entrances: 1 detected (The Whispering Catacombs – Entry Point Sealed by Data Collapse).

Threat Level: Moderate (Environmental Hazards, Unstable Code Manifestations).

My non-existent heart sank. Temporal Stability Fluctuating? That meant time itself was stuttering here. NPCs caught in loops, quests broken beyond repair, dungeons sealed off by pure data collapse. This wasn't just a few bugs; this was systemic organ failure. The "Glitch Wastes," as the system seemed to have designated this starting zone, was an apt name. It was a digital graveyard.

I focused on one of the NPC icons blinking insistently on the map. It was relatively close. Might as well see the "Critical Loop/Error State" firsthand.

Moving in this new form was strange. I didn't walk; I willed myself forward, and my coded body seemed to flow, or perhaps teleport short distances, across the broken terrain. I phased through a half-rendered wall that shimmered with "missing texture" purple, the sensation like passing through cold static.

Ahead, I saw him. An NPC I vaguely recognized: Old Man Hemlock, the starting village's herbalist. Or what was left of him. He was stuck mid-stride, one leg raised, his character model flickering like a bad hologram. His dialogue box was open above his head, but the text within was a garbled mess of alphanumeric characters and wingdings.

"Greetings, traveler! Have you ##Error_Item_Not_Found## for my famous ##Potion_Corrupt_ID##? It'll cure what ails ya, or my name isn't HН€ŁŁ███ķ!" He'd repeat the line, then his model would twitch, reset, and repeat it again. And again. A perfect, agonizing loop.

This was one of my creations. A simple, kindly NPC designed to give out beginner quests and sell basic healing potions. Now, he was a digital prisoner, his mind a broken record.

A surge of something cold and determined solidified within me. This wasn't just about salvaging my work anymore. This was about these… beings. Trapped. Suffering, in their own coded way.

"Alright, Hemlock," I thought, approaching his glitching form. "Let's see if I can at least quiet you down."

I focused on him, my internal "dev console" flaring to life. Query(NPC_Hemlock_001).

The data was, as expected, a catastrophe. His behavior tree was a tangled knot of broken references and null pointers. His inventory was full of ITEM_ID_CORRUPT.

Okay, start small. Can I just… stop the dialogue loop?

I mentally scrolled through the functions I could see within his code. There was a PlayDialogue() function, currently stuck in an infinite retry.

Patch(NPC_Hemlock_001, SetParameter: PlayDialogue.Enabled = False), I commanded. This was a basic override. I wasn't fixing the root cause, just slapping a digital band-aid on a gaping wound.

A small jolt, like a tiny spark of static electricity, coursed through my form. The UI flickered a warning:

SYSTEM ALERT:

Action: Patch() executed.

System Stability Cost: -0.01% (Minor)

Corruption Risk Incurred: Low.

Note: Repeated or complex modifications will increase cost and risk.

So, there was a price. Every intervention, no matter how small, chipped away at some ephemeral "System Stability" and incurred a "Corruption Risk." What that risk entailed, I wasn't keen to find out just yet.

But it worked. Old Man Hemlock's dialogue box vanished. He still stood there, mid-stride, flickering, but the maddening loop of garbled text was gone. A small victory, but a victory nonetheless. He was still broken, but at least he was silent.

I felt a flicker of satisfaction, quickly dampened by the sheer scale of the problem. Silencing one NPC was like trying to bail out a sinking supertanker with a teaspoon.

My attention was drawn to another blinking icon on my internal map – one of the corrupted Quest Nodes. It was located in what used to be the village square, near the dilapidated well I'd coded in for ambiance.

As I moved towards it, the environment grew more unstable. Chunks of terrain would suddenly de-rez, leaving gaping holes into the grey void below, only to snap back into existence moments later, sometimes with entirely different textures. A tree flickered between a healthy oak, a charred husk, and a crystalline structure that pulsed with an unhealthy purple light.

The Quest Node itself was a disaster. It was supposed to be a simple glowing exclamation mark above a community notice board. Instead, the notice board was on fire with glitched, rainbow-colored flames that gave off no heat, and the exclamation mark was spinning erratically, morphing into question marks, skulls, and occasionally, the universal "crash" symbol.

Query(QuestNode_Village_Main_001).

The data was even worse than Hemlock's.

QUERY RESULT: QuestNode_Village_Main_001

Original Quest Chain: "Clearing the Rat Infestation"

Current Status: Critical Logic Cascade.

* Objective: ##ERROR: Target_NPC_Mayor_MIA##

* Reward: ##ERROR: ItemTable_Corrupt_Reference##

* Trigger Condition: Interacting with ##ERROR: Object_ID_NullPointer##

Associated Entities: 17 Glitch_Rats (Spawned, Aggro Table Corrupted – Attacking Terrain/Self).

Glitch_Rats attacking the terrain and themselves. Lovely. The game was literally eating itself.

As if summoned by my observation, a section of the ground nearby distorted, pixels swirling like water down a drain. Then, with a sound like a corrupted .wav file screeching, a creature clawed its way out.

It was vaguely rat-like, but far too large, its fur a shifting mosaic of mismatched textures. One eye was a piercing red LED, the other a void-black socket. Its limbs twitched erratically, and it gnashed teeth that looked like broken shards of glass. A "Glitch_Rat," no doubt.

It spotted me. Or, at least, its single red eye fixed on my coded form. A garbled screech, like a modem trying to sing opera, tore from its throat.

It wasn't attacking the terrain. It was charging straight at me.

My newly acquired admin privileges, my understanding of the code – none of it had prepared me for the primal, instinctual jolt of seeing a hostile entity, however bugged, bearing down on me.

For a split second, the old Kael, the one who flinched at sudden noises in the server room, resurfaced. Then, the Architect, the System Core, took over.

This thing is just broken code, I told myself. And I rewrite code.

But as the Glitch_Rat lunged, its glitched claws aimed at my core, a new, far more urgent thought screamed through my consciousness: How do I fight back when I don't even have a physical attack?

More Chapters