Ten years, fourth month, and fifth day after the Battle of Yavin…
Or the forty-fifth year, fourth month, and fifth day after the Great Resynchronization.
(One year and twentieth day since arrival).
Captain Tschel was nervous.
The young officer, on the bridge of a Dominion Star Destroyer, maintained outward calm but couldn't quite get a grip on himself and push aside the anxiety.
It's not that easy—to be on the edge of Dominion territory, awaiting the enemy's appearance, and not worry.
Tschel glanced at the tactical monitor.
Dominion warships were arrayed in a standard blocking formation, a "receiving bowl," as if expecting the enemy's arrival from the depths of the northern terminus of the Hydian Way.
But that wasn't the case at all.
They were waiting—no doubt.
But the battle would unfold far from here.
They were waiting for the scout droids to transmit data about the enemy entering the trap.
And only then would the Red Star attack.
Until then, they simply waited.
Their formation, comprising the Dominion's newest Star Destroyers and a fast Star Dreadnought, a couple of Venator-type Star Destroyers, and a considerable number of support ships, this time least resembled a standard interception disposition.
If only because four Interdictor-class Star Destroyers were positioned not behind the main forces but on the flanks, generously covered by heavy cruisers.
He kept running through the moments of the upcoming operation in his head, which would be the Chimaera's first after modernization under the extreme refit program.
The margin for deep modifications to ships of this class was nearing exhaustion.
Quantitatively, there was almost nothing left to improve—the "trios" had squeezed the maximum possible out of them.
And at the moment, Captain Tschel viewed participation in the operation under Vice Admiral Shohashi's command as a kind of exam on professional suitability.
Like a diligent student, he intended to pass this test with flying colors.
Perhaps, after the coming battle, the Grand Admiral would want to return to the Chimaera.
Honestly, there was a certain gloom on board the Star Destroyer over the fact that Thrawn was making history from the Guardian's bridge.
Not that any crew member foolishly wanted to discuss or condemn the Supreme Commander's decision to transfer his flag to another ship.
It's just that the Chimaera's crew was too accustomed to being at the center of Grand Admiral Thrawn's designs.
When you've been at the forefront of events for almost two years since Thrawn's return from the Unknown Regions, being relegated to the ranks of "ordinary" Dominion regular fleet ships seemed insulting and disappointing.
Tschel, and the entire crew, including the last cabin boy, knew these were just their conjectures.
But they still wanted to return to Thrawn's "inner circle."
And even the Chimaera's attachment to the Red Star—the most effective and successful formation in the Dominion regular fleet after Thrawn's flotilla—didn't smooth over the sharp edges of disappointed public opinion.
The Chimaera's commander had heard more than once that Shohashi was considered the most capable commander among all Dominion regular fleet formation commanders.
The others were great too, but the combat record of the Red Star under the command of the "Butcher of Atoa" surpassed them many times over and by a noticeable margin.
And now, the squadron under Vice Admiral Shohashi's command clearly intended to inscribe itself once more into the lists of heroes.
* * *
Sykes-Twenty Seven, commander of the Zann Consortium combat wing responsible for the security of the Aparo sector, anticipated with relish the moment his flotilla, having successfully completed its mission, would arrive at its permanent station.
As he had assumed—when the enemy introduced its blocking detachments into the Lur system, they thereby lifted the blockade of the hyperspace routes leading out of the system along their length.
The single interdictor cruiser that intercepted Sykes-Twenty Seven's fleet during the retreat along the sixth vector offered no serious resistance, folded its gravity projectors, and made a retreat jump.
Thus allowing the triumphant commander to continue his flight to the borders of the Aparo sector.
The victory he achieved at the snowy world of Lur was glorious, but it would pale in comparison to what he intended to accomplish by breaking through the sector's mine blockade and moving into the Zann Consortium's metropolitan territory.
As in the previous operation to lure the enemy into minefields, the breakout plan was elegant in its simplicity.
Tyber Zann's advisor, Shadowspawn, using his supernatural skills, would coordinate a double breakthrough of the minefield.
On one side of the barrier, the attack would come from starships of the Corporate Sector.
Hundreds of requisitioned transport ships would strike the mines from one side—from the Corporate Sector.
While Sykes-Twenty Seven attacked with the remnants of his light fleet from the Aparo sector side.
The double strike would allow the ships to break through the defense fairly quickly and thereby evacuate the tools and specialists on the destroyers for restoring cloning capabilities directly in the Corporate Sector.
Sykes-Twenty Seven was confident he could withdraw his forces under the protection of the main forces before the Dominion's main forces, which he had been fighting until now, arrived at the breakthrough point.
Undoubtedly, he hadn't destroyed all the forces opposing him in the Battle of Lur.
By the presence of a fast Star Dreadnought in the enemy forces, he understood he was facing Erik Shohashi, known even in the Galactic Empire as the "Butcher of Atoa."
And he didn't delude himself with the thought that the enemy hadn't grasped his intentions.
Yes, they sacrificed their auxiliary forces—as Shadowspawn promised—for the breakthrough to Lur.
Undoubtedly, the Dominion needed the same Lurrian cloning capabilities as the Zann Consortium itself.
But Sykes-Twenty Seven wouldn't encounter large forces on the way to operational freedom either.
Shohashi recalled hundreds of his small ships from controlling the Aparo sector territories.
And now that he had lost them, now that his fleet had broken out of the trap, Shohashi would undoubtedly rush to defend the exposed territories.
The loss of auxiliary forces meant Shohashi would have to use his own Star Destroyers and heavy cruisers for garrison duty.
Consequently, even if he figured out what was happening, he could only pull far from the largest forces under his command to the breakthrough point on the Hydian Way.
Considering the number and combat capability of Sykes-Twenty Seven's own destroyers, as well as the support starships the Zann Consortium would deploy to meet and escort them, whatever Shohashi brought to the breakthrough point would be destroyed in a short time.
But the clone didn't much believe a battle would occur.
Shohashi had too much territory to guard now, so even if he understood where the breakout forces from the Lur system were heading, he would surely rush to assault the planet itself, not finish off the surviving Zann Consortium destroyers.
And he would run into the camouflaged starships left precisely for such an occasion.
Sykes-Twenty Seven knew Shohashi had already begun implementing this plan—he had sent his blocking detachments into the Lur system again.
This time, he blocked all six escape routes.
Obviously, he thought no "surprise" was prepared for him.
Too bad the interference induced by Dominion ships prevented understanding what was happening in the system itself, but the result would be as the Zann Consortium planned.
In any case, wherever Shohashi appeared, he faced inevitable and logical defeat.
Sykes-Twenty Seven, unlike some other clones of the original Jared Sykes, who disappeared during the offensive against the Dominion several weeks ago, understood the psychological (for both the enemy and his own forces) significance of such easy victories, where the main goal was mass killings and chaos.
The more panic—the more demoralized the enemy.
The more killed—the more motivated his own subordinates are to continue the war with the Dominion.
Undoubtedly, the attack on the Aparo sector, the collapse of the HoloNet, and the mine barriers on routes leading to neighboring sectors are part of the overall plan to attack the Zann Consortium.
If so, then the defeat inflicted on the "Butcher of Atoa" would be significant and extremely painful.
Not only militarily but also morally.
The fast Star Dreadnought possessed by Shohashi is undoubtedly one of the few Dominion "super" class ships, the elite of any fleet.
Disabling, or, if luck smiles, destroying the enemy flagship would not only reduce the Dominion's military power but also deprive it of qualified and experienced personnel.
Who are always of greater value than the best pile of metal turned into military equipment.
One way or another, striking forces inferior to your own is the best way to destroy the enemy.
Personally, Sykes-Twenty Seven preferred to strike without meeting resistance than to get drawn into protracted battles against a strong opponent who could counterattack.
However the battle unfolded, inflicting a blow on forces that would be inferior to his own was the best way to destroy the enemy.
"Admiral, two minutes to exit point," reported the navigator from the other side of the bridge.
"Prepare to open the main comm channel," commanded Sykes-Twenty Seven, eagerly awaiting the moment the fleet would drop out of hyperspace so he could begin issuing orders.
"Will be done, sir."
A smile flickered across Sykes-Twenty Seven's thin, cracked lips.
He felt the familiar vibration of deceleration, and the view in the observation window beyond the combat bridge transformed from the whitish haze of hyperspace into the real darkness of space.
They had arrived at the far reaches of the Aparo sector, where solar gravity's influence was minimal, but only a few minutes' flight from the boundary mined by the Dominion Armed Forces, as designated by Shadowspawn.
Sykes-Twenty Seven checked the tactical hologram.
No enemy ships.
"Sir," the watch officer addressed him, "we are receiving a transmission from the fleet flagship from the Corporate Sector. They are in position and ready to begin breaching the barrier. They are inquiring about our status."
Excellent.
He had outmaneuvered his opponent.
"Dispatch light forces to breach the minefield along vector twelve," ordered Sykes-Twenty Seven. "Inform flagship Sykes-Twenty Eight that the ships are combat-ready. Equipment and slaves are in the destroyers' holds. The Lurrians are frozen in carbonite."
The reply took about five minutes to arrive.
After all, the minefield's width was considerable enough that even a powerful, enhanced laser beam couldn't traverse it quickly.
Sykes-Twenty Eight had also begun breaching the mine barrier.
In half an hour, Sykes-Twenty Seven had lost half his light forces but had advanced twenty percent through the minefield.
He had cleared sufficient space to begin safe movement through the minefield.
Triumph was near.
"Sir, we detect the emergence of four Star Destroyers off our stern," reported the watch officer.
"Identify!"
"They are Interdictors, sir!"
"Ours?" Sykes-Twenty Seven clarified, just in case, not really believing it possible.
"No, sir," came the expected reply.
Shohashi had brought ships to intercept his forces.
But he had sent too few destroyers here...
"The enemy is deploying gravity well projectors, sir."
"Deploy the Imperial and Victory-class ships to intercept the Interdictors," ordered Sykes-Twenty Seven. "Venators—begin moving along the cleared lane in the minefield."
Apparently, Shohashi intended to hold them here and bring in more of his forces using artificial gravity wells.
The distance between the opposing fleets was about fifty standard units.
Once the ten most combat-capable destroyers of his fleet completed their turn, he could engage any ships Shohashi could bring here with firepower.
One, two destroyers—it didn't matter.
Even if there were spy droids in the area, the Butcher of Atoa wouldn't have time to bring ships from distant systems.
And once the lane was ready, and the gravity well stations within the minefields were destroyed by the Zann Consortium's breakthrough forces, reinforcements from Corporate territory would leave nothing but a memory of Eric Shohashi's squadron.
The backup plan had worked.
Now he just needed to destroy the Interdictors and...
"Turn completed, sir!"
"We detect the emergence of an enemy fleet!"
"Destroyers, sir!"
"Heavy cruisers!"
"Crimson Dawn!"
Sykes-Twenty Seven was speechless.
Instead of seeing only the darkness of space, dotted with distant sparks of stars and nebulae, Sykes-Twenty Seven found a Dominion fleet arrayed before his ships, led by a fast star dreadnought, ready for battle.
And the number of Imperial-class Star Destroyers the enemy had amounted to a dozen.
Exactly the number of ships Shohashi had during his attacks on the Lur system.
Therefore...
Could it be that the Butcher of Atoa had anticipated Sykes-Twenty Seven's actions and realized he didn't intend to attack any system in the Aparo sector but planned to break out of the sector⁈
How could the opponent so effectively decipher tactics devised not only by Sykes-Twenty Seven, a clone of a famed commander from the Clone Wars who led the Zann Consortium to victory over an entire galaxy, but also by Shadowspawn, thanks to whom the organization had subjugated the best and most profitable part of the galaxy⁈
He thought: "This is impossible!"
Then he shouted at the top of his lungs:
"Shields to full power!"
But the enemy had already opened fire.
Two massive red streaks of ion charges disabled the pair of Imperial-class ships closest to the enemy.
Thus, Sykes-Twenty Seven learned he hadn't disabled all the Venators with ion cannons that Dominion Vice Admiral Eric Shohashi possessed.
The Butcher of Atoa had arrived at the trap prepared for him fully armed.
And why hide it now⁈
He had used Grand Admiral Thrawn's tactics.
He had set his own trap within the ambush meant to defeat his fleet.
* * *
The battle hadn't even begun yet, but Vice Admiral Shohashi, leaning on his cane, stood in the middle of the central dais of the Crimson Dawn, his eyes never leaving the observation monitors.
From the decrypted messages, he knew a fleet of five Star Destroyers of each type—Imperial, Victory, Venator—had left the Lur system.
Initially, the enemy also had nearly a hundred corvettes, frigates, and cruisers of various types.
But after the battle with the Dominion's droid-controlled assault fleet, the enemy destroyers had sustained non-critical but serious damage, though they remained largely combat-capable.
Meanwhile, the enemy's light forces had been almost forty percent destroyed.
The Crimson Dawn's central computer displayed seventy-one markers for enemy light ships.
Therefore, the Zann Consortium had a fleet of eighty-six starships of various classes.
But this data was current up to the point before the Red Star squadron appeared in this location.
Now the situation had changed—in Shohashi's favor.
Eric could oppose them with one fast star dreadnought, ten Dominion Star Destroyers—the latest "triples"—four Interdictors, and a dozen Vengeance-class heavy cruisers.
And two Venators equipped with w-180 ion cannons.
Second-generation Dragons, for which a single shot from the main battery was enough to disable any enemy capital ship.
"Activate gravity well projectors," Eric ran his thumb over the engraving of Iran Ryad and closed the lid of the archaic pocket chronometer with a distinct click. "Deployment direction: vectors six and seven, twelve and eleven. Begin jamming."
He felt no peace.
For some reason, the ritual that had become routine over the years no longer brought calm.
Though it no longer mattered.
The enemy ships hadn't fallen into the trap of the minefield's gravity wells.
They had exited hyperspace prematurely, indicating what Thrawn had said.
The enemy had prepared for a long time to break the blockade and managed to calculate the suppression boundaries for hyperdrive operation created by the gravity well generators scattered along the entire minefield separating the Corporate Sector from Aparo.
"Sir, we detect laser beam transmissions," reported a specialist from the communications compartment. "Directed along the Hydian Way."
"Towards the Corporate Sector?" Eric clarified.
"Affirmative, sir."
So Thrawn was right here too: the sector blockade was being breached from two sides simultaneously.
"Order the Dragons to begin targeting enemy starships," ordered Shohashi. "Imperials first, then Victories."
"The enemy has traversed forty percent of the mine barrier," the watch officer warned the vice admiral. "Venators are entering the cleared lane."
Eric looked at the tactical monitor.
The Crimson Dawn's scanners picked up information at a range of two hundred units.
The distance between the opposing fleets, accounting for mutual closure, was currently forty-five units.
Which the enemy's Victory-class Star Destroyers were actively exploiting.
Their generous missile salvos failed to reach their targets—the anti-ship self-propelled projectiles were intercepted either by covering corvettes or by the Dominion destroyers' own point-defense artillery.
The Dominion's own launchers weren't being used—according to Thrawn's information, Lurrians and the Dominion's necessary cloning equipment were on board.
And the interception rate for missiles at a range of forty-five standard units was high.
Therefore, the maximum range the scanners could currently "reach" was one hundred fifty-five units behind those ten Star Destroyers moving towards the Red Star.
The width of the previously established mine barrier between sectors was three hundred units.
In that case, it could be assumed that the Zann forces from the Corporate Sector side had also cleared a lane of roughly the same length as the retreating flotilla from his direction.
It wasn't for nothing he had ordered the gravity well vectors deployed to block both forward advancement and the enemy's flight into the Aparo sector.
These same measures would also hold back enemy reinforcements from rushing into the sector after breaching the minefield.
"Targets one and two hit," reported the watch officer. "Target three is maneuvering, targets four and five are changing course."
Eric understood why the commanders of the last three remaining enemy Imperial-class ships had done this.
Realizing the threat from the Dragons, they sought to use their damaged comrades as shields to close with the Dominion Star Destroyers.
And those were generously pummeling the enemy ships with turbolaser and ion artillery, not letting the Zann forces relax.
Meanwhile, the turbolasers fired exclusively at the enemy's combat-capable ships, and the ion cannons at those who had already lost power to their onboard systems.
A precaution to avoid accidentally allowing enemy Star Destroyers to "revive" after being hit by w-180 ion cannons.
Eric had only two Dragons at his disposal.
Though no more were needed.
The third Imperial and the first Victory were added to the list of Star Destroyers already disabled by ion shots from his squadron's Dragons.
"Strike element of the fleet—advance," ordered Shohashi. "Boarding parties prepare to seize enemy ships. Dragons switch to targeting Victories. We'll handle the enemy formation's flagship ourselves."
"Yes, sir!"
"Precision fire from all weapon types!" barked Shohashi. "Strip the target of shields and armament! Disable the ship!"
"It will be done, Vice Admiral!"
The Red Star surged forward across the entire front.
Each triple Star Destroyer advanced, frantically dousing the still-combat-capable starships of the Zann Consortium with fire from all guns.
Consequently, all ships except the Interdictors and their four covering heavy cruisers began closing with the enemy with a single goal.
Within their depths, shock troopers and combat droids prepared to attack the immobilized ships of the Zann Consortium.
Yes, they weren't facing Vengeance-class frigates or Aggressor-class Star Destroyers, which used self-destruct systems when threatened with capture.
But there were no guarantees that the crews of enemy ships disabled by ion shots wouldn't use the emergency or engineering reactors of the Imperials to blow up the ships, thereby preventing "their trophies" from falling into Dominion hands for subsequent use.
Only when the enemy ships were under the full control of Dominion shock troopers could it be said that neither the cloning equipment nor the Lurrians were threatened.
The Crimson Dawn closed with the enemy flagship, identified by numerous communication actions addressed to other Zann Consortium ships.
Powerful artillery salvos shattered the enemy's deflector field in seconds.
The remnants of its starfighter complement were mercilessly exterminated by laser weaponry and the starfighter wing of the fast star dreadnought of the Dominion Armed Forces regular fleet.
Eric informed the commanders of other capital ships to concentrate fire solely on exterminating enemy starfighters and maintaining ion control over the damaged Zann Consortium ships.
No closing with the disabled destroyers was permitted in case the enemy might blow up their own ships.
And at the same time, on the tactical hologram, one could see hundreds of transport and boarding starships erupting from the depths of the Dominion Star Destroyers to fly dozens of standard units and latch onto the hulls and emergency airlocks of enemy ships.
Some were meant to burst into the open hangars of Star Destroyers and deploy troops in landing sections, allowing shock troopers and combat droids to advance towards the most sensitive and dangerous areas of the ships.
The boarding parties broke through to bridges, reactors, engineering and engine compartments, and adjacent spaces.
The Crimson Dawn and its crew didn't need orders every time the situation changed.
The eight-kilometer giant hovered over the hull of an Imperial-class Star Destroyer drifting on inertia.
The powerless flagship of the Zann Consortium flotilla shuddered as invisible grips of tractor beams seized it.
The ship slowly bled off speed due to the counter-thrust of the star dreadnought.
And at the same moment, streams of boarding troops poured from the depths of the Red Star's flagship.
The ship coordinating the actions of all other starships in the flotilla had to be captured at any cost.
The faster—the better for the counter-intelligence officers, who would be grateful for the promptness and the opportunity to dig through the data preserved on the ship's computers by the time it was secured.
"Dragons—change basing echelon," ordered Eric. "Fire main battery for effect on enemy Venators."
The range still allowed it.
Shohashi looked at the tactical hologram.
The enemy had traversed forty-seven percent of the minefield.
And there its progress ended.
As did the light forces the fleet commander who fled the Lur system had at his disposal.
But this didn't mean the breach was eliminated and the blockade would remain intact for any part.
No.
This battle was merely a prologue to a larger one.
The Crimson Dawn's sensor systems detected the presence of numerous enemy starships attempting to breach the mine barrier regardless of losses.
Eric watched as the markers for gravity field generators forming part of the mine barrier winked out.
Only one installation remained.
And the enemy from the other side of the blockade would be able to jump to his fleet's positions.
Well...
He was ready for that too.
"Sir," the watch officer addressed him. "Sensor control reports that approximately sixty Victory-class Star Destroyers of both modifications have been detected on the other side of the mine barrier."
"Acknowledged, Lieutenant," Eric replied calmly. "Let them break through. We have the means to greet them."
"Yes, sir," the watch officer answered, somewhat abashed. "The Dragons report all five enemy Venators are immobilized and drifting towards the remaining mines in the lane cleared by the enemy's light forces."
"Don't worry, Lieutenant," Eric advised, watching the mine barrier thin on the tactical screen. "The breakthrough forces from the Corporate Sector have accelerated their breach actions. The immobilized starships won't be harmed."
"Yes, sir."
"Inform the Disrupter and the Detainer," he named the Interdictors blocking vectors eleven and twelve with their gravity wells, "to be ready to deactivate their installations and breach the superluminal barrier on my order. All other ships be ready to turn."
"It will be done, Vice Admiral."
The Disrupter and the Detainer controlled the zone at the very edge of the minefield on the Aparo sector side.
At the right moment, they would deactivate their installations.
And the only thing holding back the Zann Consortium ships breaking through from the Corporate Sector would be the two other Interdictors.
The Stopper and the Lurking in the Shadows.
But their vectors were deployed far from the zone controlled by the Disrupter and the Detainer.
Directly opposite.
Far in the rear of Shohashi's ship positions.
The enemy could clearly see that the Dominion side had Dragons equipped with ion cannons.
And saw that ships with precious cargo were being boarded.
They wouldn't waste time fighting through the lane in the mine barrier.
Not when they could jump.
Exactly where a trap awaited them.
Eric took the antique chronometer from his tunic pocket.
With a habitual motion, he opened the lid and ran his thumb over the engraving of Iran Ryad.
The Red Star no longer calmed the vice admiral.
Something had changed.
Not in her—she had long been dead.
But in him.
His heart no longer tore at the thought of her death.
Not after the death of the real Snow Queen.
One could say he had tasted the blood of the one who gave the order to destroy the love of his life.
Could it be that some part of his psyche decided the vow had been fulfilled?
No, that wasn't right.
Baron Fel wasn't in the grave yet.
When he died—then it could be considered that vengeance had been carried out as it should have been.
As promised.
But for now...
"Sir, the mine barrier has been breached," the watch officer reported with a slight tremor in his voice. "The Interdictors and other ships have received the designated orders."
Currently, the Crimson Dawn was positioned closer to the minefield than any other ship of the Red Star.
As planned.
And the fast dreadnought's sensors were as sensitive and long-ranged as ever.
"Gravio-acoustics register enemy ships transitioning to hyperspace!"
"Disrupter and Detainer, jump out," commanded Eric. "All other ships—launch Scimitars and set preliminary course one unit closer than vectors five and six. Attack immediately upon enemy starships exiting their jump."
"It will be done, Vice Admiral!"
Eric clicked the lid shut and put the archaic chronometer back in his pocket.
A grand battle was foretold.
* * *
The gloom of the quarters was dispelled only by the hologram of the battle of the blocking detachment under the command of Captain Valum Vigor.
The "guest of honor" himself silently watched the analysis of his actions, compiled from data obtained from buzz droids and spy droids launched from his own detachment's ships before the assault fleet ships went into action.
After the holographic Aggressor-class Star Destroyer and Vengeance-class frigate exploded, and an exact copy of the latter was swarmed by Dominion boarding ships, the hologram froze.
"Thank you, Lieutenant Colonel Tiers," I addressed my adjutant standing by the tactical holoprojector quietly.
Shifting my gaze to Captain Vigor, I inquired:
"How can you explain this? Why was my order to destroy enemy starships violated?"
The man, lips pressed together, stood ramrod straight, drilling the gloom of the ceiling bulkheads with his gaze.
"I gave the order to capture the enemy ship, sir," he stated clearly, loudly, without hesitation.
"I assume Captain Makeno did not act on his own initiative," I agreed.
"That is correct, sir," Vigor continued drilling the ceiling, not daring to look me in the eye.
Precisely and according to Imperial regulations.
You can recruit a person or accept a defector.
You can retain his rank.
You can conduct "advanced training."
You can hand him one of your state's most modern Star Destroyers—of which there are currently only five available and combat-ready.
You can make him and his comrades understand that no one holds a grudge for the past.
But you cannot understand his logic.
The order was simple and clear: disguised starships are to be destroyed in any case.
No alternatives.
But this commander acted differently.
I wanted to know the reason for violating an extremely simple and precisely formulated order first and foremost.
Because, despite disobedience of an order being a serious disciplinary offense bordering on a crime (depending on the severity of consequences).
But to understand how seriously the offender should be punished, one must understand what exactly motivated him.
Over the past year, there had been many cases where violations of orders were dictated solely by good intentions.
Take Vice Admiral Mora and the attack on the Kuat-subordinate planet Kai Fel, when he violated orders and inserted his own initiative into the carefully planned algorithm for capturing the planet and the hyperdrives we so desperately needed at the time.
He sat in a cell.
Explained himself.
Wrote a tactics textbook.
Now he commands a fresh, forming squadron for the second phase of the counteroffensive against the Zann Consortium's allies.
While intelligence identifies everything necessary for the attack, while sector borders and regional hyperspace routes are mined and other preparations for the assault are made, the new strike formation will be equipped and undergo combat integration.
But the question of what drove Vigor at the moment he sent our special forces-trained boarders to assault the disguised ship remains.
Could he have guessed that our special forces were sent to his ship not for anti-boarding combat, but to, if necessary, subdue both him and his former comrades-in-arms from the military service of the Five-Star Commonwealth, who were part of the **Raider's** crew?
No, unlikely.
**Makeno** is not one to chatter — when it comes to mission execution.
So here it's either "good intentions," or plain stupidity, or — an underestimation of the danger.
The situation needs to be clarified.
"Sir," Captain **Vigor** cleared his throat into his fist after listening to my question to the end. "I understand that my actions posed a threat to anyone who boarded the enemy's cloaked ship. But risk is part of our profession as military personnel."
Quite correct words.
"There's a difference between risks, Captain," I reminded him. "The risk of dying in battle for a simple **Soldier** is much lower than for the special forces squad you sent to storm a ship equipped with an actively used enemy self-destruct system."
"I understand that, sir," the commander of the **Raider** agreed after a brief silence. "During my advanced training, it was brought to my attention that the **Zann Consortium** blows up its ships when threatened with capture by the enemy or lures prize crews onto them, after which the reactor and ammunition are detonated. However, I analyzed the enemy's tactics and concluded that conducting a covert operation with stealthy penetration onto the enemy ship, diverting its attention with an attack by our ships to facilitate access to the reactor — the primary threat of self-destruction — and its subsequent capture. The enemy starship was deprived of the ability to maneuver and fire. After which the ship was subjected to **Ion** cannon fire, followed by a full-scale boarding."
"That's a statement of facts, Captain," I said. "Nothing more."
"Yes, sir."
One cannot deny the elegance with which this operation was carried out.
But one also cannot ignore that it was implemented contrary to the prevailing order.
"Do you consider your order correct, Captain?" I inquired of the **Raider's** commander.
This time he needed a few seconds to answer.
Not to come up with it — Captain **Vigor's** face already made his attitude towards his actions clear.
He was choosing words for the appropriate form of expression.
Which could speak of him as a tactful person.
Or as a cunning person who chooses words to avoid being found guilty of a serious offense and not incur deserved punishment.
Understanding the difference isn't difficult.
It would be enough to hear him appeal to my own actions and cite distorted facts.
"My order contradicted yours, sir, which is unacceptable," said Captain **Vigor**. "I acknowledge this fact and am prepared to bear responsibility for my actions and the consequences that resulted."
"Excellent," I nodded, looking at **Tiers**. "Lieutenant Colonel, document the fact that Captain **Vigor** is subject to disciplinary action for violating the order of a superior officer."
"Yes, sir."
A shadow appeared on **Vimar's** face, clearly visible thanks to the hyperspace glows illuminating the quarters through the viewport.
And thanks to the subdued lighting.
"Furthermore," I continued, "note that the Captain is to be commended for developing tactics for capturing large enemy starships equipped with cloaking fields."
Now surprise appeared on the **Raider's** commander's face.
"Captain," I addressed **Vigor**, "after the **Guardian** clears the light barrier, return to the **Raider** and resume command of your destroyer. Additionally, by the end of the month, the regular fleet headquarters and I personally will expect a detailed report from you."
"On what subject, sir?" the officer forced out.
"Your tactical maneuver requires study and, if necessary, refinement," I explained. "The approach is useful. And the fact that you captured a combat-ready and practically undamaged enemy starship with cloaking equipment, in violation of a superior officer's order to destroy enemy ships, does not negate your merits. However, I must warn you: next time you may not be so lucky. And the gamble may not pay off. I hope I have made my view of the situation clear?"
"Perfectly, sir."
"Dismissed."
"Yes, sir."
Spinning on his left heel, Captain **Vigor** left my quarters on barely bending legs.
Only **Tiers** and I remained.
"Sir," the latter addressed me quietly, "this case could set a precedent for other commanders. Misinterpreting cause and effect will lead to an increased number of gambles among ship and formation commanders."
"All true, Lieutenant Colonel," I agreed. "However, you are precisely the one responsible for Captain **Vigor's** punishment. And it is within your power to ensure that subordinates understand exactly what I mean by simultaneously punishing and commending **Vigor**. The story of Rear Admiral **Mor** is beginning to be forgotten. Which is inevitable, given the dilution of personnel. It's necessary to remind them that orders must be followed. And that they are given based on purely rational considerations. Therefore, don't forget to include a thoroughly justified rationale for both decisions — both the punishment and the commendation. Everyone who studies the order must understand the thin ice **Vigor** walked on. And, in fact, he is being commended for what his subordinates did, not for what he himself did. Yes, add Captain **Makeno** and his subordinates to both lists."
"Yes, sir."
"Victors are not judged" — that's nonsense.
Victory at any cost, or through heavy sacrifices, or due to unjustified stupidity — that is not something to be encouraged.
Rewarding idiocy is a signal to subordinates that you are guaranteed to get a commendation no matter how you stumble your way to the coveted victory.
Incorrect explanations and motives for commendations and punishments lead to a misunderstanding of how the mechanism works.
"Rewarding the uninvolved and punishing the innocent" — is not our method.
Both **Makeno** and **Vigor** violated a direct order — inevitable and severe punishment will follow.
But both planned and executed an operation that allowed us to develop tactics that are sometimes as necessary as air.
As soon as headquarters and the tactical and strategic analysis department receive the report from **Vigor** (I already have **Makeno's** detailed report), they will work through the situation and produce a digestible methodology outlining optimal actions.
"Since we've touched on the topic of 'dilution of personnel,' let's move on to the matter for which we came to **Lur**," I said. "Have you received precise data on the actions of the 501st Legion?"
"Yes, sir," **Tiers** placed an information chip on the table. "Effectiveness is high, casualty numbers are slightly above the norm based on the peak activity of the 501st during the Empire's time."
"Above or below our own statistics?" I clarified, connecting the chip to the receiving port.
"The current composition of the 501st is operating more effectively than immediately after its formation last year."
"Casualties among the latest reinforcements?"
"Slightly higher than those of the 501st veterans," said **Tiers**. "But this is explained in part by the fact that the legion in its current composition is experiencing combat conditions for the first time."
"Conflicts between veterans and new recruits?"
"Not a single one, sir. However, there is a certain wariness among veterans towards the recruits."
"Which is logical," I said. "Everyone knows perfectly well that we do not control **Kamino**, the DNA source for the **Grand Army of the Republic** has been dead for over thirty years. But at the same time, new clones of **Jango Fett** are appearing in the 501st. Their concerns are understandable."
"Yes, sir. I came to the same conclusion."
It took me a few minutes to study **Tiers's** report and the attached reports from regimental and battalion commanders.
"So," I concluded, looking away from the monitors. "Combat effectiveness fits quite well within the statistics of **Dominion** clones. Mental disorders?"
"Not manifested, sir," reported **Tiers**. "Identity crisis, psychosis, mental disorder — not detected."
"And yet," I reminded, "Doctor **Zyix K'zzt** warned that standard weeks are the timeframe for the development of personality-body conflict. The new clones passed this mark without issue. Cognitive problems were also not detected, dementia is absent."
"Yes, sir," **Tiers** nodded.
"Based on the available data, it can be concluded that the **GeNod-Dominion** project using **Boba Fett's** DNA and the imprint matrices of his father's clones, produced using **Kaminoan** technology, are resistant to combination," I summarized.
"Yes, sir," **Tiers** confirmed. "We have full-fledged sources of replenishment for **Snowtroopers**, marines, sappers, 'burners,' medics, and 'sandmen.'"
"All true," I agreed. "Considering the base of **Shock Troopers** who came into our service along with the former Inquisitor **Obscuro** on **Vjun**, a significant part of the **Shock Corps** specialization can be restored based on the conducted tests."
**Tiers**, as the curator of the **Dominion's Shock Corps**, has done a lot of work optimizing **Shock Trooper** specializations.
And the so-called "marines" are no longer **Shock Troopers** stationed on spaceships for boarding and anti-boarding activities, as it was under the Empire.
These are precisely **Shock Troopers** trained for operations in coastal zones and on the surface parts of oceanic planets.
We haven't managed to return many **Jango Fett** clone **Shock Troopers** to the 501st.
Primarily — these are **Snowtroopers**, operating on planets like **Lur** and **Hoth**.
"Hazardous" **Shock Troopers** are trained and equipped for work on planets with a high degree of adverse environment: radiation, acid, volcanic rock, and so on. This category includes the notorious "acid troopers," whose armor is identical to Imperial **Shock Trooper** armor for work on volcanic planets, radiation zones, etc. The difference is only in the training program for these clones, and even that is minor. But separating them into different units is unwise, given the circumstances — an unaffordable luxury.
We cannot afford to "split" the budget to create several types of **Shock Troopers**, equip them with one type of gear in different forms, just to report on their special need.
**Shock Trooper** "burners," they are the direct descendants and ideological followers of clone flamethrower troops.
Sappers and medics...
Well, it's clear who they are and what they serve for.
"However, we still have a problem with staffing **Assault Commandos**," I reminded.
"As well as a number of other **Shock Trooper** specializations," **Tiers** agreed. "Intelligence is searching for **Jango Fett** clones who could be useful in restoring these areas of activity."
"Results?" I inquired.
**Tiers** was silent for a second.
Which was very unlike him.
"Lieutenant Colonel?" I inquired.
"The scouts checked the information from your agents," **Grodin** 'measured out.' "Indeed, a whole community of clone deserters from the **Grand Army of the Republic** has been discovered on **Mandalore**. Not all could be identified, but individual representatives of Elite Republic Commando types like **Null**, type **Alpha**, as well as fighters from **Delta** and **Omega** squads were noted. All of them were somehow connected with the Mandalorian mercenary, former instructor named **Skirata**."
One might think this could surprise me.
"Did they make contact?" I inquired.
"No, sir, only remote observation."
"Continue tracking," I ordered. "Is it **Bravo-Eleven** that is searching for deserters on **Mandalore**?"
"Exactly so, sir," **Tiers** confirmed. "There is other information from **Mandalore**. Related to Jedi."
"Interesting," I didn't hide the obvious. "I take it that Jedi, with whom they previously worked, are also with the deserters?"
"All true, sir. But that's not all," **Tiers** continued. "As far as agent **Bravo-Eleven** managed to figure out, in this same community, not only do the clones not look their age of deep old men, but there is also suspicion that the young man living with them is the son of one of the clones. And a female Jedi."
"Well, how about that," I said.
So this part of the universe also coincides with the reality surrounding me.
Maybe it's time to stop being surprised by this, but the habit of double-checking information hasn't gone anywhere.
"All data is on the chip, sir," said **Tiers**. "Along with the personal files of the deserters and data on the Jedi."
"Thank you, Lieutenant Colonel," I replied. "Continue the work of searching for other **Jango Fett** clones. We need to close the gaps in a considerable number of specialties."
Not to mention the fact that we simply don't have a **Jango Fett** clone of the most common specialization.
We don't have a **Jango Fett** DNA **Shock Trooper** infantryman.
Which is quite understandable — they die in the greatest numbers on all battlefields.
Yes, specialized clone **Shock Troopers** have general military training, but...
How wise is it to use a chisel or a hacksaw as a hammer?
"May I give the order to expand the cloning of **Boba Fett**?" asked **Tiers**.
Yes, we have very few **Shock Troopers**.
And those we have are spread in a thin, thin layer across the regular fleet ships.
So thin that we had to use **Kavil's Corsairs** and Mandalorians as ground forces in a huge number of battles in the first phase of the counteroffensive.
"Yes, Lieutenant Colonel," I said. "Provide the newly formed legions of new clones with Phase-II **Grand Army of the Republic** uniforms. Assign the active legions the status of guards — they've earned it. **Boba Fett** clones will fill the newly formed regular units."
This way we can at least distinguish them from each other.
Because those productions of Imperial-design **Shock Trooper** armor that we have can't even handle the meager volumes of our own **Shock Trooper** intake.
In the end, we will come to uniformity of uniforms for our **Shock Troopers**, regardless of how and when they were produced.
The question is only when the comparative tests of the **Empire's Shock Corps** armor sets and that Clone Wars heritage we have in storage will be completed.
There is a suggestion that some clone armor sets, after appropriate modification, will return to service.
And the galaxy will shudder, seeing the face of **Jango Fett** in Phase-II armor sets once again.
But for now...
"Grand Admiral," the comlink erupted with the rapid speech of Captain **Pellaeon**. "In ten minutes we will arrive at the designated point."
"Acknowledged, Captain," I responded. "Sound battle stations."
Time to finish this blitzkrieg.