THE GLITCHED MONARCH

Chapter 2: The Malfunctioning Core



The damp chill of the cellar pressed against Leo’s skin, but it was nothing compared to the cold dread settling in his stomach.

"Julian," Leo rasped, staring at the heavy wooden door. The name felt heavy on his tongue, dragging up a messy web of inherited memories. Julian was the golden child, the recognized heir who had awakened a rare "Gale Core" at age fifteen. To Julian, Leo was an eyesore—a living, breathing reminder of their father’s past indiscretions, and a convenient punching bag to show off his superior strength.

Leo looked down at the hard, moldy heel of bread resting in the dirt.

*Eat it and survive another day as a dog, or change the rules of the game.*

The choice wasn't even a choice. Leo ignored the bread and focused entirely on the glowing blue status sheet hovering in his field of vision.

```

==================================

STATUS SHEET (LOCAL)

==================================

Name: Leo Vermis

Class: None (Unawakened)

Health: 12 / 45 [Warning: Hypothermia Imminent]

Mana: 0 / 100 [CRITICAL ERROR: Core Malfunction]

==================================

```

As a QA tester, Leo spent his days looking at things that were broken. When a game crashed, it was usually because two systems were trying to access the same memory address, or a calculation had divided by zero, or an asset was trying to load where it didn't belong.

His new body was a classic hardware conflict.

The human soul in this world was hardwired to connect to the "System Kernel" through a spiritual organ called a Mana Core. In normal humans, the core acted like a network gateway—taking in raw ambient energy (mana) and distributing it safely through the body’s meridians.

But Leo’s meridians were physically crushed, a birth defect that had never been healed. When his system attempted to run the standard initiation sequence, it detected the blocked pathing and threw a critical exception:

CRITICAL ERROR: Core Malfunction (Mana_Max = 0)

"Because the capacity is hard-locked at zero, the system shuts down any attempt to draw power to prevent my soul from imploding," Leo murmured, his fingers tracing the edges of the blue screen. "It's an automated safety protocol. But safety protocols are written by developers. And developers always leave backdoors."

Using a sequence he had memorized from years of testing beta builds, Leo swiped his finger diagonally down the left side of the screen, double-tapped the error code, and held his breath.

*Ping.*

```

[DEVELOPER SANDBOX MODE: ACTIVE]

[WARNING: System logs paused. Local memory edits will not be reported to the Main Frame.]

```

A secondary, deeply complex menu unfolded beneath the standard status sheet. It was filled with raw, cascading lines of green compiler code, variables, and memory address pointers.

Leo’s heart hammered against his ribs. He couldn't change his physical body's genetic makeup. He couldn't magically repair his shattered meridians. In the system's database, his Max_Mana attribute was stored in a read-only register locked by the world's laws.

"I can't change the hardware," Leo muttered, his eyes darting through the lines of code. "But I can trick the software."

He scrolled past the attributes, diving deep into the active status condition buffers. There, he found a list of active booleans—simple true/false switches that tracked his current physical state.

```

Local_Player.Status.is_bleeding = False

Local_Player.Status.is_poisoned = False

Local_Player.Status.is_freezing = True

Local_Player.Status.is_sleeping = False

```

Leo stared at is_sleeping = False.

In the standard game design of most RPGs, players recovered their resources at an accelerated rate when resting. In this world's system, when a human fell into a state of "Deepsleep," the system applied a massive passive multiplier to their mana recovery rate—typically x100—to allow the core to regenerate overnight.

If Leo could force the system to apply that multiplier while he was awake, what would happen?

He selected the variable. A small virtual keyboard flickered into existence. He deleted False and typed a single, world-altering word:

True

```

[System Event: State 'Deepsleep' spoofed successfully.]

[Mana Regen Multiplier: x100 Active.]

```

Leo braced himself.

Initially, nothing happened. The cellar remained dark, cold, and silent. He was still standing there, wide awake.

But then, deep within his chest, a spark ignited.

Because his maximum mana capacity was hard-locked at 0, his body should have registered no change. But the system's background compiler was now running an infinite loop: it saw that his current mana was below his "rest state" requirements, and applied the x100 multiplier to fill a cup that legally held nothing.

The math broke.

Current_Mana = (Current_Mana + (Regen_Rate * 100))

In a fraction of a second, his mana didn't just regenerate; it overflowed.

```

Mana: 100 / 0 (Overcharged)

Mana: 2,500 / 0 (Overcharged)

Mana: 18,000 / 0 (Overcharged)

```

"Oh," Leo gasped.

A sudden, overwhelming wave of heat exploded from his chest. The bitter, bone-deep chill of the cellar evaporated in an instant, replaced by a searing, euphoric warmth. Raw, visible blue energy began to seep from his pores, casting a brilliant, neon-sapphire glow across the damp stone walls.

The system was experiencing a massive, unmitigated buffer overflow. He had just turned himself into a walking, breathing nuclear reactor.

If you find any errors ( Ads popup, ads redirect, broken links, non-standard content, etc.. ), Please let us know < report chapter > so we can fix it as soon as possible.

Tip: You can use left, right, A and D keyboard keys to browse between chapters.