Global Apocalypse: My System Is Always AFK

They went back down that evening, just the two of them this time — Ethan and Suresh, no archaeology team, no Priya standing guard, just the two of them and a flashlight, because Ethan had decided he wasn’t asking this particular question with an audience.

The vault welcomed them the way it always did now, golden light rising gently to meet them the moment they stepped through the passage, the terminal’s dark bronze surface glowing steady and patient on its dais like it had been waiting all day for exactly this conversation.

Ethan sat down cross-legged in front of it, which felt a little undignified for what he was about to ask, but he was long past caring about dignity where any of this was concerned.

"Okay," he said. "I want a straight answer this time. Not fragments. Not fifteen archive entries I have to piece together myself. Where did my system actually come from. All of it. From the start."

[NOTICE: The system would like to note that it has been asking itself variations of this exact question for the better part of four months, and it is, frankly, relieved someone is finally putting it directly to the source instead of letting the system keep guessing.]

The terminal’s light pulsed once, gathering itself, and the plain, uneven text began resolving in the air above the dais — slower this time, more deliberate, like it understood the question deserved a real answer rather than another scattered fragment.

[QUERY RECEIVED: ORIGIN OF SUBUNIT "IDLE/AFK PROTOCOL."]

[RESPONSE COMPILING.]

[This architecture — the vault, the terminal, the buried city above and around it — was not built by any single Instance’s Framework. It predates the concept of "Instances" entirely. It is, according to the deepest layer of data the system can currently access, part of something called the Origin Engine: a governing structure responsible for seeding and maintaining apocalypse-style trial systems across a vast number of separate, parallel worlds.]

Ethan sat with that for a second. "So the whole apocalypse thing — the monsters, the gates, the leveling, all of it — that wasn’t invented by whatever’s running Earth. It’s a format. Something copied and deployed everywhere."

[Correct. Each world that receives one of these trial systems is designated an Instance. Earth is one Instance among what the terminal’s records suggest is an extremely large number — the exact figure is not specified, but the language used to describe it does not read as small.]

"And Arjun’s world was one of those too."

[Arjun Mehra’s Instance was, according to available records, the first fully documented case of an idle-type user achieving what the Origin Engine classifies as "unresolvable combat power" — the same designation currently attached to the subject’s own stat sheet. When his Instance’s trial concluded, rather than assign him to lead the surviving governing structure, as was apparently standard procedure at the time, he refused. Repeatedly. Permanently.]

Suresh, sitting quietly a short distance away, spoke up for the first time since they’d entered. "And that refusal is why all this exists. The guardians. The city. The empty seat."

[The system believes so, yes. When a user refuses the seat the Origin Engine intends for them, the Engine does not simply move on. It appears, based on everything gathered so far, to construct an entire holding architecture around that user’s own preferences instead — a compromise, of sorts, built to keep the option open indefinitely rather than force the issue. Guardians to protect what he actually cared about. A home built to his own specifications. And, eventually, a dormant search function, left running for centuries, waiting for someone else to arrive who might be willing to say yes where he said no.]

Ethan felt something uncomfortable settle in his chest at that. "So this whole city — the market, the guardians, the house rules carved into the wall — none of that was really a monument to him. It was the Engine’s way of not taking no for an answer. It just built around him instead of overriding him."

[That is a fair interpretation of the available evidence, yes.]

"And now it’s doing the same thing to me."

[The system believes that is likely, yes.]

Ethan sat with that for a long moment, staring at the terminal’s steady gold glow, at the empty space around the dais where — presumably, eventually — some version of a throne was meant to take shape.

"Okay," he said finally. "So my system. Specifically. How did a piece of this — whatever this actually is — end up assigned to me, on Earth, the exact same day the apocalypse started here?"

[RESPONSE COMPILING.]

[The terminal’s records indicate that when an Instance’s trial concludes without a willing successor, the Origin Engine does not discard the associated system architecture. It archives it — flags it for redeployment, pending review, to be assigned to a future Instance under stricter oversight, specifically to avoid producing another "unresolvable" case.]

[The Framework’s own Administrators confirmed, weeks ago, that the Idle/AFK Protocol currently assigned to the subject was flagged for removal seventy-two hours before Earth’s activation — a distribution error allowing one instance to slip through before deletion completed.]

[The system now believes it understands what that "removal" actually meant. It was not being deleted for being broken. It was being pulled back out of general distribution because it was Arjun Mehra’s own archived system — the exact architecture that had already produced one unresolvable user once before, being flagged, correctly, as too dangerous to risk redeploying a second time.]

[The seventy-two-hour shipping error the Administrators described so casually was not a minor scheduling mistake. It was the single moment the Origin Engine’s own safeguard against repeating this exact situation failed.]

Ethan let out a slow, disbelieving breath. "So I didn’t get a broken system by accident. I got his system. On purpose, almost — except it wasn’t supposed to happen at all, and nobody caught it in time."

[That appears to be precisely what happened, yes.]

The room was quiet for a long moment after that, the terminal’s gold light settling into a steady, patient glow, as if it, too, understood the weight of what had just been confirmed.

"That explains a lot, actually," Ethan said eventually, quieter now. "Why it never leveled me the normal way. Why it kept giving up on ranking me. Why the sword recognized his mark. It was never really new tech assigned to some random guy who got lucky. It was the same thing that already happened once, just — replayed, somewhere it was never supposed to land."

[The system believes that is an accurate summary.]

Suresh, who had been listening quietly through all of it, finally spoke again, his voice careful. "So what does that mean for you? Practically. Does the Engine expect you to finish what he started? Take the seat he refused?"

Ethan didn’t answer right away. He looked at the empty space around the dais, at the faint outline in the stone where something like a throne would eventually, presumably, need to go, and felt the same flat, immediate refusal rise in him that had carried him through every recruitment offer since the very first week of this apocalypse.

"No," he said finally. "I already told the Framework’s Administrators no. I’m not telling this thing anything different just because it’s older and has a nicer basement."

[NOTICE: The system logs this refusal, consistent with prior statements.]

[The system would, however, like to raise something it has been holding back for the last several minutes of this conversation — a final line of the terminal’s response that only just finished compiling.]

Ethan glanced up. "What."

[The terminal has confirmed that the off-world signal detected during synchronization is not a passive echo, as originally assumed. It has been actively responding — not to the terminal, but specifically to the subject’s own presence, growing stronger each time he interacts with this architecture.]

[It has just, moments ago, stabilized into something the system can finally read clearly for the first time.]

[It is not a location. It is not a message.]

[It is a countdown.]

Ethan felt the Void Sword shift faintly against his shoulder, humming low and wary, the same reaction it always gave right before something new decided to introduce itself.

"A countdown to what," he said.

The terminal’s light flickered once, and above the dais, a single new line of text finally resolved, plain and unadorned, the same handwriting style as everything else in this ancient, patient archive.

[UNKNOWN. THE SYSTEM ESTIMATES COMPLETION IN APPROXIMATELY SEVENTY-TWO HOURS.]

Visit and read more novel to help us update chapter quickly. Thank you so much!