Merge Conflict

Chapter 7: Merge Conflict

The Great Hall of the Azure Cloud Sect was a place where silence carried more weight than words. The air was thick with the scent of sandalwood incense, a fragrance that clung to the stone pillars and the embroidered robes of the sect elders. But the real pressure came from the Qi that coiled and pulsed in the air like invisible threads, binding the gathered disciples in an unspoken hierarchy. I sat at the back of the hall, my posture rigid, my mind racing through a thousand different scenarios that all ended in the same way: me being exposed.

The sect leader stood atop the dais, his robes embroidered with swirling clouds that shimmered as if alive. His voice, deep and resonant, echoed through the chamber. “The time has come for the Inter-Sect Convergence Tournament.” His gaze swept across the hall, lingering on me for the briefest of moments before moving on.

A murmur rippled through the crowd like a wave of static. My fingers twitched as I clenched them into fists. The tournament. The one that had been whispered about in the training halls, the one that had been avoided like a bug in a critical function.

The sect leader continued, his voice rising. “When the rivers meet, the currents clash. Only the strongest stream shall remain.”

I couldn’t help but think of the codebase I had once debugged, the one where conflicts had been resolved not by elegance, but by brute force. My stomach twisted. This wasn’t just a tournament. It was a test, a stress test, and I was the unverified build.

The hall erupted into a cacophony of murmurs and gasps. I watched as disciples from different sects gathered at the edges of the hall, their postures rigid with unspoken tension. Each of them radiated a different kind of power—some exuded a smooth, flowing Qi, like a well-optimized function, while others carried the chaotic, brute-force energy of a poorly written script. The sects were like different data streams, each with their own syntax, their own logic, and now, they were all converging into one execution path.

I exhaled sharply, my mind already calculating probabilities. The odds of me surviving this were about as good as a server crash during a critical deployment. But I had no choice. The System Interface flickered in my vision, a translucent overlay of glowing text and statistics, but I couldn’t focus on it now. The tournament had forced my hand. I couldn’t remain a background process anymore.

The sect leader raised a hand, and the hall fell silent once more. “The tournament will begin in three days.” His voice was calm, but the weight of his words pressed down on me like a stack overflow.

I was in over my head.

---

The courtyard at dusk was a place of flickering shadows, where the last light of the day was caught in the glow of spirit-lanterns. The lanterns, enchanted with low-level Qi, cast a soft, golden light that danced across the stone pathways. But the mood was far from serene. A crowd of disciples had gathered around a massive, enchanted parchment scroll that unfurled itself from the air like a living thing. It shimmered with the faintest traces of magical energy, updating in real time as names and rankings were inscribed onto its surface.

I approached the scroll, my stomach churning. The System Interface flickered in my vision, but I barely noticed it. My attention was fixed on the glowing text, my name appearing in the lower corner of the scroll.

Newcomer/Unranked – Kai Chen

Beside it was another name, one that sent a jolt of dread through my veins.

Zhao the Iron-Hand – Rank 142, Rival Branch, Azure Cloud Sect

Zhao. The bully who had made my life miserable during my first weeks at the sect. He had been the one to mock me, to call me a “glitch in the code of the universe,” to mock my strange ways of training, my tendency to question everything. Now, he was my opponent.

The crowd around me murmured, their voices laced with disbelief and fear. Zhao was no unknown. He was a name that carried weight, like a deprecated function that still lingered in the codebase because no one had the guts to delete it.

I took a step back, my breath shallow. I could already see it in my mind: the clash of Qi, the brutal efficiency of Zhao’s style. He was a brute-force algorithm, one that didn’t care about optimization, only raw output. And I—

I wasn’t ready for this.

But before I could turn away, a voice cut through the air like a syntax error in a perfectly written program.

“Hope you’ve prepared your funeral rites, little glitch. Your very existence is an error I intend to delete.”

Zhao was standing just behind me, his eyes gleaming with the kind of confidence that usually came from being the top-ranked disciple in the sect. He was tall, his posture like a blade poised for attack. His aura was a dense, almost suffocating Qi that pulsed with the rhythm of a well-optimized loop.

I swallowed hard.

“Don’t be so sure,” I said, my voice steady despite the tremor in my chest.

Zhao smirked. “You think you can fight me with your… whatever that is?” He waved a hand dismissively. “You’re a glitch in the system, and I’m the one who’s going to fix it.”

The crowd around us erupted into murmurs. Some of them looked at me with pity, as if I were already dead. Others looked at Zhao with a mixture of fear and admiration.

I exhaled slowly, my mind already calculating. There was no way around it. I had to fight. And I had to win.

But first, I needed to understand my opponent.

And to do that, I needed to scrape the data.

I reached into my System Interface, activating the Scripting Engine. The interface flickered, the lines of code appearing in front of my eyes like a command prompt. My fingers moved with practiced ease, typing in a command that would extract the hidden stats from the scroll.

A few seconds passed. Then, the data appeared—Zhao’s stats, his combat style, his weaknesses. My heart pounded as I analyzed the numbers. He was fast, his Qi output was high, and his defense was formidable. But I could see the cracks. There were patterns in his movements, small delays in his response time.

A buffer overflow.

A latency.

I could exploit it.

I exhaled, my mind already running through the possibilities.

Zhao had underestimated me.

But he wouldn’t for long.

---

Back in my private training cell, the air was thick with the scent of sweat and the faint metallic tang of Qi. The cell was dimly lit, the only source of light coming from the faint blue glow of my System Interface. The walls were damp, the stone cold beneath my fingertips as I sat cross-legged on the floor, my eyes fixed on the floating lines of code in front of me.

I had spent the last few hours running simulations, parsing through Zhao’s combat patterns like a codebase in need of refactoring. My mind was a blur of algorithms and optimizations, of data structures and debugging tools. Every second of my training had been spent analyzing Zhao’s style, looking for the smallest of inconsistencies, the faintest of anomalies.

And I had found them.

Zhao’s attack pattern was highly repetitive, almost too consistent. His movements followed a predictable rhythm, as if he had been coded by a developer who had never heard of randomness. His Qi output was brute-force, with no regard for optimization. He relied on sheer power, not finesse.

That was his weakness.

I had run the simulation a hundred times, each time adjusting for variables, testing different scenarios. The conclusion was always the same: Zhao’s attack pattern was low entropy, meaning it was highly predictable. His defense, while strong, had a noticeable delay in his response time—latency, in software terms. And his Qi control was poor, with several instances of buffer overflow, where he overextended his power, leaving him vulnerable for a brief moment.

If I could exploit those weaknesses, I could win.

I exhaled, my breath uneven. The weight of the task ahead pressed down on me like the final line of a function that had to be perfectly optimized or risk a crash.

I wasn’t just fighting Zhao. I was fighting the entire system.

The System Interface flickered again, the lines of code shifting as I ran a final simulation. My fingers moved, typing in a command that would test my hypothesis.

A few seconds passed. Then, the simulation played out in front of me.

Zhao, in the simulation, was attacking with his usual brute-force style. His fist shot forward with the force of a thousand hammer strikes. I dodged, my movements precise, calculated. The moment he overextended, I struck, exploiting the buffer overflow. His defense faltered, and I landed a blow that would have been impossible in real combat.

He fell to the ground, his Qi flickering like a corrupted file.

The simulation ended. I stared at the screen, my mind racing.

I had done it.

But the System Interface flickered, and a message appeared in the corner of my vision:

ERROR: UNEXPECTED DATA CORRUPTION. REBOOTING...

The screen flickered, and my vision went black.

Then, everything went silent.