Chapter 231: Attack
"Scatter! Everyone scatter!"
The Duke's command carried through the forest over the sound of burning metal and the specific acoustic aftermath of a firefight that had gone very wrong very quickly. His people were already moving — the trained response of soldiers who had learned that in ambiguous situations, dispersion was better than clustering.
The strange aircraft had climbed into the clouds and disappeared.
That bothered the Duke more than its presence had.
"Don't stand down," he said, over the comms. "The aircraft was suppression. Whatever comes next is the real objective." He looked at the armored vehicle sitting in the road with the warhead in its cargo hold and made the calculation that every mission commander made in this situation: the asset mattered more than the personnel, which meant he needed to be between the asset and whatever came next.
He was walking toward the vehicle when the figures appeared.
Not fast. Not tactical. Walking, in the specific way of something that had decided the pace was appropriate for the situation and the situation would confirm that.
"Fire," the Duke said.
His people opened up.
The figures kept walking.
The Duke watched rounds impact on the lead figure's chest — the specific visual information of projectiles connecting with a target and producing nothing he'd ever seen a target produce, which was continued forward movement at the same pace. The figure registered the impacts without registering them as impacts, the body language of someone walking through something that didn't rate as a significant event.
"Grenades," he said.
The grenades were accurate. The blast radius was correct. The lead figure went backward several meters and then stood up with the specific quality of someone checking whether something had happened to them and determining that it hadn't.
The Duke watched this and revised his understanding of the engagement parameters.
The figures were wearing combat suits — the all-black configuration that his initial observation had categorized as tactical gear. The assessment had been wrong. What they were wearing was something different from tactical gear in the same way that a tank was different from a car. The high-density alloy that covered the torso, the helmet construction, the specific materials science that his weapons were confirming he hadn't encountered before — this was purpose-built for exactly this: absorbing everything that conventional infantry weapons could generate and continuing.
The weapons they were carrying were the specific contradiction that made the situation difficult to process.
AK-47s. Soviet-era grenades. Some World War II-vintage firearms that the Duke recognized from museum pieces rather than operational experience.
Antiquated weapons. Impenetrable armor. An aircraft that had taken apart his convoy like it was made of cardboard.
The combination didn't make sense within any threat framework he'd been briefed on, and the Duke had been briefed on most of them.
What it did make sense as was a force that had prioritized defense and mobility over firepower — people who knew they could take hits and stay functional, and who had made the tactical calculation that under those circumstances the specific quality of the weapon mattered less than the specific quality of the person using it.
That calculation was proving correct.
His people were doing what trained soldiers did when they found something conventional weapons couldn't stop — concentrated fire, attempting to overwhelm any system with sustained input to find the threshold where it failed. The approach was sound. It was producing results, eventually — the alloy had limits, and sustained concentrated fire was reaching them.
The problem was the exchange rate.
By the time his people generated enough sustained concentrated fire to breach one suit's armor, the people inside the suits had generated enough output with their vintage weapons to remove two or three of his people. The engagement math didn't favor his side.
Ripcord — the Duke's primary weapons specialist, a soldier whose reaction time and combat competence had pulled the Duke out of bad situations more than once — had positioned himself with a heavy weapon and was covering the Duke's position.
"Go," Ripcord said. "I've got your flank."
The Duke looked at the remaining battlefield. Three of his people still functional. The rest were down — not dead, he was noting, the dark Knights were taking people out of the fight without the follow-through that would have made the outcome permanent. That was information.
They were taking prisoners, or leaving survivors.
That was a choice. Someone had made that choice deliberately.
The Duke filed it and sprinted for the armored vehicle.
The briefcase with the warhead documentation was in the cargo hold — the specific item that the mission required him to protect. He got to it ahead of the nearest advancing Knight, pulled it clear, and turned.
The Knight was already there.
Six feet away. The helmet's construction made reading expression impossible but the body language communicated something that wasn't aggression — the specific quality of something that was doing a job and had reached the end of it.
The Duke raised his pistol and fired into the helmet at point blank range.
The helmet produced a dent.
One dent.
From a full magazine fired directly into it from six inches.
The Knight reached past him and took the briefcase with the easy confidence of something that had never doubted the outcome, turned, and walked away.
The Duke fired again.
The Knight's pace didn't change.
"Stand down." The voice came from behind him — the same voice from earlier, the man who had told him this was a demonstration.
The Duke turned.
Jake was standing at the road's edge, coat in place, watching the engagement wind down with the expression of someone reviewing the execution of a plan rather than the outcome of a fight.
"You said demonstration," the Duke said.
"That was the first part," Jake said. "This is the second part."
The Duke looked at his people — the ones still standing, the ones on the ground who were functional but had been put there by impact rather than penetration. He looked at the Knights withdrawing through the forest with the coordinated patience of people who had accomplished what they came to accomplish.
He looked at the briefcase disappearing into the trees.
"The warhead," he said.
"The warhead documentation," Jake said. "The warhead itself is still in the vehicle. The documentation is what I need."
"Why," the Duke said.
"Because the warhead is evidence of what the research team built," Jake said. "The documentation explains how they built it. The how is what's useful to me."
The Duke looked at him.
"You told me this was about a conversation," the Duke said.
"It is," Jake said. "The first conversation established that I have capabilities you haven't encountered. The second conversation establishes that I have intentions you haven't assumed." He paused. "I could have taken the warhead. I could have killed your people. I did neither of those things, and I told you in advance why."
Ripcord had lowered the heavy weapon and was watching this exchange with the focused attention of someone who was taking everything in and forming conclusions about it.
The Duke looked at Ripcord.
Then back at Jake.
"General Hawk," the Duke said.
"The meeting you said you'd arrange," Jake said.
"I'll make the call," the Duke said. For the second time. With a different quality to it — the first time had been the contingent agreement of someone managing a developing situation, the second time was the specific quality of someone who had processed enough information to believe the call was worth making.
"Your documentation will be returned through a neutral intermediary when the meeting is confirmed," Jake said.
The Duke looked at him.
"You're holding the documentation as leverage," he said.
"I'm holding the documentation as a scheduling mechanism," Jake said. "When the meeting happens, the documentation comes back. Your research team can verify its integrity — nothing has been altered, nothing has been copied." He paused. "I have what I need from it already."
"You memorized it," Ripcord said, from the side. The tone wasn't accusatory — the tone of someone who had been watching and had arrived at the most logical explanation.
"My AI processed it," Jake said. "Through my wrist unit. It took about four seconds."
Ripcord looked at the wrist unit.
The Duke looked at the wrist unit.
"Four seconds," the Duke said.
"The Red Queen is very fast," Jake said.
The Duke exhaled through his nose in the specific way of someone who had decided to accept the situation as it was rather than the situation as they'd expected it to be when they'd woken up that morning.
"The meeting," he said. "General Hawk."
"When you're ready," Jake said.
He turned.
Selene was at the tree line, the specific quality of someone who had been watching an engagement from overwatch and had assessments she was going to share.
Matilda was beside Selene.
Princess was in Matilda's arms, looking at the Duke with the evaluating attention that the cat brought to everyone.
The Duke looked at the small girl and the cat.
"That's—" he said.
"Part of the Dark Council," Jake said. "Yes."
The Duke processed this.
"The one that— the cat," he said.
"She's more capable than she looks," Jake said. "Most things here are."
The Duke looked at the cat one more time.
Princess looked back at him with the calm, unhurried assessment of something that was conducting an evaluation and was taking its time.
The Duke turned to his comms unit.
The withdrawal route took the team through the forest's eastern edge and to the designated transit point two kilometers north.
The Knights were loose with the specific quality of people who had been in a real engagement for the first time in a while and were processing the residual energy of it. Not reckless — the Dark Council's training had produced something more disciplined than the War Boy baseline — but alive in the specific way that combat adrenaline produced in people who had been built for it.
Jake walked through them and listened to the debrief fragments — what had worked, what hadn't, where the coordination had been clean and where it had needed adjustment.
Selene was running her own version of the same assessment, which was more organized and more detailed and was going to produce a written summary that Jake was going to find very useful.
Matilda had her notes out.
"The second fire contact," she said to Jake, walking beside him. "The Duke's people tried to concentrate fire on single targets to breach the armor. That's correct tactical thinking. The problem is the response time — between identifying the concentration and achieving the breach, the individual Knight had too much time to respond and was neutralizing the concentrating units before the breach completed."
Jake looked at her.
"You're twelve," he said.
"I'm thirteen in two months," she said. "And I've been watching you fight since the Hunger Games arena and I read everything the Red Queen flags as tactically relevant." She turned a page in the notebook. "The solution is either faster concentration — multiple units coordinating simultaneously rather than sequentially — or more vulnerable armor at specific points to reduce the breach threshold, which creates a risk management problem on our side."
Jake walked.
"You're going to talk to Selene about this," he said.
"I was planning to," Matilda said. "She's going to have the same observation. It's better if I bring it to her first than have her bring it to me."
Jake looked at the path ahead.
"That's sound thinking," he said.
Matilda made a sound that communicated she was aware of this and had known it before he said it.
Princess, from Matilda's shoulder, turned to look back at the direction they'd come from — the tree line, the road, the Duke's people in the distance assessing the situation and making calls.
"He's a good soldier," Princess said, which was the specific comment that the cat made when she'd completed an assessment and had reached a conclusion worth sharing.
"The Duke," Jake said.
"Yes," Princess said.
"I know," Jake said.
He thought about the franchise's established timeline — where the Duke was in the narrative, what was coming for him, the specific crucible that the G.I. Joe story built toward. The Duke was in the early phase of something that was going to demand everything he had.
The Dark Council didn't need him yet.
But the timeline was going to produce a moment when the Duke would need somewhere to go.
Jake was going to make sure the somewhere was there.
He reached the transit point, confirmed the team was assembled, looked at the briefcase that the senior Knight was carrying.
The documentation was in the Red Queen's memory.
The rest was logistics and timing.
He initiated the transit.
The forest disappeared.
[Power Stone Goal: 500 = +1 Chapter]
[Review Goal: 10 = +1 Chapter]
If you liked it, feel free to leave a review.
20+chapters ahead on P1treon Soulforger