176: The First Original Condition

The April 6 session started at eight PM.

Standard Floor 20 run — the weekly schedule that had been producing the highest revenue yield since December. One hundred and thirty-three members in the formation. Tunnel relay, drain redirect, Phase 2, Phase 3. The [x] modifier sitting at 43.1% from last night's session, the same number that had been in Wenqing's update at eleven PM the night before. I'd set the 2:45 AM alarm, slept, woken to the dark ceiling of the dorm room, and logged in for the three AM window the way I'd been logging in for three months.

Nothing about the eight PM session looked different from any other eight PM session. The formation assembled correctly. Ironmark confirmed the aggro rotation on the command channel. TwilightTide acknowledged position from her sixteen-meter mark in the healer cluster — I'd read Wenqing's note about the distance table, had marked it to discuss with her later, had not yet sent it. Old Wolf gave the pull signal at 8:17 PM in the flat, precise way he always gave the pull signal, with no particular inflection for the fact that this might be the session Wenqing's model had pointed toward.

We pulled the Abyssal Sovereign at 8:17.

Phase 1 was normal through the first eleven minutes. My output tracked at the usual level — the transitional class's combat profile had become familiar enough by December that the council read it the same way they'd read the Berserker output before. The void field applied at minute four, exactly on cue. Ironmark held aggro through the first suppression pulse. TwilightTide ran the healer channel in the abbreviated-attention register she'd developed since March, where the coordination calls had compressed down to the minimum because everyone in the channel already knew the pattern.

Zhu Yuhan, at the sixteen-meter mark, applied a heal to Ironmark at the eight-second cycle. Then again at the sixteen. The rhythm of it.

At minute twelve, the [x] modifier panel in the bottom-right corner of my interface updated.

Not a number this time.

A notification.

*[System: BLADE SOVEREIGN (TRANSITIONAL) — THRESHOLD CONDITION DETECTED. CLASS ACCUMULATION: COMPLETE. INITIATING EXPRESSION SEQUENCE.]*

I read it in the half-second between attack chains, in the window between the second hit and the recovery animation. The Abyssal Sovereign's HP bar was still moving down the right side of my screen. The formation was still running. I hit the next chain while the panel updated again:

*[System: CLASS EXPRESSION ACTIVE. FORMATION RESONANCE — SOVEREIGN'S EDGE. Duration: variable. Effect: adjacent formation members within 12 meters receive a secondary resonance pulse synchronized to Bladeless's next three strikes. Resonance augments the target's next skill activation with edge-synchronization — output modifier: variable based on formation depth. This effect is not a buff. It is not a skill. It is what the blade means when the blade knows the formation.]*

I read it in the two seconds between my attack chains, in the recovery window that a practiced player could find and use.

*Not a buff. Not a skill.*

The Sovereign's strikes and the formation's intent, synchronized.

I hit the Abyssal Sovereign on the next attack chain. The interface didn't change visually — no particle system floated up from adjacent guild members, no glow ring appeared on the ground beneath my feet, no status icon materialized above anyone's health bar. Whatever was happening was happening in the combat log. Nothing on the surface of the game announced itself.

Wenqing's message on the private channel arrived one second after the hit:

*Something just happened in the combat log. Ironmark's next attack chain output 18.7% higher than his standard profile. No consumable, no environmental buff, no skill in his tree.*

Then: *Old Wolf's block sequence blocked 23.4% more than his calculated threshold. That's not variance.*

Then, four seconds after: *TwilightTide's next heal cycle — 6.2% above her standard output. This is happening across the adjacent zone. This is not any Berserker skill. What did you just do.*

*The class expressed,* I sent.

He didn't reply for eight seconds. I kept fighting. The Abyssal Sovereign was at 61% HP. The void field shifted its anchor point and the formation adjusted — Ironmark stepped two meters to the right without being told, because he'd run this formation for months and knew the void field's shift pattern the same way he knew his own cooldown timers.

*I see it in the log,* Wenqing sent. *The intervals are 3–4 seconds, tied to your attack timing. The class is — it's using your strikes as synchronization pulses. The adjacent members are attaching their output to your rhythm without knowing it.*

Formation resonance. What the blade means when the blade knows the formation.

The words in the notification had been precise. They'd said it wasn't a buff. They'd said it wasn't a skill. They'd said it was what the blade *meant* — which was not the language of a game mechanic. It was the language of something that had been designed to refuse the usual categories.

Old Wolf, on the command channel at minute fourteen: *Something changed. The output across the tanks just spiked. Not consistently — in intervals. What is that.*

*The class expressed,* I sent on the command channel. *Run the session. Don't adjust for it.*

*Don't adjust for it,* he repeated. Then, after a pause in which I could almost feel him doing the mental arithmetic of a raid leader deciding whether to trust an unusual instruction mid-fight: *All right.*

TwilightTide on the healer channel, quietly: *I can feel it in the output timing. When you strike, the next cycle comes easier.* A pause — not the functional pause of someone checking a cooldown timer but the pause of someone putting language to something they hadn't expected to feel. *Is that it. Is that what the class does.*

*Yes,* I sent. *That's what it does.*

She didn't respond. The session continued.

Phase 1 cleared at the thirty-nine minute mark — four minutes faster than the average since December. Phase 2 and Phase 3 ran at the same pace but with a quality of efficiency that was harder to quantify than the Phase 1 time. The formation wasn't hitting harder in the way a buff made you hit harder. It was hitting at the right moments — the attack cycles landing in the windows they should land in, the heal pulses releasing at the correct instants, the tank repositioning happening half a second earlier than it usually happened. Not more damage. Better timing.

Which, in a sustained five-hour boss encounter, amounted to the same thing.

At the kill notification, the system panel updated:

*[System: BLADE SOVEREIGN (TRANSITIONAL) — FIRST ORIGINAL CONDITION: EXPRESSED. FULL CLASS DESIGNATION ACCUMULATION: 94%. REMAINING THRESHOLD: SUBSEQUENT FORMATION SESSIONS. DESIGNATION: BLADE SOVEREIGN (TRANSITIONAL). NOTE: FULL DESIGNATION WILL COMPLETE WITHIN 30 DAYS OF FIRST EXPRESSION.]*

94%. Not complete.

But expressed.

The transitional class had done what a Berserker couldn't do — had synchronized the guild formation's output to the rhythm of a single blade, not through a skill, not through a buff, but through the pattern of strikes in a space where the formation already knew how to listen.

***

Wenqing sent a six-page analysis at eleven PM.

He'd been watching the combat log in real time during the session. The document arrived already organized — not a first-pass summary but a structured analysis, the kind he produced when he'd been running the numbers in parallel with the event itself.

Page 1 was the combat log data. The exact output records showing the resonance intervals across eleven adjacent guild members. The intervals were consistent in timing with my attack chain, within a margin of 0.3 seconds. The output augmentation ranged from 4.2% on Old Wolf, who had been farthest in the adjacent zone at 11.8 meters, to 22.1% on Ironmark, who had been at 4.3 meters, closest to the blade.

Distance inverse relationship. The closer to the blade, the stronger the resonance. Which made a particular kind of sense that the Berserker class had never required me to think about.

Page 2 was the analysis of mechanism. He'd written: *The mechanism is not a standard MMORPG buff system. Standard buffs use a skill-triggered effect flag that appears in the log as a status code. There is no status code for what Bladeless applied tonight. The output augmentation is attached to the existing skills of adjacent guild members — it's not a new effect layered on top. It augments what is already there by adding coherence to the timing. The adjacent members' skills are hitting at a more optimal phase of the attack cycle — better impact timing — because the resonance pulse is orienting them to a shared rhythm.*

He'd been watching MMORPG combat mechanics for two years. He understood what was in the log and what shouldn't have been. The specific precision of his language — *no status code, attached to existing skills, coherence to the timing* — was the precision of someone who had looked at the data and eliminated every simpler explanation before settling on the one that fit.

Page 3 was the strategic implications. I skimmed to the conclusion: *The formation resonance, if it holds across multiple sessions and different combat contexts, represents a qualitatively different kind of guild coordination capability. Not a higher-tier version of what the guild already does. Something else: a way of fighting in which the guild's aggregate output is attached to a central coordinating node that is not a tank, not a healer, not a position in the formation — but the blade itself.*

Something else. That was accurate.

Pages 4 through 6 were the data tables. I didn't read the tables. Wenqing would send a summary when he'd finished processing them, and the summary would be better than me reading the raw numbers at eleven-thirty PM.

***

I logged out at eleven-thirty and went to the bench.

Wanqing was there. She'd been tracking the guild record tab on her phone — I'd known she would be. The April evening was mild. The mid-green maple was visible in the campus lights, the specific color of April growth that had arrived without announcement and was now simply there. The thermos was between us on the bench in the position it always occupied.

"It happened," she said.

"Yes."

"Wenqing updated the guild record at eleven."

"He was watching the combat log in real time."

She poured without asking, the way she'd been pouring for a year and a half at this bench. The steam rose at the right height for the April temperature — not the vertical column of a cold December night, not the low diffuse rise of July. The April height.

We sat for a moment in the way that didn't require filling. The campus was quiet. Students still on the paths between buildings — an April Wednesday night had a different quality than a December Wednesday night, the foot traffic lighter but present, the evening still warm enough that people moved through it without hurrying.

"Tell me what it does," she said.

I told her what the system notification had said. What Wenqing had described in his analysis. The resonance intervals. The distance-inverse relationship. The adjacent output augmentation — Ironmark at 22.1%, Old Wolf at 4.2%, TwilightTide at 6.2%. The mechanism: not a status code, not a buff layered on top, but coherence added to existing timing.

She listened with the kind of attention that doesn't interrupt because it's receiving the shape of the information, not just the data points.

When I finished, she was quiet for a while.

"Not a skill," she said.

"Not a skill."

"Not a buff."

"No status flag in the combat log. He checked."

She held the thermos cup. The steam rising in the April evening. "What is it, then."

I thought about the twenty-first sequence. The Sword Sovereign at the empty doorway with no equipment designation, no visible class indicator, nothing in the combat log to say what he was — just the doorway and the man going through it, walking east into whatever the sequences had prepared him for. *I'll recognize it when it happens,* Beigong Yan had said. The recognition had not been dramatic. It had been a combat log entry that shouldn't have existed and a formation hitting intervals it had no mechanical reason to hit.

"The class's design is about severing," I said. "Not just cutting through resistance. Severing the boundary between what the blade does alone and what the blade does in a space where others are also working. The resonance is what happens when the blade knows the formation well enough that the formation starts hearing the blade's timing and hitting on it."

She looked at the campus. The April paths. The mid-green leaves in the light. "He severed himself from the blade," she said — she was quoting TwilightTide's unfinished sentence from December, the one that had trailed off in the healer channel because the second half of it hadn't existed yet.

"The sequences were the transition. What was left was—"

"This," she said.

"Yes."

She was quiet for a while. Long enough that the silence became its own kind of comment on the size of what had arrived.

"94%," she said.

"Within thirty days of first expression. Wenqing's model said there was a maturation period after the first original condition. He predicted it back in January."

"He predicted it before you knew there was anything to predict."

"He built the model from the January data. He was right about what the data was showing him."

She set the cup down on the bench. The sound it made — ceramic on wood, in the April quiet — was small and specific. "What happens at 100%."

"I don't know. The system notification said the class would show me. Beigong Yan said the same. After the full designation."

"Thirty days."

"At most. The acceleration pattern might be faster."

She looked at the maple. The April leaves in the campus light had the specific quality of growth that had arrived without announcing itself — the tree was mid-spring before anyone had counted the days since the early-bud stage. "I've been watching you build toward this since October 2015," she said. "The Pioneer's Path cycles. The Heritage Fragments. The Floor 20 attempt. The sequences. The modifier."

"Eighteen months from the Pioneer's Path first node."

"Longer than that. You knew about the class before the first node. You built toward it from before October 2015."

She was right. I'd walked into the Pioneer's Path on the first day of the game already knowing where the path led — not in detail, not with certainty about any specific mechanic, but with the knowledge that the class existed and that it was worth the accumulation cost. The work had started before the work started.

"Yes," I said.

She looked at me. Then she looked at the maple again. Whatever she was deciding not to say, she decided not to say it. "Good," she said. "What comes next."

"The sessions between now and the full designation. Wenqing's new model. Then the 100% system notification."

"And after that."

"After that, the class shows me."

She poured again. The April night was mild enough that the tea stayed warm in the cup longer than it did in November. She held the cup with both hands, not for warmth but for the familiar weight of it.

"All right," she said. "Tell me when it does."