https://novelcool.info/chapter/Chapter-64-The-Garlic-Wuxia-Saga-Part-11-/13511087/
Chapter 63: Garlic Wushuang Saga (Part 10)
Chapter 63: Garlic Wushuang Saga (Part 10)
“Trouble…” Pan Feng muttered under his breath.
“Did he hear us?” Hua Xiong whispered.
Feng Bu Jue folded his arms. “I’m standing just a few meters away. What’s the point of whispering?”
Pan Feng scratched his head. “Yeah, well—”
Feng Bu Jue cut him off. “Before you start spinning excuses, let me say this: I don’t think you’re cheating players. You’re clearly Dream Corporation staff. Whether you’re Gms or not, your work here isn’t something that should go public. So here’s the deal—tell us the truth, and we’ll cooperate. We’ll even keep our mouths shut after the scenario ends. But if you don’t…” He paused, letting the threat hang. “I might feel compelled to write a little serialized exposé—dramatic, embellished, split into a dozen chapters—for every forum under the sun.”
“Wait, hold on—” Hua Xiong raised a hand. “Let us talk this over.”
“So… the system uses this data to generate a scenario,” Feng Bu Jue said. “It transforms derivative beings from code into tangible monsters. Your job is to kill or defeat them, stripping them of resistance or escape capabilities. Then the system can eliminate them entirely when cleaning up the scenario.”
“That’s exactly it,” Hua Xiong said. He picked up a cup and a jar of sugar cubes. “This cup represents the scenario’s shell. You players are like these sugar cubes.” He gestured toward the cup. “When you queue for a scenario, you hear the system prompt: Team size random value generated: six players.” He tossed some coffee powder into the cup. “At that point, the data is already injected into the shell. But during this phase, it’s still just basic elements—air, water, terrain, dirt, and so on.” He picked up six sugar cubes. “Then, the six of you—players entering the scenario—arrive at its entrance. You each hear the message: Your team has entered the queue. Searching for other ready players or teams. At that moment…” He dropped two sugar cubes. “Two players are replaced by me and Brother Pan. Those two will immediately be reassigned to another waiting scenario, and they won’t even notice the change.”
Pan Feng added, “We Gms usually work in pairs on standby. Once derivative being code is locked into an upcoming scenario, we insert ourselves into the queue. The players we replace are typically either a duo queuing together or two solo players. They won’t be grouped with anyone who successfully enters the scenario.”
“What if there’s a five-player team or a full six-player squad?” Xiao Tan interjected.
“For a five-player team, we can only replace the solo player, sending in one GM. As for a six-player squad, we can’t interfere at all. They’ll have to face the derivative being themselves. But since launch, no six-player squad has ever encountered a derivative being.”
“Besides,” Pan Feng continued, “the system’s ‘captured’ data volume is only enough to generate six-player team survival scenarios. So you don’t need to worry about encountering derivative beings in two-to-five-player scenarios or other modes.”
“Wait, doesn’t that make six-player team scenarios super dangerous?” Xiao Tan exclaimed.
“Do you think there are that many derivative beings?” Pan Feng chuckled. “The probability of such uncontrolled system data appearing is nearly one in a billion. During internal testing, two server groups—Sleep Mode and Non-Sleep Mode—ran continuously for thirty days and only generated derivative beings ten times total.”
“In short,” Hua Xiong said, tossing the remaining sugar cubes into the cup and pouring hot water from a coffee machine, “when you hear Scenario generating… all those elements will randomly form a normal scenario—plot, world-building, everything—based on your level, combat strength, skill proficiencies, past performance, etc. Meanwhile, the derivative being merges with some data element and materializes.”
Feng Bu Jue frowned. “So… how strong are these derivative beings exactly?”
“Ha ha…” Pan Feng laughed. “You’ve seen our strength firsthand, haven’t you?”
“I noticed,” Feng Bu Jue replied.
“Now you know why we always work in pairs to handle them.”
“You mean one GM could get killed?” Feng Bu Jue asked.
“Exactly,” Pan Feng said. “Don’t be fooled by our displayed level thirteen. We use GM accounts with actual combat power about ten levels higher. Even so, we’re not invincible. Take that boss earlier—it escaped by jumping off the building. We couldn’t follow. If we jumped, we’d die just like players.”
Xiao Tan asked, “Then why doesn’t your company boost the admin characters’ power? Like making them look level thirteen but actually have fifty-level strength?”
Hua Xiong raised the coffee cup. “Can you fit two watermelons into this cup that holds two sugar cubes?”
“Oh…” Xiao Tan nodded, finally understanding.
“Our accounts don’t level up. We’re specialized for levels five to ten. Other level ranges have similar admins with combat power far beyond their displayed levels,” Pan Feng explained. “Now that you know about derivative beings, if you ever encounter one again—though the odds are practically zero—please cooperate with the on-site admin and keep it secret from other players.”
Feng Bu Jue mused, “I’m curious… What happens if a derivative being escapes your hunt within a scenario?”
Pan and Hua’s expressions darkened.
Feng Bu Jue pressed on, “You admitted a single admin might fail against one. That means incidents have happened before, right? Like an admin hunting solo and getting killed by a derivative being.”
Hua Xiong said grimly, “The scenario will close normally, reverting to data. The surviving derivative being’s code becomes stronger and more cunning.”
“Cunning?” Feng Bu Jue frowned.
“Derivative beings have limited autonomous AI, categorized into Level 4 tiers. We admins typically handle the weakest Level 4s—slightly smarter than clever scenario bosses, and slightly stronger than major scenario bosses.”
“If a derivative being survives a scenario’s closure,” Hua Xiong continued, “it evolves—stronger, craftier—possibly advancing to Level 3. Level 4s fall to a single admin 97% of the time, but Level 3s require two admins. Solo attempts have less than 50% success.”
Feng Bu Jue asked, “What about higher levels?”
“We’ve never seen any,” Hua Xiong replied. “Honestly, we’ve never even heard of Level 2s. They’re theoretical at best. Level 3s have only occurred once. Even during live service, Level 3 emergence probability barely increases—still practically nonexistent.”
“Hmm… Got it. Then let’s see just how strong this Level 4 data trash in the scenario really is,” Feng Bu Jue said with a grin.
(End of Chapter)
Chapter end
Report
