NovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · readerNovelReader · reader
Reborn Sword Sovereign · Chapter 166
Reborn Sword Sovereign · Chapter 166
Read in
Chapter 166 · 2373 words · 11 min

166: Abyssal Sovereign

TwilightTide had the drain mechanic solution by Wednesday.

She sent the preliminary analysis Tuesday evening, which was earlier than she'd said. The document was twelve pages. The first page was the summary; the next eleven were the session log annotations, the frame-by-frame HP data from the drain's 30-second window, and the statistical modeling of activation timing. I read all twelve pages. Not because I needed the full statistical model — the summary was sufficient for understanding the approach — but because the care in the detail was worth recognizing. Someone had looked at a failed attempt for four days and come back with the structural answer. That was worth the twelve pages.

The drain effect — the targeting pulse that selected the highest-HP member and applied 840 HP per second drain for 30 seconds — had a single design property she'd identified from the session log data: it targeted the current highest-HP member at the moment of activation, not the highest-HP member throughout Phase 1. It was a snapshot, not a running calculation.

Which meant the snapshot could be manipulated.

If the highest-HP member had a temporary debuff active that reduced their HP below the second-highest member's current HP at the exact moment the targeting pulse fired, the drain would select the second-highest instead.

The second-highest HP in the guild formation was a tank named Ironmark. His tank build ran at 24,300 HP base, approximately 4,300 below my Berserker pool.

"If we apply a temporary HP-debuff to Bladeless of at least 4,301 HP at the moment before the targeting pulse fires, the drain selects Ironmark instead," TwilightTide said at the Wednesday briefing. She drew the HP numbers on the briefing board — mine, Ironmark's, the required reduction amount. "The pulse fires at the 35-minute mark based on last week's Phase 1 timing. The HP-debuff needs to be active at the 34-minute mark to cover the variance window."

"What debuff," Wenqing said.

"The Iron Magistrate's Judgment Seal. It's a consumable debuff item — it reduces HP by 5,000 for 90 seconds. We've had them in the guild inventory since the Floor 11 clear. They were the off-spec loot from the Floor 11 boss."

Old Wolf: "We use a consumable debuff on our own guild commander to redirect the targeting pulse."

"Yes. He takes the HP reduction, the pulse reads him as lower HP than Ironmark, the drain locks onto Ironmark instead." She looked at Ironmark, who was in the standard position at the back-left of the briefing room. "Ironmark is outside the void field at 16 meters — Zhu Yuhan can heal the drain at full output."

"840 HP per second for 30 seconds," Zhu Yuhan said. "25,200 total drain. Against Ironmark's 24,300 pool — he doesn't survive the full 30 seconds unhealed."

"No. I need to sustain net positive healing of 700 HP per second on Ironmark for the full 30 seconds to keep him above zero. That's achievable at 16 meters with my current output profile and the standard buff stack." She looked at Zhu Yuhan. "It's achievable. Not comfortable."

Zhu Yuhan looked at her. "We've done harder things."

"Yes," TwilightTide said. "We have."

The Saturday attempt had the relay tunnel run in 42 minutes — three minutes faster than the previous week because the formation's second iteration through the relay timing was cleaner. The second time through any complex coordination is always better. The first run builds the muscle memory; the second run uses it. The Graveyard Approach — the server's name for it, accumulated from months of other guilds' failures — had stopped being the problem the moment we had a solution for it. The problem was now the floor itself, which was the right kind of problem to have.

We reached the boss chamber with 132 members — four more than the first attempt. The pre-fight formation hold at the chamber entrance was shorter than last week. Old Wolf called positions with fewer words. Everyone was already in them. The chamber had the specific quality of a space we'd been in before — familiar without being comfortable. The second attempt carried the first attempt's information in it, which was the only way information worked in high-difficulty content: you earned the knowledge by surviving contact with the mechanic, and then you applied it. There was no shortcut to the first contact.

Phase 1 ran at the drain-redirect strategy. The void field applied. The tank line held the 16-meter healer boundary. At minute 34 I applied the Judgment Seal consumable. The debuff landed: HP dropped by 5,000, to 23,600 — 700 below Ironmark's 24,300. The interface showed my HP bar significantly shorter than Ironmark's for the 90-second window.

The targeting pulse fired at the 35-minute mark.

The drain locked onto Ironmark.

Zhu Yuhan held him through the full 30 seconds. It was not a clean recovery — Ironmark came out of the drain at 200 HP, which was the margin of survival that was smaller than TwilightTide's model had estimated but which was still above zero. Two hundred was enough.

Phase 1 fell at the 41-minute mark.

*Ding!*

[System: ABYSSAL SOVEREIGN — Phase 1 complete. Phase 2 commencing.]

Phase 2: a domain expansion that enlarged the boss chamber's effective field by 300%, filling the enlarged space with void energy that dealt progressive damage per second to any guild member not in a formation with at least four adjacent members within three meters. The formation had to maintain cohesion — everyone within reach of at least four others — while dealing with the boss's Phase 2 attack patterns and moving through the expanded space. The domain expansion had been in TwilightTide's Wednesday briefing as a theoretical: *If Phase 2 is a domain mechanic, the counter is cluster formation. I've built a draft cluster protocol. We may not need it.* We needed it. The draft protocol was already in the formation channel's pinned documents. She'd built it for a mechanic she hadn't confirmed existed.

TwilightTide: "Tight cluster formation for Phase 2. Everyone within 3 meters of at least four others. We lose DPS efficiency but we eliminate the void damage. I'll call the cluster adjustment if the formation drifts."

Old Wolf: "Healers."

"Inside the cluster. Zhu Yuhan and I heal from inside the formation, not from a perimeter position. Full coverage, lower mobility."

Phase 2 ran for 58 minutes. The longest Phase 2 of any Black Castle boss we'd faced — 16 minutes longer than the Voidcrown Empress. The cluster formation held through most of it. The difficulty was the attrition: with everyone within three meters of four others, the formation couldn't disperse to dodge the boss's secondary attacks. Twelve AoE attacks over 58 minutes, each one catching 30-40% of the formation's footprint. At the 50-minute mark we'd lost 27 members.

The cluster's internal discipline was a different kind of difficult from anything we'd run before. Standard formation thinking separated roles by position — melee at range, healers at perimeter, tanks at front. The cluster collapsed all of that into a single body that had to function as if the role separation still existed even though the physical separation didn't. TwilightTide held the coverage map in her head and called position adjustments within the cluster — two meters left, rotate the tank line clockwise, bring the rear DPS forward — the whole time maintaining her own output and tracking the incoming attack patterns. It was a kind of multitasking I'd seen her do in three AM sessions, in the quiet when there was no one watching, and which she did now the same way: without making it visible that it was difficult.

The TwilightTide-Zhu Yuhan healer coverage from inside the cluster was the factor that made the cluster viable. Healer mobility in a cluster formation was reduced — they couldn't reposition without pulling others out of cluster range — so the coverage had to be managed through priority calls and precise output control. TwilightTide ran the priority calls. Zhu Yuhan ran the output. They had been doing this from inside formations for a year.

105 of 132 remaining.

At 5% HP the Abyssal Sovereign entered Phase 3: a soul-binding mechanic. One player targeted. Forced to mirror the boss's movement for 15 seconds — wherever the boss moved, the bound player moved with it, pulled by an invisible tether that the game rendered as a faint violet line between them. If the tether covered more than 40 meters in the 15-second window, it snapped and the targeted player took instant-death damage.

The soul-bind targeted TwilightTide at the 3% HP mark.

She was pulled twelve meters in the first five seconds — the Sovereign was moving fast in the Phase 3 finale, its movement pattern erratic. Ten more meters in the next five seconds, cutting across the chamber in a diagonal. At ten seconds she was 22 meters from her starting position, moving toward the 40-meter limit faster than the linear rate suggested.

Zhu Yuhan began moving with her without being asked.

She didn't say anything on the healer channel. She just moved — staying within TwilightTide's healing range, tracking the trajectory of the soul-bind's pull, maintaining her output while TwilightTide was being dragged across the chamber floor. She did it the way someone does a thing they'd already decided they would do if this moment came.

The fifteen seconds ended. TwilightTide had covered 31 meters. Nine meters under the limit. The tether released with the game engine's signature dissolution effect — the violet line fracturing into light and disappearing.

"Thank you," TwilightTide said, on the healer channel. Her voice on the channel had the specific quality of someone who'd just spent 15 seconds being pulled across a chamber floor by a game mechanic and was monitoring their own state for any output drop in the process. None.

"You knew I'd follow," Zhu Yuhan said.

"Yes."

"Then it wasn't a surprise."

"No. It was still worth saying."

A beat on the channel, and then both of them returned to their coverage positions without any further acknowledgment. The work continued.

Final push: 3% to 0. Four minutes. Eighty-nine members remaining. The last 3% of a boss this deep in the Black Castle was the most mechanically dense phase of any fight we'd run — every system running at maximum, every mistake punished immediately. The formation held. The kills came in. Old Wolf was calling positions without any of the verbosity that early-stage fights required — single words, compass directions, role designations. The guild had been in enough high-pressure minutes together that the full sentence wasn't needed. The word was enough because the context was already shared. That was what two years of formation-building produced at the three-percent mark: the shared context that made the full sentence unnecessary.

At 0%:

*Ding!*

[System: ABYSSAL SOVEREIGN eliminated. BLACK CASTLE FLOOR 20 CLEARED. Server record: 5 hours, 23 minutes, 11 seconds. SEVERING LIGHT. FIRST GUILD ON TIANLONG SERVER TO CLEAR ALL 20 FLOORS.]

The guild channel was loud for a long time.

I stayed in position in the boss chamber and let the channel run. The chamber had the quality of a space where something had been completed — the Sovereign's form dissolving at the center, the void field gone, the environmental audio returning to the Black Castle's standard deep-stone quiet. The space was larger without the Phase 2 domain filling it. The same chamber it had been before the fight, with nothing in it now except 89 characters standing in the positions they'd been in when the last hit landed.

Wenqing's note appeared at the top of the notification queue: *20/20. All floors. Severing Light.* He didn't add anything to it. He didn't need to.

***

After the notification cleared, Wenqing posted the guild record: *20/20. All floors. Severing Light.* He added, below that: *Formation credit: TwilightTide (relay approach and drain redirect design). Technical execution: Ironmark (drain redirect target). Healer coordination: Zhu Yuhan (Phase 3 mobile coverage, soul-bind track).*

He credited all three. The record was accurate.

TwilightTide, on the healer channel: *He credited the Phase 3 coverage.*

Zhu Yuhan: *I saw.*

*You didn't have to do that.*

*I know. You're welcome.*

The guild channel was loud for another ten minutes — the kind of noise that came from relief and satisfaction running simultaneously, the particular sound of a group of people who had done something they'd been building toward for months. I listened to it and let it run. The channel would settle on its own.

Old Wolf's post-kill note, when the channel quieted: *Second run of the tunnel tonight was 42 minutes. Tight. The relay team is clean. Floor 20 goes on the weekly schedule starting next Saturday.* He'd already started planning the post-clear routine. That was Old Wolf's version of completion: immediate transition to the next operational question. Not celebration — orientation. The thing done was filed and the next thing was already on the desk. He'd been doing it since the first floor we cleared together. I'd learned to read it as its own form of satisfaction — the satisfaction of someone whose natural mode was forward-looking and for whom the absence of the next problem was itself the problem. There was always a next thing. Tonight's next thing was the weekly schedule.

***

Wanqing, on the bonded thread at seven PM: *All 20 floors.*

*Yes.*

*The class transition.*

*Tonight. I'm going to find Beigong Yan.*

*And then.*

*And then he tells me the final instruction.*

A pause. The thread was quiet for a moment. I could picture her at whatever she was doing on a Saturday evening — the problem set, probably, or the Suzhou flat, or somewhere between. The thread didn't tell me the location. She rarely sent messages about location. What she sent was the conversation itself, which was enough location information for the purpose — wherever she was, she was thinking about the same thing at the same moment. That was the consistent fact across whatever the physical location was.

*I'll be at the bench tomorrow morning,* she said.

*The November bench.*

*Yes. The same bench.* Another pause. *I want to be there when you tell me what he said.*

*All right.*

*Good,* she said. *Go find Beigong Yan.*

I went.

Previous166 / 350Next

Comments (0)

Sign in to comment

No comments yet.