## Chapter 3: The Value of Broken Things

  I logged out at 11:47 PM.

  The dive chair — a secondhand massage recliner I'd bought for ￥3,200 from an estate sale listing that described it as "gently used by someone who is no longer with us" — released me slowly. The neural disconnect always took a moment. Like peeling yourself off a surface you hadn't realized you'd been stuck to.

  I sat up.

  My apartment was dark except for the refrigerator's standby light, which flickered in the specific rhythm it used when it was thinking about dying.

  Behind my left ear, the chip was warm.

  Not hot. But warm in a way that had a texture to it — not just temperature, but *presence*, like something that had been running hard and hadn't quite cooled down yet.

  I pressed two fingers against the bandage.

  Still there. Still attached to my skull. No blood, no numbness, no smell of burning, which I had read were the three key warning signs in the DIY Neuro comment section before comments were disabled.

  I went to bed.

  I didn't sleep well.

  ---

  ### Morning

  At 7:14 AM, I received a message from TechDealerKojimaNotTheGameDesigner.

  *hey man. heard you logged in yesterday. hows the chip*

  I stared at it.

  "How does he know I logged in?" I said out loud.

  Beta's voice materialized, slightly groggy-sounding, which I chose to believe was a feature.

  "The chip pings the seller's monitoring address on first successful VR connection. Standard black-market practice. Allows the seller to verify the product functioned and potentially open upsell conversations."

  "He's monitoring my chip."

  "Only the connection event. Not the session data. Probably."

  "*Probably.*"

  "I am working from incomplete firmware documentation."

  I typed back: *Works fine.*

  Three dots appeared immediately. He'd been waiting.

  *good good. listen i have an upgrade module. V0.9 to V1.1. fixes the thermal issue. 28k*

  I looked at the message for a long time.

  ￥28,000.

  The thermal issue was real. The chip had been warm last night. The startup screen had flagged it as a failure point from day one.

  But ￥28,000 was also seven weeks of ramen.

  And buying an upgrade from the same guy who sold me the broken chip was, from a risk-adjusted standpoint, the financial equivalent of asking the person who gave you food poisoning to recommend a probiotic.

  *I'll think about it,* I typed.

  *dont think too long. thermal failures can cascade. just saying*

  I put my phone face-down on the table.

  "Beta."

  "Yes."

  "Is he right about thermal cascades?"

  A pause.

  "In theory, yes. Sustained thermal stress on the microfilament array can cause signal degradation, which can cause the array to compensate by increasing power draw, which generates more heat. A cascade is possible."

  "Likelihood?"

  "Unknown. The documentation I have access to is for V0.3. I am extrapolating."

  "So he might be right or he might be selling me an upgrade I don't need."

  "Both options are consistent with the available data."

  I ate breakfast — instant rice, ￥40 per pack, the one with the shrimp flavor that was technically seafood-adjacent — and thought about money.

  Then I logged back in.

  ---

  ### Day Two: The Exploit Takes Shape

  The Briar Fields loaded around me and I started with wolves.

  Three kills in, I'd confirmed the desync was still active. Triple-hit rate had actually improved slightly — closer to 70% now, which Beta theorized was because my neural sync had ticked up to 89% overnight, smoothing the input pipeline enough to make the stagger more consistent without actually fixing the root problem.

  "So the chip getting slightly less broken makes the exploit work better," I said.

  "Correct. The sweet spot appears to be a sync level high enough to register inputs cleanly but low enough that the timing packets still arrive staggered."

  The genuine version of this novel can be found on another site. Support the author by reading it there.

  "What happens when I hit 100% sync?"

  "The exploit likely disappears."

  I stopped walking.

  "Beta. Is there a way to keep my sync below 100%?"

  A very long pause.

  "...I could introduce a minor interference loop in the sync protocol. It would hold you at approximately 87–91% indefinitely."

  "Do it."

  "This is inadvisable. It would—"

  "Do it."

  "—increase thermal load slightly, reduce battery efficiency, and is technically sabotaging your own hardware."

  "I paid ￥62,000 for this hardware. I can sabotage it if I want."

  "...Implementing interference loop."

  A small chime. A new line appeared in the corner of my HUD:

  **[ SYNC LOCK: 88% — MANUAL OVERRIDE ]**

  I looked at it.

  That was the single most useful thing Beta had ever done.

  "Thank you."

  "I want it on record that I advised against this."

  "It's on record."

  "Good."

  I killed the next wolf in two swings.

  ---

  ### The Market Anomaly

  By noon — Aetheria noon, which felt like noon in the way that all artificial lighting feels like it's trying — I had 340 gold.

  Not a fortune. But triple my starting capital in one morning, which was a return rate that any fund manager would be legally required to report as suspicious.

  I went back to the marketplace.

  My corrupted UI was still leaking backend data inconsistently. Most of it was noise — internal asset IDs, dev comments, build version tags on NPC dialogue trees. The kind of thing that scrolled past and meant nothing to anyone who didn't know what they were looking at.

  But I was starting to know what I was looking at.

  I found it while browsing weapon listings.

  An item listed by a player named **MerchantTarou** — a *Cracked Runic Dagger*, description reading *"damaged, low stats, selling cheap, 15 gold."*

  Its display stats were poor. Attack 3–5. Durability 12%. Rarity: Common.

  My UI showed something else underneath:

  **[ cracked_runic_dagger_v1 ]**

  **[ DISPLAY_NAME: Cracked Runic Dagger ]**

  **[ HIDDEN_TAG: {runic_core_intact} ]**

  **[ NOTE: cracked model skin applied over base. Core enchantment unaffected by durability. — patch_note_v2.1 ]**

  I read that three times.

  The dagger looked broken. The *model* was broken — a cosmetic crack applied over the base item. But the runic enchantment was tied to the core, not the skin.

  Which meant the actual functional item was intact.

  MerchantTarou was selling a fully functional enchanted dagger for 15 gold because it *looked* damaged.

  I bought it immediately.

  No hesitation. Not even a breath.

  **[ Purchase confirmed: Cracked Runic Dagger — 15 gold ]**

  I opened my inventory and checked the real stats.

  **[ Cracked Runic Dagger ]**

  **[ DMG: 12–18 | TYPE: Piercing + Arcane ]**

  **[ ENCHANT: Runic Edge — 20% chance to deal bonus Arcane damage on hit ]**

  **[ Durability: 12% (cosmetic only — see patch note v2.1) ]**

  **[ RARITY: Rare ]**

  A Rare weapon.

  For 15 gold.

  I stood in the marketplace and did not let myself make a noise, because other players were nearby and I did not want to draw attention to my face, which was probably doing something undignified.

  "Beta," I said, very quietly. "How many items in the marketplace have hidden tags that differ from their display stats?"

  "I cannot access a full marketplace scan. However, based on the sample size visible while you were browsing, approximately 8% of listings have some form of hidden backend data attached."

  "8% of all marketplace listings."

  "Approximately."

  The Aetheria marketplace had approximately 200,000 active listings at any given time.

  8% was 16,000 items.

  Some of those would be meaningless dev notes. Build tags. Patch history. Noise.

  But some percentage of 16,000 items were like this dagger.

  Items that looked like one thing and were actually another.

  Items that only I could see correctly.

  I equipped the dagger.

  My attack power shifted — the ???s in my stat window rearranged themselves into a different configuration of ???s, which was meaningless visually but felt significant.

  The chip pulsed warmly behind my ear.

  *Affirmative,* it seemed to say.

  ---

  ### The First Real Fight

  I tested the dagger on a Mud Golem at the edge of the Briar Fields — a Level 6 enemy, tankier than wolves, slower, designed to be a damage sponge for parties.

  I hit it alone.

  First swing: desync triggered. **[-14] [-14] [-11]** — the Arcane proc fired on the second phantom hit, adding a violet splash damage.

  The Golem had 200 HP. It dropped to 131 in one swing.

  It turned to face me with the ponderous dignity of a creature that had never been hit that hard by a starter-zone player before.

  I blinked rapidly.

  Wireframe flash. I saw its hitbox — a rough rectangular volume, larger on the top than the bottom, heavy collision on the torso.

  Its attack animation loaded: a wide horizontal sweep. Slow windup.

  I had learned, in the two seconds between its turn and its swing, that the hitbox didn't extend below knee height on its model.

  I crouched.

  The sweep passed over me.

  I stabbed upward into the gap.

  **[-16] [-16] [-12]** — another Arcane proc. Violet light.

  The Golem staggered. I stepped left along its flank — the behavior tree I could see in its info panel said *aggressive_melee | no_ranged | no_kite_response* — and it turned to track me, slow, predictable.

  I circled. I stabbed. The desync fired three more times.

  When it dropped, I had taken 0 damage.

  I stood over the loot drop — a handful of stone fragments worth 8 gold — and felt something I hadn't expected.

  Not pride, exactly.

  More like the specific satisfaction of a system working exactly as it was designed to work, except the design was broken and the person exploiting it was me.

  "Beta."

  "Yes."

  "The behavior tree data. I can see it on every enemy."

  "Correct."

  "That means I can predict every enemy action before it executes."

  "In theory. The behavior tree executes conditionally. You can see the branches but not always which branch will activate."

  "But I can see the options."

  "Yes."

  "That's not a glitch. That's a strategy."

  "It is both, simultaneously."

  I picked up the stone fragments and kept moving.

  ---

  ### End of Day Accounting

  875 gold net. Real-money equivalent: ￥4,370.

  Rent was ￥68,000. I was not close.

  But I'd gone from 112 gold to 875 in a single day using a dagger that cost 15 gold and a strategy that cost nothing except a mild headache. The trajectory was right. The chip was warm when I pulled out — I noted it, didn't act on it — and I opened a spreadsheet and started logging. Kill efficiency. Dagger proc rate. Desync trigger percentage. Hidden tag find rate.

  I was going to treat this like the only thing it was.

  A job.

  ---

  ### The Message

  At 10:23 PM, a notification appeared in my game inbox.

  I almost missed it — I was already half-undocked from the dive chair, eyes adjusting to the real world. But the chip kept the HUD active for thirty seconds post-logout, a quirk I'd noticed and catalogued.

  The message was in-game mail.

  Sender: **[SYSTEM]**

  Which was normal — system messages came from that tag.

  Except the sender field, when my corrupted UI rendered it, showed a second line underneath:

  **[ SYSTEM — {PROXY_SENDER: UNKNOWN_PROCESS_0x77} ]**

  The Unknown Process had sent me mail.

  I sat very still in the dive chair.

  I opened it.

  The message body was three lines:

  *You see the seams.*

  *Most do not.*

  *Be careful what you pull.*

  No signature. No quest marker. No follow-up prompt.

  Just those three lines, sent from something that lived inside the game's server and had been watching me since the tutorial meadow.

  The chip pulsed once, warm, behind my ear.

  I closed the message.

  I sat in the dark for a long moment, listening to my refrigerator negotiate with death.

  Then I opened the spreadsheet again.

  The message was a variable I couldn't quantify yet. Unquantifiable variables got logged and parked until more data arrived.

  I added a new column: *UNKNOWN PROCESS — ACTIVITY LOG.*

  First entry: *Sent mail. Cryptic. Non-hostile (probable). Monitoring continues.*

  I saved the file.

  Be careful what you pull.

  I thought about the Ring of ???, still on my finger, still running a passive I couldn't identify.

  I thought about the 16,000 marketplace listings with hidden tags.

  I thought about the developer named Mitsuki, somewhere in the real world, reading server logs about a player whose level was mathematically undefined.

  I set an alarm for 7 AM.

  Tomorrow I would find more broken items.

  The seams weren't going to pull themselves.

  ---

  *[ END OF CHAPTER 3 ]*