The Six-Eyed Beast - Cover

The Six-Eyed Beast

Copyright© 2025 by BenLepp

Chapter 31: The Ship who Cried Wolf

February 25th, 2279

When the alarm came in, they were as ready as they could be. All blast doors went down, all crew were inside the citadel (only the much-suffering bots stationed outside), the gunports were opened, all systems set at max charge, all teeth clenched. The first step was observation. Soon, a massive object appeared on the passive scanners, and imminently, it became clear that RND had given the Maka information on the Rubicon, for the Maka was zig-zagging. A clear sign that she knew her opponent had mines, as most modern Senatorial vessels didn’t have mine chutes anymore, designed to fight in the battlewall. Sure, it could have been the AI itself coming up with the possibility that an unseen attacker would use such an unsavory weapon, but Perlas initiated the misleading cloaking field anyways. Otherwise, there wasn’t much to see they didn’t already know about a Sentir-class vessel, so they sent out the message that would start the 72 hours timer, which was the first nerve-wrecking moment, as the Maka instantly turned in their general direction. She had also received the GO, and correctly assumed (or known) the enemy ship would be coming from Kappa 3, although the Rubicon, as usual, didn’t arrive at the point they would in a direct line, as per Basil’s principal orders. Still, the Rubicon had to change course hard to stay outside effective scanner range of the Maka under cloak and fell into a distant pursuit course. It was time to stab the dragon and see what it would do.

The first test was simply firing a lone torpedo from out of range at the Maka. She simply changed course a little, let the projectile pass and scanned it thoroughly, receiving misleading information, as Basil had fired a much smaller, slower torpedo with a much weaker payload. The games had begun.

The second test was flyby by the Toucan under cloak. At almost exactly 0.34 clicks the Maka reacted and unleashed a hail of beam fire and small but quick and well-guided torpedoes on the Toucan, which immediately evaded, being on autopilot with full reverse engines already firing. It was narrowly missed and started fleeing, sub-light, it was much much faster than the Maka but the latter surprised everyone by simply using the quantum slipstream to jump to a point in front of the fleeing cloaked ship, the Toucan only surviving because Ivern remotely ordered it to do a hard turn and burn in a random opposite direction whilst the Maka was coming out of the jump still, losing a precious half-second and scanner distance to the cloaked target. As much as they were happy to see the Toucan survive, it was suspicious how quickly the Maka could charge up her quantum engines, with almost no warning given to an observer, she could jump half a second earlier than the Rubicon could, which seemed to be an advantage of the new D-10. There was a lot of sweat on the officer’s faces after this, but Boddins, watching from the medbay feed, was happy to see such a careful approach, as he had seen with Basil before. Maybe he would let him continue.

The third test was a bit riskier, as the Rubicon tried her first pass at the Maka at the maximum speed she could still fire off her payload and turn away from the hulking vessel in time without touching shields, as Ka’al’s plan was still considered insane, even though theoretically, the Rubicon could survive a ramming attempt at battle speed, just not the crew aboard her, as the dampening systems would be overcharged in milliseconds. The Rubicon having a larger cloaking field meant she was already detected at 0.5 clicks. As she was coming in hot, the Maka fired very accurate torpedoes and beams into the Rubicon’s launchers – or where she thought they would sit. Their suspicions had been confirmed, not only did the Maka know about the mines, she also knew where to fire into a cloaking field, way before her scanners could determine the real outlines of the flat vessel approaching her. Still, it was a beating they took, as the Maka soon corrected her salvos to a wider spread, landing lucky hits and more accurate hits the closer the Rubicon got. The Rubicon’s answer was a full 36-torpedo salvo into the front-third port shield of the Maka, which the Maka was unwilling to endure, surprising everyone. She just jumped forward a few clicks and immediately started turning to follow the attacker, which panicked and also went to jump speed, dropped a flash and changed course, losing the pursuer. Both ships learned very important lessons on each other in this instance: The Maka needed even less than half a second to charge up her jumpdrive (she had not shown her full potential against the small enemy), and the Rubicon was able to change course under cloak and within the slipstream by manipulating the quantum field ahead of her in relation to the one in her core without dropping out and back in, something other ships avoided for the strain it put on the hulls, which was of no concern to the Rubicon (something the AI now feverishly tried to calculate and account for). Also, the Maka’s shields had been hit by eight of the Rubicon’s heavy torpedoes but only degraded by around 22%, which meant that a single salvo of 36 would not always pierce her shields, even if she kept stationary against all sanity and even if she did that, there were no torpedoes left to do actual damage to the ship in a measure that would justify the risk. Damage to the Rubicon was minor, only the armor around the starboard ions had been hit several times, but taken it well.

Then, there followed a pause, where the Maka returned to her course, happily zig-zagging around and Basil returned to his quarters, slightly worried about his prospects and scheming to get rid of Boddins, as it was not very likely to claim victory without insane risks.

Boddins immediately became a problem after finding out Basil’s next order, which was directed at Nocks. She was supposed to get as many neutral ships into the vicinity as possible. That was done by offering a tax-free trade line for a week that passed through the AOO of both ships, by going to the pirate lines and telling them about it, and by inviting many scavengers to take apart a juicy wreck that was said to have been discovered. They also faked the start of an illegal race – many of such races between youngsters going on – where the fastest ship around a set course of buoys would win the slowest ship. These races were illegal simply due to the high occurrence of pirate attacks or participants opening fire on each other, Ton being a regular organizer of such races, having once more been recruited by Basil under the promise of a – this time maybe real – juicy wreck to plunder, if the Rubicon won. Ton was hiding his ships in nearby systems, waiting for orders or the joy of seeing Basil die for his arrogance.

In short, the general area was slowly crowded with more and more ships, the Rubicon sending out lie after lie to get them there. Boddins protested at using civilians and criminals as a distraction, but Basil argued they were just there to prevent the mimic from being too obvious, for if only one ship suddenly appeared sending for help, the Maka would surely figure out it had to be the stealthy attacker.

The fourth test, by now less of a test and already a real attempt at dealing and risking damage (Basil simply called them “tests” for as long as possible to keep his naysayers at bay), came after the area was populated with a lot of very different ships looking for very different things. The pirates were careful though, pretending to be freighters, as they were very much out in the open and also suspicious of the number of vessels and the heavy cruiser patrolling the area in strange fashion. The Rubicon left the immediate scanning area and came back as a rusty old and very wide freighter. Old Rusty traversed the AOO for a while, before belching out a lot of radiation from the port engine and signaling SOS, turning on its own axis at a standstill, creating an irradiated disc around the freighter. The other ships, as had been predicted by Basil, were very weary of pirates, as this was a usual trap. The Maka feared no such thing and closed in. Now, the AI was considering the safest angle of approach, it was surely not the irradiated area, as this would interfere with the scanners for too long, possibly missing a mimic or a cloaked mine. She decided to appear above the freighter, offering to send maintenance drones but then immediately rescinded that offer upon closer scans of the freighter, which turned out to be the Rubicon looking up to her, ready to fire. The Maka, finding itself in a manageable situation that was however created by the enemy and therefore offered unknown variables, chose to jump again, which Basil had seen coming, as the Maka jumped right into a hastily repositioned minefield swooping up from the mimic’s limits, hence why they chose such a wide freighter. The minefield, however, was only partly in place in her course, since she had detected the mimic quickly by avoiding the spreading radiation. Basil had been a tad too optimistic. Still, her frontal shields took a beating as she jumped through some of the mines, but nonetheless, she stopped soon after, turned broadside, closing back in on the Rubicon. To the AI’s great surprise, the Rubicon had – instead of running again after being discovered – used the time the Maka was blind whilst jumping into the slipstream to come about hard, decloak, and point itself at the Maka’s bow, accelerating at her usual, unimpressive rate. As the two ships closed in, almost at effective range, the Rubicon did the shortest jump her quantum engines would allow her and reappeared right next to the incoming port front quarter turned towards her for the broadside attack. The resulting exchange of fire into the weakened forward shields of the Maka resulted in one penetration that took out the heavy beams – the long-range weapons – but it took the Rubicon painfully long to turn away enough to jump out, constantly being hit by an insane barrage, losing half her lower beams and two launchers. Interestingly, the Maka didn’t pursue, as it seemed that her long-range scanners – which could not be anywhere but in the front of a vessel for practical reasons – were at least temporarily out of commission, unable to track the jumping Rubicon returning to cloak, the scanners having been Basil’s actual target, unbeknownst to his crew.

Another pause followed, the first 24 hours of the test running out, with the Rubicon losing a third of her forward firepower and many beams and the Maka losing her heavy beams, some bowward structural integrity and the aforementioned scanners in the front, which meant the obvious angle of attack now lay at the bow of the heavy cruiser, although unlikely to contain the CPU core. Both ships were aware of this, so the Maka increased her forward shields to maximum, redirecting every shield generator a bit forward, leaving a weak point in the rear.

On the Rubicon, apart from trying to repair her damage in the field, a debate was now raging if the weak point in the rear was a trap or just a necessity. Basil decided it was a trap but worth going for, getting him into another discussion with first Nasz who wanted to count this as a nil-nil and give up and then Boddins seeing the increasing exchange of deadly fire. Interestingly, Nasz had gotten her sidearm from her ready room, since Basil was clearly out for blood, increasing the fight to an inevitable climax.

The fifth attempt followed a few hours later, with some repairs done to the Rubicon, even one launcher back up, meaning she could dish out almost the same damage as before. They largely followed Mellir’s plan and detonated a full 12 radiation mines, dropping them around the Maka’s course under cloak, out of short scanning range and therefore clear sight, quickly swinging to the rear of the enemy vessel as the radiation spread in the general area. The Maka chose not to jump out, which should have been a warning to Basil, who still risked the run. The Maka’s ion stream indeed was distorted and the Rubicon was sneaking up to fire into the weakened spot of the shields, until the Maka overcharged her ion engines, peppering the front of the Rubicon with radiation, making her clearly visible on the scanners and almost overheating the front equipment. The Rubicon was caught in a bad spot, as the Maka quickly turned to starboard, blocking the Rubicon’s jump route and opened a broadside at the close enemy, the Rubicon finally turning to jump out, but only after receiving crippling hits to a further three launchers and some upper beams.

Again, the Rubicon retreated for repairs and a frustrated Basil hid in his quarters, unavailable to the crew.

The sixth attempt was a modified version of Perlas plan, since they only had 2 launchers left, it took them several hours to generate and prepare a full salvo of 45 torpedoes, 39 of them now following close to the Rubicon’s hull within the cloaking field. Another few radiation mines were dropped but the Rubicon didn’t use the distorted ion stream of her opponent this time, she came in frontal and launched all 45 projectiles against the reinforced shields, achieving two penetrations with torpedoes that were launched a fraction of a second later, set to penetrate the already weakened decks and explode as far into the Maka as possible. The problem now lay in turning and having to pass the Maka whilst trying to jump, wherein the Rubicon lost her final launchers and the rest of the beams to the accurate fire of the broadside she was passing at very close range, even receiving some hits to both the ion engines as well as the quantum plates. The Rubicon was now without weaponry.

Legally, the fight was over but in the fraction of a moment before the Rubicon managed to jump out against the direction the Maka was facing (with good prospects of escaping even if she had switched to other scanners or repaired some), the Maka kept firing after destroying all weaponry, aiming for the position of the core of the Rubicon, deep withing the ship, in a clear attempt at destroying the vessel after burning through the armor. There was no doubt anymore, her orders had never included letting the Rubicon escape.

The damage to the Rubicon was intense, several internal systems had ruptured, several crew members injured and only one of the launchers looked like it could be repaired in time, plus the port ion engine was damaged and running rougher, making them a clearer target even under cloak.

Nasz decided to pull the plug. She got up from her tactical workstation, hand on her sidearm and approached Basil, who knew exactly what was coming.

- Captain, we’re out of the game. Also, the Maka didn’t cease fire after we were disarmed. She’s gone nuts or your fears were justified. As XO, it is my duty to stop you when your actions are a clear danger to the crew. Please accompany me to doctor Boddins for an evaluation of your capacity to lead.

Ah, that’s their plan. All by the book you assholes.

- Commander, if you want me out of this chair, you’ll have to force me.

Basil was sitting in his chair, unarmed, so it seemed like not much of an issue for Nasz, who was even physically superior to Basil. But Mellir was aiming at her with his rifle. He finally saw his chance to prove himself to his captain, his mentor, his torturer at times.

- Ensign, put down your rifle.

- I can’t do that commander. The way I see it, we’ve been making steady progress where you saw no chance. In my opinion as chief of security, you’re the one acting against standing orders from the Senate.

A voice came over the intercom, it was Boddins.

- Mellir, stand down. Your captain is on high doses of illegal substances and unable to see reason at this point. His pride will not allow him to stop until we’re all dead.

- Ah, we all know. He’s been juiced up from the start and has gotten this ship further than anyone...

Nasz had reacted quickly, what Mellir had started to say showed that the time for negotiations was over. The Security Chief siding with Basil was something she could not accept in this situation. Her stun shot hit Mellir right in the face and the cyborg went down, twitching. Some moments passed, and he kept twitching.

- YOU FRIED HIS FUCKING FACE IMPLANT NASZ.

Nocks could get really loud. She wasn’t really reacting much to the whole debate on continuing or not, waiting for her chance to hack the damaged Maka, but she did know Mellir better than Nasz, which was her measure of all things.

- Get him to medbay immediately, commander.

It was Nocks giving orders to her confused superior, as nobody else had taken Nasz’s side besides the frankly useless Boddins in medbay. Nasz just stood there for a while, looking at the twitching Mellir, before informing Boddins a critical patient was coming in and carrying the jerking body out of the bridge and to medbay, showing how easy it would have been for her to overwhelm the formerly trained and formerly quick Basil. Boddins also had no choice, if a critical case was brought before him, his oath compelled him to ignore all circumstances and save a life. Nocks quickly deactivated some of Mellir’s implants, not only to prevent further shooting once he woke up but to prolong treatment time. Perlas was shocked at the violence, but decided to stay on the bridge, keep the cloak and mimic running at peak trickery and simply stun the captain if he went too crazy. Ka’al considered joining the mutiny for a moment out of aged spite for Basil, but then decided it was too much fun to be in this fight and his chair. Korolev had her own reasons to never jeopardize her position on this ship, no matter how dangerous it got, it seemed better than being on her own. The captain spoke into the intercom.

- Deputy Ellip, find Commander Nasz and escort her to the brig. Then make sure Dr. Boddins does not leave medbay for the duration of the mission.

Ellip, running from the security station down to medbay immediately saw her direct superior twitching and even sparking a bit, decided that the orders must have their reason and disarmed Nasz quickly, much to the surprise of the Catanian, who had not expected another crew member who had joined them late to immediately take Basil’s side. Soon, Nasz was staring at her own reflection in the brig – it still smelled like pirates in there. Boddins was cut off from the intercom and Ellip guarded the door. The reason Basil had snooped up Ellip on Kappa quickly was that she used to serve on a frigate called SFF Pegal, where a group of officers had tried to take command of the ship due to their captain, a very ill Sii suffering from branch rot, giving more and more insane orders. Ellip was low-ranking in security but refused to break the chain of command for hours, for which she was dismissed from the ship and demoted down to deputy. For some reason, Sam Ellip would always uphold the status quo, of which Basil was the top dog. Why Sam Ellip was like that was of no interest to the captain, he had simply seen disagreements about the mission in the future and solidified his standing with security, even acknowledging Mellir as a “cloudwalker”, a term that usually made him chuckle.

Feterni and the engineers heard about the events from Perlas directly via discrete comms, but were assured that the Axxi would step in if things got even crazier, so they shrugged and went back to work, trusting in the ship they built to get them through this. The rest of the crew went into waiting, as Basil had retreated to his quarters for his final attempt, as the repairs to the one launcher they could save would bring them close to the final hours of the field test.

4 hours before the field test was slated to end, Basil was finally ready. He had gotten rid of both annoyances, the rest of the crew still followed orders, there were many ships in the area and the Maka seemed to still have problems with her long-range sensors, as he decloaked the Rubicon at long range for but a moment but the Maka didn’t react. His next orders would be so disturbing to the crew, Nasz had actually done him a favor, as everyone was aware of the consequences of disagreeing now. Especially Ivern and Feterni now had to shut up and follow orders. He looked at Perlas, who was already studying him with a few eyes.

- Perlas. Do you trust me?

- I trust that I will be able to understand your reasoning in the coming hours, Sir.

- Good enough. I’ll talk you all through it. Get me Ivern and Feterni.

Over on the SFC Maka, the mood – if it could be called that – was great. A lot of lists came out with green results. Only the destroyed frontal beams and the fact that the Rubicon had lucked into hitting both heavy sensor arrays twice were put down as a loss, otherwise, by points, this was over. Acceptable damage to herself and crippling damage to the enemy’s ability to continue the fight. The CPU felt it most likely the enemy would simply run down the clock to stay alive. The Maka kept having a look around at all the vessels buzzing around, some scanning intensely for something the Maka wasn’t informed about. Likely a diversion tactic by her opponent, she calculated no possible danger to herself from that.

Then, Commhub 206d went dark, the connection towards Kappa 3. The CPU calculated that it was either the pirate ships in the vicinity she had identified by their fake registrations earlier, before the long-range sensors went dark or a simple malfunction, as 1 in every 20.000 commhubs malfunctioned per quarter. She calculated no possible danger to herself from that. She considered investigating, but as Commhub 206d lay slightly outside the given AOO, she preferred to wait and attempt repair after the mock battle was over or the opponent was destroyed.

Next, Commhub 206b went dark, the connection towards Virginis, which now had to be directly contacted at max comms range. The likelihood of a technical failure multiplied with itself and was stricken from the list of possibilities. She still calculated no possible danger to herself, but a query was opened. There were three logical options, one, being the most likely, was the opponent, as although the 2 hubs were too far apart to be attacked by the same ship in that timeframe, the opponent had a small cloaked fighter aboard. The second option were again pirates, much less likely since there wasn’t much material to be gained from simple commhubs. The third option was someone else, a previously uninvolved party, completely separate from the current mission objective. Most unlikely, since there had been no reports or warnings of organized groups beyond some pirates in the area, but the possibility still appeared on the list. Minor percentages were given to cosmic events, maintenance shutdowns that weren’t communicated, or a malfunction of the Maka’s own, well-checked comms equipment that had been found to have no damage.

Just a short while later the SFC Maka noticed a lot of the ships she had on short-to-medium range were leaving the area in roughly the same direction, going towards the center parts of the League’s territory at high speeds or whatever their top speed was. The repair bots were still struggling to get the long-range scanners up again, since very sensitive materials and components had been destroyed, repair was only realistically possible after returning to space dock. The Maka’s CPU decided to hail a freighter nearby, asking for the reason of the sudden course change of several different and unconnected vessels. It received no response. The database showed that ships only reacted to about 67% of comms attempts from League vessels, so the Maka tried the next vessel, which also did not respond, even changing course away from her a little. The third vessel finally responded, saying there was some kind of “trouble” in the opposite direction, and that the Fleet “should do their job instead of asking stupid questions”. The Maka decided to follow the advice and move in the suspected direction of the “trouble”, but also to remain within the AOO for the remaining 3 hours, to not give the opponent a reason to declare victory on a technicality, as she wasn’t allowed to be attacked outside the AOO and could be seen as running down the clock herself.

The next ship she came across was sending out a weak distress call, having been attacked. The hull showed strange damage, stemming from an unknown weapon, as if a fusion reaction had taken place against the outer lining, vaporizing parts of the hull. The ship was empty, all shuttles gone – but it was not a mimic, it was real. The registration checked out; it was a freighter licensed to a Fellian company.

More and more chatter came in, showing evidence of a widespread attack. As the Maka kept moving towards the chatter, wreckage appeared on the scanners. A large freighter had been completely destroyed, again by the same strange fusion weapon. It used to be Tillin and as she got closer, remaining biomaterial was evidence for having had a crew aboard. It was impossible to determine the registration due to the damage to the ship.

Another distress call came in, this time from a colony of settlers on one of the larger rocks in the Virginis system, one of their neighboring colonies had been wiped out by a strange ship. This was outside the AOO and now at max comms range but the Maka responded to gain intel and received a grainy and distorted feed of the attack, an indeed unknown design of small warship had fired an energy projectile, which ignited against the populated asteroid and cracked it into multiple pieces.

The Maka was at a loss at explaining this, as by her calculations, at least 5 ships would need to be involved if this was a distraction by her opponent. One ship each would have to attack a comms hub, one ship each a freighter and another ship the far-off colony. More proof was needed. As the Maka kept going towards the calculated center of all these events, out of all ships, her designated opponent, the Rubicon came onto the sensors, but it was not alone. The Rubicon was firing two of her obviously now repaired beams at the strange type of vessel that had also attacked the outpost. The Maka could not say with certainty if it was the same vessel or a vessel of the same class and build. The nimble vessel stuck to an area behind and slightly under the Rubicon and fired an energy projectile, not much unlike what the database showed the Oopids to have used in the last war. As the projectile connected to its target near the hangar bay of the Rubicon, a catastrophic explosion shattered the cruiser, blowing out the hangar bay door and the port ion engine. The Rubicon lost all power and started drifting, sending out an automated SOS signal. The unknown attacker turned to engage the Maka, firing off another projectile, which luckily detonated prematurely in another one of the already observed fusion detonations for unknown reasons, blinding the Maka’s scanners for a bit. Then, the attacker dove behind the drifting Rubicon, putting themselves, the drifting medium cruiser and the approaching heavy cruiser on one line, which hindered the Maka’s view onto the attacker. As the Maka passed the Rubicon, she scanned her intensely, and found the ship to be without power, destroyed weaponry, and unable to move under her own power. Which meant the Maka had won the engagement and could now carry out the add-on “delete upon completion” order to eliminate ship and crew of the Rubicon. The problem was that this order also specified not having any witnesses, and as she fully passed the wreck of the Rubicon, the strange attacker was gone, likely cloaking. At the same time, two more reports of attacks came in, one even from a pirate vessel not far off asking for assistance, the other a liner being pursued by an unknown ship. Calculating the risk that someone was watching on their scanners, the Maka just held position, yet unable to fire at the Rubicon to finish her off, waiting for the other ships to leave visual range far enough as to not be able to record the Maka firing at an allied vessel. The Rubicon meanwhile was drifting and frantically sending some encrypted line of code to the Maka, several times, over several channels. Then, she hailed her on an open channel.

- This is the Rubicon. SFC Maka, stand down. The test fight is over, the Senatorial League has been attacked by the Oopid-Seki. We are at war.

Calculations aplenty were running within the Maka’s CPU. They were nowhere near the Oopid-Seki’s space, but then again, it was within the files of the ship that enemies tended to strike soft underbellies as one cited admiral had put it. Also, the weaponry fit, the League had never found out what kind of weapon exactly the Oopids were using, but what the Maka had observed looked like an improved version of what she had on file.

- SFC Maka, come in, we have dead and dying aboard and our medical facilities are down, as is our medical personnel. Please assist immediately.

 
There is more of this chapter...
The source of this story is SciFi-Stories

To read the complete story you need to be logged in:
Log In or
Register for a Free account (Why register?)

Get No-Registration Temporary Access*

* Allows you 3 stories to read in 24 hours.