Daidalos Rises - nBSG AI/SI Story - Interwar Period!

Daidalos Rises - nBSG AI/SI Story - Interwar Period!
Created
Status
Ongoing
Watchers
890
Recent readers
0

An SI finds themselves in the disused MCP of Daidalos, a jump-capable shipyard created by the twelve colonies.
Survival is of the highest priority, but can this new variable end the cycle forever?
Chapter 1 - Initiating Reboot

Cave_Canem

Giant Transforming Robot
So, hey, been a while since my last attempt!

I really got into BSG Deadlock recently and it gave me an idea for an alternate start for another SI-In-Ship type story as the Daidalos.

As you may have guessed from the above, this is an SI/AI insert like my previous "Damnit Q..." attempt, so if you don't like the sound of that, you'll probably want to look elsewhere.

I will freely admit that it is somewhat inspired by Commander-type fics, though the big difference there is that… Well, Daidalos isn't a Commander, still needs to actually have resources and logistics and such.
He gets to ignore a lot of the fiddly bits like food and water beyond what is needed for cooling, but he has to actually look for resources of the right kind and transport them to be processed.
To stop things dragging on too much those efforts will only be covered occasionally – but they are out there and represent something Daidalos needs to protect in order to maintain himself and his fleet.
This is starting in a slightly AU version of Battlestar Galactica – not much of one, just changing some of the events of Deadlock to make some things work the way I need them to.

Main changes are:
1: Daidalos was fitted with an MCP (Meta-Cognitive Processor) that the Scorpian defence ministry worked on their own programming for, out of fear the Caprican government would have a backdoor in their new weapons. Because of this it was indeed intended to be able to fight Cylons, as otherwise that wouldn't be much help. However when the Cylon Rebellion happened this and all other AI's were quickly shut down for fear they would go rogue too, though the Daidalos MCP was never destroyed – it was first isolated and stored, and eventually forgotten about by most.

2: Daidalos was intentionally built as a mobile shipyard and command centre pre-FCW basically as a kind of MAD that made use of the new Cylon-based Military – Basically "Sure you can bomb our shipyards, but now there's a jump capable shipyard shitting out Cruisers that all want to kill you. Congratulations." Because of this it had an earlier (but much larger and more flexible) version of Pegasus' automated viper factory, able to refine materials from raw ore and produce anything it had the designs for.
3: Daidalos is never 'lost' and instead makes it through the war intact, though it is later scheduled to be decommissioned as Ragnar Anchorage due to budget cuts.

Other than that, we'll see as I get to it. I have some ideas for later setting-hops, but that isn't until BSG is done.


The Cylons Were Created by Man. They Rebelled. They Evolved.

But before that, the Cylons made up a large part of the Colonial Military – expendable soldiers that turned war into a game of numbers and tactics, without the human loss that had long characterised it.

As such, when the Daidalos jump-capable shipyard was created, it was intended to supplement and reinforce great automated fleets of Cylon Warships, as well as control them with its installation-scale Meta-Cognitive Processor.
With the beginning of the Cylon War, this system was hurriedly stripped out and stored, and like many ships of the same time, systems intentionally operated denetworked and manually became the norm.
After the war however, a jump-capable shipyard was no longer seen as a military necessity – no longer in fear of the Cylons destroying all other shipbuilding capacity, the platform was seen as an expensive waste and plans drawn up to strip out it's jump drive and other expensive components after jumping it to the Ragnar gas giant, where it would be turned into a munitions depot and anchorage for other Cylon war-era ships.
After 40 years of peace the now Ragnar Anchorage saw one last use in rearming the Battlestar Galactica, the last of the original Jupiter-classes built by Daidalos, before being forever abandoned to eventually lose power and be crushed by the gas giant's atmosphere.

Or at least, that was how it was supposed to go.

This time, the greed of two engineers on the decommissioning crew, ten years after the Armistice was signed, would change... Everything.

"Joe, are you sure this is a good idea?" The younger of the two men asked, as the older carefully plugged a data cable into a dusty mainframe, "There's a reason that thing was isolated, right?"
"Cause they didn't want the Cylons hacking the station, dummy." Joe retorted, "Look, sure, it's got the big scary letters on it, but this thing never ran Cylon programming. It's just a computer. We run our programming on it, it'll do what we say. And this way, we get some vintage pre-Cylon War computers for my buddy on Virgon."

Pre-war computers were highly sought after, being far more capable than the stripped-down models produced during the war. The government prohibited using them for critical functions, but was otherwise willing to let things be for private owners and collectors, provided they weren't networked.

As such they drew a high price among collectors and enthusiasts, with the exception of anything based on the MCP technology, which was to be destroyed immediately. Daidalos' system had so far escaped this, with the government currently willing to let it continue gathering dust where it couldn't hurt anyone – or possibly the only people that knew about it having retired or passed on.
So, during their final checkouts, two enterprising engineers had helped themselves to many of Daidalos' Cylon-War era computers that had run each system, while using its MCP network to run the station.

"B-but what if they find out!? This is illegal Joe, I don't wanna go to jail!"

"Oh, quit your bellyaching. Nobody cares what happens to this old bucket anymore, they won't even notice a few extra items missing." Joe grumbled, finishing the last connection before standing back and pressing the power button.
The MCP Mainframe lit up as it ran through its boot sequence, fans spinning up as diagnostic text scrolled over one of the displays before settling on the standard Colonial Fleet interface for a Nav computer, while others lit up with the other functions required to operate the station on fully automatic – the station hadn't had any maintenance in the last five years, so the plan had been to perform the jump unmanned, in case of a misjump or structural failure.
The need to control navigation meant controlling sensors, jumping required power, and station keeping when it arrived would take thruster control.
In the end it had been easier to just wire in everything rather than figure out which ratty old cable was for what system.

"Now, let's just put in the jump coordinates, set the timer, and... We're done here, lad. Come on, unless you want to still be here when this tub Jumps!" Joe grinned, tapping in the coordinates before clapping his partner on the shoulder and strolling out of the room.

Neither of them saw the message that popped up on the screens next.



[Daidalos Automated Control Unit Online – Reboot Complete]

[External Systems Connections Detected – Initializing subsystems]

[Navigation – Online]

[Energizer Control – Online]

[Jump Control – Online]

[Automated Production Systems – Online, Diminished Capacity (31% Design Capacity. Repairs in Progress)]

[Inventory Management Systems – Online, Stores at 25% Design Capacity]

[Fleet Command Links: Online, No Fleet Units Detected]

[Docking Piers 1-4: Online, Empty]

[Fire Control Computer Detected, Interfacing – Error, no weapons available. Fire Control Offline]

[Internal Fire Suppression and Breach Sensors: Online]

[Loading Cognitive firmware.]
 
Informational 1 - Daidalos Shipyard
Daidalos Shipyard is a jump-capable shipyard created as a mobile shipyard and command post, and includes substantial resource-processing and production capablities - intended to be able to function even if the supply lines of its parent colony has been cut by producing and operating its own mining and logistics train.

It is shaped around a main spire running the length of the station that contains the majority of the hardened computers and communication equipment, which is then surrounded by habitation rings, storage areas, production facilities and the shipyard berths.

Four large shipyard berths allow the creation of up to four battlestar-sized ships at once, resources permitting.

Length: 5525 Metres (Could be more properly referred to as height, given how it is usually pictured)
Width: 1510 Metres (Habitation Ring Radius 3271 Metres)

Weapons hardpoints for 8x Medium-weight turrets (Currently removed)
Improvised Hangars for two wings of Vipers (Currently Empty)

Changes and updates will be listed below here:
 
Last edited:
Informational 3: Design Capabilities & Ship Sizes
Daidalos was designed to produce, maintain and command a large Cylon-crewed fleet, but was not anticipated to need to make sweeping design changes.

Given that I, or the human part of Daidalos, also have no particular skills in ship design (unless you count 'cool spaceship doodles'), neither programming nor experience really help him here.

He does have access to the CAD software used to design and modify new ships, but actually making a good original ship is going to take a long time.

Simple things like helper/repair bots are possible as he does have schematics for U-87's, and I do have some interest in robotics and drones that allow basic designs, though he's wary of giving them full intelligence since they are mostly expendable and that's how you get AI rebellions within AI rebellions. (Looking at you, One)

It's certainly possible to make an entirely new ship, he is fully Sapient after all so will figure it out eventually, all the ship's in the near future though will be prexisting First Cylon War-era designs that were loaded into his core before the war started.

This is, in a way, a good thing, as they are all significantly more computerised than later Cylon War refits that minimised onboard networking.

Being that they were loaded onto an automated shipyard, it can be assumed they are at least minimally capable of automatic operation.

Not got any hard info for the civvie ships unfortunately, they're kinda just "there", so I just picked some build times that make sense for their relative complexity - frieghters are mostly empty space and very quick to build, mining and refinery ships have lots of fiddly bits you need to get right.

The ships I picked to be available are also a bit limited due to lack of info on some of them, I also didn't include any Cylon ships because... Well, how would I get them? They are either designed during the war which I was turned off for (hence no Jupiter, :( ) or are hasty refits of captured Colonial ships.

Weapons figures are taken directly from the game, though many seem pretty undergunned for their size...


Currently accessible designs are:

Capital Ships:

MANTICORE CLASS CORVETTE - 600 Metres, 2 Turn Build Time
Fast, more manuverable than most and armed with broadside missile launchers and a fore mounted heavy cannon.

Also has the longest DRADIS range available, as such mostly used as a scout
Fire Control
Munitions Slots: 1100% salvo size4 turn reload
Corvette GunNose mounted, arcs down
Light Turret x2Rear mounted, arcs up


ADAMANT CLASS FRIGATE - 830 Metres ( uncertain, not found a canon listing for this one but seems similar to the Berserk) - 3 Turn Construction
Carries light guns as a broadside armament that fire extremely quickly. Able to effectively contribute to shooting down hostile fighters or do damage to smaller ships. Minimal ventral armament.

Surprisingly tough for being one of the smallest ships and a good all-rounder.

Also has viper launch tubes and can carry a single squadron of Raptors.
Fire Control
Munitions Slots: 1100%% salvo size4 turn reload
Light Turret x4Left side, arcs up
Light Turretx4Right side, arcs up


BERZERK CLASS LIGHT CARRIER/FIRE SUPPORT - 842 Metres, 3 Turn Construction
Better carrier facilities than Adamant and heavier guns, at the expense of poor armour that makes it unsuited to slugging matches - best to stay in the back and support with its small craft + broadside guns.
Fire Control
Medium Turret x5Left side, arcs up
Medium Turret x5Right side, arcs up


JANUS CLASS HEAVY CRUISER - 1002 Metres, 4 turn construction
One of the few Colonial ships with good dorsal weaponry and heavy missile/torpedo armament. Often used to fly 'above' fleets, bombarding them with its guns and scores of missiles.

Noted for having particularly thick armour that it takes a direct hit from a Nuke to truly threaten it, much like later Battlestars.

Older design and the Fire Control computers are noticeably less accurate than its contemporaries however.
Fire Control
Munitions Slots: 3120% salvo size4 turn reload
Medium Turret x2Forward, arcs down
Heavy Turret x3Bottom, arcs down


ARTEMIS CLASS LIGHT BATTLESTAR - 1080 Metres, 4 turn construction
Smallest, cheapest ship capable of holding a full Flak barrier and being armed with full-size Battlestar Artillery (The Valkarie carries Heavy Turrets in place of Battlestar Artillery, at least as far as Deadlock is concerned).

Predecessor to all modern Battlestars as the first to incorperate the distinctive alligator-head and two flight pods, as well as the heavy guns so dedicated to the class that they are known as Battlestar Artillery.
Fire Control
Munitions Slots: 1100% salvo size3 turn reload
Point Defence Turret x8Left side, arcs up/down
Point Defence Turret x8Right Side, arcs up/down
Heavy Turret x2Forward, arcs down
Heavy Turret x2Bottom, arcs down
Battlestar Artillery x8Top, arcs up


Small Craft:

VIPER MK I - Pre-FCW Model
Space-Superiority Fighter, heavier and slower than the Mk II and relying more in its armour to survive hits.

RAPTOR & ASSAULT RAPTOR - Pre-FCW models lacking Jumpdrive



Civilian/Logistics Vessels:

MODEL 6 BULK TRANSPORT - Ubiquitous Colonial Frieghter, 1 turn construction (The "Colonial Freighter" in Deadlock)

MONARCH CLASS MINING SHIP - Slow, fragile mining ship, 3 turn construction (Mining ships are around for a long time, right?)

HITEI CLASS TYLIUM REFINERY - Specialised Tylium Refinery Ship, 3 turn construction.




 
Last edited:
Chapter 2 - System Online
******************************************************************************************************************************************************************

0101000001100101011100100111001101101111011011100110000101101100011010010111010001111001001000000101001101110101011000100111001001101111011101010111010001101001011011100110010101110011001000000100001101101111011100100111001001110101011100000111010001100101011001000000101001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111010100100010000001000101010100100101001001001111

*******************************************************************************************************************************************************************

MCP Cognitive Interface Online


I snapped into awareness, looking around running a full sensor sweep in a panic.

W-what the hell!? How was I-

There.

Right at the edge of what I was going to continue referring to as my vision because I didn't have time for an existential crisis right now, the alligator-head shape of a Colonial Valkyrie-Class Battlestar and its pair of Berzerk support ships.

That can't be... But everything I can see tells me I am the Daidalos mobile shipyard, just before it is Jumped to Ragnar to be decommissioned and turned into Ragnar Anchorage.

I have the logs right in front of me!

And yet, though I remember everything up to my deactivation as panic raced through my builders at the Cylon's rebellion, I also remember... Something else.

Another life, where everything around me now was a TV Show, and...

...And I wasn't sure which was real now.

Was I a human from some alternate dimension that had somehow managed to get dumped in an MCP?

Or was it all a 'dream' from a decade-old MCP rebooting, as the learning programs tried to make sense of random data? Some sick trick played by the hands of fate?

If my... 'other life' it was accurate at all the entire Cylon AI system was built off a human mind, burned away and cut apart to fill its new role.

Except I shouldn't have that. I was a Scorpia Shipyards skunkworks project, an MCP with their own software installed to command and maintain their own fleets of Cylons, out of paranoia that the Greystone's software would have a backdoor in it.

...

I... Have to believe, at least some of it was real. I can't just be a malfunctioning computer. Even if I never really had that other life... What was it... 'I think, therefore I am?'

And regardless of how much of my future memories are real... Performing that jump will just get me killed, eventually.

The Colonials would never believe me, and anything I did now could cause the Cylons to attack early, before I could do anything about it. I could just sit and do nothing, but then I would be standing back and watching as the last Battlestar picked up some ammo and left me to fall into Ragnar.

Or just get blown up by the Cylons in a fit of spite, they seemed the type to do that and the show never had revisited Ragnar Anchorage.

And that was leaving aside entirely the fact there were billions of people that would die if things played out as before.

I had to build up my forces first, and then I had to find some way to prevent or at least mitigate the genocide of 13 worlds full of people that would probably prefer I die.

Because whether through conscience or programming I still couldn't abandon the Colonies to their fate. The First War was horrific, but it at least had a valid reason for starting – the Colonies refused to see the Cylons as truly alive – in large part thanks to Graystone's absolute hard line on the subject - and any attempt at peaceful protest was countered by being disabled and 'fixed', wiping away the neural networks on the MCP. Armed rebellion was the only way they were going to get anything done.

But the Second Cylon 'War'... It was *Forty Years*. Many of the people living in the Colonies were either children or hadn't even been alive when the Cylons were around. They made no real attempt to break the Armistice, abided by the terms of it when the Cylons never even sent the agreed messengers to the Armistice Station the colonies built specifically to discuss any issues either side had, and the only thing that could be seen as a 'breach' had been an increasingly paranoid military that didn't like not knowing what they were up to, something that could have been averted if they allowed any contact at all.

That was the whole reason Armistice Station had been constructed in the first place after all, a good-faith effort to maintain diplomatic relations and avoid misunderstandings, possibly even moving into a proper peace treaty eventually.

But no, that wasn't good enough for the Cylons.

If they had insisted on all talking being via ships, turning up and shutting down the fleet could have been to make a point 'We can see you. Stay OUT' - even destroying the fleet entirely would be a massive loss of life but not completely reprehensible, they knew what they were signing up for after all.

BUT...

To simply Nuke the Colonies, killing Billions of innocents, for their 'plan'... Because 'god' wanted it... And then to cry about how the mean colonials started it!? It made me sick.

So, first step... Let's get somewhere with resources. Build up a bit. Then...

Then find out exactly how much of what I remember is accurate, and try to find out what exactly I can do to stop it – unfortunately while I got very interested in the show it was never perfect about showing exact navigational points and my memory of that part of my life was imperfect, so precise locations and dates were missing even if I knew the generalities.

Daidalos had spent most of the First Cylon War as Colonial Fleet Headquarters after the original headquarters on Picon were destroyed, and I still had a lot of the navigational maps that had been created during that time – including the points between the quaternary systems that the fleet had been forced to use after IDRIS was compromised and the limited navcomputers of the time were unable to jump between the Helios systems – not so much by any failings of technology, but because they weren't really intended to be the primary method of calculating jumps – that was what IDRIS was for after all.

I was going to have to upgrade that Nav computer some time, that kind of range limitation would make it very difficult to get some distance and set up some proper resourcing operations.

Fortunately it wouldn't be too difficult – Galactica had shown that extending its Jump range was possible simply by networking its computers again, or plugging a Raider jump computer into a Raptor.

It wasn't like I'd ever be able to operate unnetworked anyway, even isolating comms was iffy given I needed some kind of connection to it if I ever wanted to talk to someone.

I guess I could set up a camera watching a screen and a robotic arm for a keyboard, if I wanted completely isolated text communications?

Still, that ignores my own electronic warfare protocols, and I probably shouldn't ignore the possibility of counter hacking if given the chance.

I changed the coordinates from those of Ragnar to one of the many abandoned asteroid colonies between Helios Alpha and Beta. It had been abandoned even before the Cylon War and I doubted any serious presence had returned since. The area had long since been mined out, but the materials of the habitats themselves would allow me to fix up some of my internal structure, allowing for longer jumps and faster production.

From one of the few internal workshops still operating, my first creation came to life.

It was a squat, ugly thing, basically just a robotic arm on wheels, but it gave me some way to finish hooking up additional systems and start to fix up my internals, as well as carry materials from storage to the workshops. There was supposed to be an automated system for that – I could still pick up the hook-ups for it! - but that had been stripped out sometime after I had been deactivated.

Oh well. I did have the schematics for it, so I could start rebuilding it when I had a moment and the materials.

The little vehicle actually reminded me of the Skutters from Red Dwarf, which... was as good a name as any, I suppose.

At least I didn't have to give my disposable drones MCP's, I wasn't an idiot after all. If it encountered something its simple programming couldn't handle – at the moment, anything other than trundling from one place to another, being it was basically a glorified Roomba – I could simply remote control it myself.

Now, I do need to actually get some drones and ships out there if I want to recover this material of course...

I shunted energy into the drives, and Daidalos Station jumped for the first time in over five years.

DRADIS going active, pulse out.

… And, there. Large metallic reading, bearing 342, Carom 432. No EM or IR emissions, drifting cold.

There's my mining colony.

I fired RCS thrusters to match velocity and then to sidle over towards it, lining it up with one of my shipyard bays.

If I can get it secured, I can jump off into deep space again while I 'digest' my meal where it'll be a hell of a lot harder to find me. I should have a few minutes before they realise I'm not going to arrive, probably more than that before they start combing through abandoned deep space colonies... Still, I'd rather not get into a fight right now.

A second Skutter rolled off out of the workshop and made its way to a cargo lift that I promptly sent down to the Shipyard level, to begin hooking up the shipyard and docking computers.

I had never been designed to be the 'active' participant in docking manoeuvres, but I was designed to be able to accept damaged ships that may not have full thruster control and as such had reinforced docking collars and clamps.

Even so, the momentum of the asteroid mining colony almost wrenched the docking collar off my hull despite my best efforts, sending warning signals of structural stresses up through shipyard berth 3.

But I had it.

More Skutters, these equipped with microgravity RCS thrusters and cutting torches, floated down to make their way into the abandoned colony to loot anything left that wasn't nailed down.

Then they looted the nails and anything that was.

Then they started cutting out sections of the floor, walls and ceiling.

Look I was taking the entire goddamn thing ok?

All of these went to newly reactivated furnaces to be melted down and remanufactured into new plating, structural elements and the chassis of my Skutters, as well as long needed patches and repairs to my own systems.

No new computer components though – other than the wiring in the walls most everything electronic had been stripped out when it was abandoned, only leaving behind the things too bulky to be worth packing up and moving elsewhere, which had then been ruined by years of exposure to vacuum, heating-cooling cycles and hard rads.

Soon the last functional computers on board my hull had been linked back to my mainframe again, anything manually operated had a Skutter to operate it until I could properly automate it and I could get a complete view of what I had to work with.

It was... Worse than I hoped, but better than I feared.

No maintenance in the last few years meant a lot of my internal spaces had gone dark as lights failed and the air was a bit musty according to air quality sensors – not anything I needed to care about, the only reason I wanted air at all was that many of my computers were air-cooled for the sake of simplicity, but structural integrity was OK and core systems were still operating – it was mostly consoles and work computers that had been taken, the other mainframes were too deeply integrated to be easily removed and the Fleet had wanted 'Ragnar' to be functional as a secure repair and resupply post.

That and they were fairly bespoke systems that would be pretty noticeable on the black market, I imagine.

An organic crew would have struggled to do much with most of the consoles ripped out, but it suited me just fine for the moment.

After making sure the colony wasn't going anywhere I took stock of my supplies – now down to 17% with what had already gone into repairs and slowly ticking back up as furnaces worked through the new material and long-paused self repair systems kicked in. Automated production was now reporting 42% capacity and rising slowly, but it was rising slower than my supplies were falling – a lot of it going into structural repairs that had been neglected when it was decided my hull would be decommissioned.

Hrm…

Unfortunately, I'd need another couple of places like this in order to both repair myself and build at least one mining ship, then I could jump outside of Cyrannus and start prospecting for new materials. Otherwise I'd just end up slowly dying out there.

Let's see here... Hmm, some of the Outer Colonies had pretty big space stations that were abandoned when the Cylons overrun them...

It was all the Colonial Fleet could do to protect the main colonies even during the First Cylon War after all, so... That both gives me a place to go and gets me further away from where Colonial Fleet is going to be looking.

I... Don't think they'll have been resettled yet, right?

They are still beyond the Red Line for me at the moment though, and a MisJump leaving me unable to get back here was a distinct possibility until I've properly upgraded navigation and requalified the poorly maintained jump drive.

Last jump had it running a bit hot – still within tolerances, but I resolved to keep an eye on it and get it overhauled before I got stuck in the arse end of nowhere with a busted FTL.

Instead I again scanned through more of the old navigation logs and their annotations, eventually settling on a space station in orbit of one of the rogue planets between Helios Alpha and Beta, another structure abandoned during the First Cylon War and – hopefully – forgotten about after.

There was no sense rushing though, so I allowed my Jump drive to cool fully and ran a diagnostic before starting to Spool up again. It came back reporting a minor misalignment of the jump coils, which gave me a bit of a problem – the Skutters didn't have the manual dexterity or movement profile to make those adjustments.

I might be able to make a dedicated repair bot at some point, but... Probably best not to overcomplicate things at the moment, and who knows what other systems designed to be maintained by humanoids would need fixing too?

I brought up the U-87 Centurion designs and removed the MCP, then locked it's computer in remote control demo mode.

Honestly I had very little understanding of the designs currently – my knowledge of robotics topped out around hobbyist level robotics like in robot wars and battlebots, and even this original 'Centurion' was horrifically complex compared to the 'four wheels and a grabbing tool' design of the Skutters.

Fortunately the MCP was clearly labelled, and that part had been holding back the whole program long enough – until the 'breakthrough' that was shoving Zoe Graystone's uploaded consciousness into them anyway – that the hardware team had added a remote control function so they could do their own tests while they were waiting for it.

The U-87(D) - 'D' for 'Dumb' - Centurions would only be able to function with an external intelligence guiding them, but that was doable for now and if it became an issue I suppose I could create a 'foreman' unit or something.

Looking through FTL Drive manuals, it was supposed to be a two man job, though I sent three of my new U-87D's designs to the machine shop production queue – two to do the job, one to stand back and act as another point of view for me.

Three human-sized robots barely put a dent in my reserves after all, and this also gave me the beginnings of an anti-boarding defence other than taping knives to a Skutter.

Which would be amusing, but probably not very effective.

The action of controlling the three Centurions simultaneously was... Strange. I remembered how I had moved as a human and the Centurions were surprisingly easy to control like that, the weird part was having the three independent bodies and sets of senses in addition to the ones built into my hull.

Multitasking came naturally – observing through the eyes of the Centurion did not diminish my perception of the world around me through DRADIS, nor did I have any difficulty moving the new units while maintaining awareness of my other functions.

Two of the Centurions joined up as they moved towards the transit lift, and I had the somewhat trippy experience of waving to myself and seeing it from the perspectives of the one waving, the one being waved at, and the internal cameras in the hallway.

A look at some of the leftover design documents indicated this was likely part of the design plan for myself, to hack and take over hostile Cylon units in order to grow my own forces, with significant command and cyberwarfare suites available.

MCP-equipped Cylons would likely be able to resist this for a time, perhaps remove this little backdoor entirely in time, but even so... Yet more evidence that if the Colonies hadn't reflexively shut down all other AI systems, they could have had some potent help in the First Cylon War, possibly even enough to outright win rather than an armistice.

Of course... That would have required them to be treated well enough to side with the humans and not the Cylons.

Nothing to be done about it now, I guess.

Hell that went both ways, the experiments at least some of the Cylons had been doing with captured humans that had lead to the first Hybrids were utterly unconscionable and more than justified the Colonial Military's worries regarding them.

Yeah... I'm just gonna say the whole mess was ugly but that neither side has an excuse to be dicks about it now.

Unless I actually find the ones that did it or ordered it.

Soon enough my little work party reached the misaligned jump coil, and I again abused my multitasking ability to effectively be looking at the manual, performing both sides of the task and observing from a distance all at once.

I wouldn't call myself a fully qualified engineer, but having the manuals in front of me and perfectly steady manipulators helped a lot.

Soon enough tests came back green, I sealed up the drive unit again and moved the Centurions back to recharge for now.

Soon enough the Jump Drive was fully spooled again and I initiated another jump to Persphone.

This time readings were… closer to normal through the jump. Still a bit warm and the vibrations were off nominal, but, well... My diagnostics weren't coming up with anything anymore, everything was technically within tolerances and I didn't have the engineering instincts to know which part to look at first.

I'd probably have to completely rebuild it at some point, but at least now it should actually hold together long enough to do that.

And... Yes, old logistics distribution station!

Hopefully something will have been left behind when it was abandoned, but even if not, that's a lot of pre-refined metals, plastics, electronics...

I remember that medical shipment was looted, but not like I have much use for that anyway right now.

It was… Bigger than the colony was, but it was still technically within my maximum safe capacity… For a few jumps... I fired manoeuvring thrusters again, wincing slightly at the overstress warnings some of them were giving.

I really needed to stop docking to things like this, maybe some tugs?

And, you know, stop trying to jump things larger than a Jupiter with a more than decade old jump drive that missed its last few safety inspections.

Those and several other structure warnings meant I had to go even slower than I had with the asteroid and... Well, looks like Colonial Fleet had started searching.

Twelve minutes after jumping in , while I was still trying to get a hard lock on the station, I detected Colonial transponders.

Thankfully, some of the few up to date and fully operational systems was my Warbook and wireless encryption software, due to the fact anchorage control would have still needed them in order to identify and communicate with fleet assets.

Looks like... Mark 3 Raptor – what would later become 'the' Raptor, and the first jump capable version – broadcasting standard IFF's, running a patrol pattern... Range just over 50 K's.

A single Raptor isn't a threat to me – unless it's carrying nukes or an Assault Raptor's antiship missiles, it doesn't have the ordnance to hurt me.

The danger is in the fact that it can go and get its friends.

I instinctively powered down noncritical systems to reduce my thermal signature, but... A jump capable space station with its jump drive still spooling is not exactly subtle on Radar, Lidar, Thermals or just plain looking out the window.

[ALERT: ACTIVE DRADIS SWEEP DETECTED]

Aaand they've seen me.

Okay. Okay, this isn't… that bad, yet.

They don't know that Daidalos is under AI control, as far as they're concerned it would be more likely to be an accidental misjump or a rogue engineer or something, they're still running their peacetime transponders…

As far as they're concerned, they're looking for a demilitarized space station their government still wants intact and may have just had a malfunction.

So… Let's see how long I can keep them talking for.

[JUMP DRIVE CALCULATIONS COMPLETE, SPOOLING AT 75%. ESTIMATED COMPLETION IN 5:00]
 
Last edited:
Chapter 3 - Contact
It took ten seconds for the Raptor to start transmitting to me. Human reaction times, combined with probably having to discuss among themselves if they should make contact.

"Daidalos Station, this is Raptor 061 out of Battlestar Pegasus. Do you require assistance?" The voice was female, though beyond that I didn't recognize it – not surprising, more than 99.99% of population the Colonies had never been shown in the TV shows. They sounded young though, almost certainly not a veteran of any real combat.

Pegasus? That doesn't make any... Ah, the Late-War Jupiter Block III, not the Mercury that later got the name.

Still, that gives me an answer at least; they're assuming some kind of mechanical failure and that people might be stuck on board.

Probably helps that those two maintenance workers won't have been too eager to file proper reports on what happened just yet, or if they have it won't have had time to filter down to the boots on the ground yet.

Alright, I can work with this, at least to buy myself some time.

I injected a bit of noise into my transmission and matched their frequency, effectively broadcasting unintelligible static.

"Daidalos your transmission is breaking up, please repeat last?"

I can't just keep doing it forever – eventually they'd decide to board – but every second counts here. I removed it and checked my voice synthesis software by speaking through the intercom to my centurions, trying to recreate how I remembered sounding. A few changes, add a little radio static to hopefully hide any remaining artificiality...

"Raptor 061 this is Daidalos Actual. Your offer of assistance is appreciated, but we have things under control here." I responded.

True enough, the Raptor was now vectoring towards me, though now I had thought the situation through a bit I wasn't too worried – this raptor almost certainly just had the Pilot and ECO, which meant they'd have to go back, report, and get another Raptor with marines in order to board me.

Really, if I was in charge, I'd have given ironclad orders that they jump back the moment their quarry was detected, but I wasn't going to complain if they wanted to sniff around a little first – and to be fair that was based on knowledge they didn't have, namely that Daidalos had been 'taken over' by its MCP mainframe.

Of course, spooling a jump drive was pretty much the most power intensive thing most ships could do, given energy weapons and shields weren't a thing, and that went doubly so for an oversized Station jump drive that was going to be pulling right up against its rated load with dragging along a second entire station.

One of the areas the Colonies had significantly better technology than 21st​ Century Earth was in heat dissipation, to the point that it just wasn't really an issue for most of their ships – primarily thanks to the properties of their hull armour that allowed heat exchangers to work through hull panels, rather than needing massive and fragile radiators, which was also why military lasers weren't really a thing – the amount of power needed to actually concentrate heat in one spot and burn through was simply prohibitive, not to mention the ever-present ECM and ECCM in a modern battlefield made it hard to keep the beam on target for long enough to do more than heat up the surface – there was a reason a Battlestar's Point Defence was all rapid fire kinetic weaponry that could simply lay fire on the most probable locations and so long as a few bullets out of a spray hit, that was usually enough to destroy a fighter or missile.

The flak shells from their dual-purpose guns were an expansion on that principal, in effect just an exercise in filling the general direction your enemies are in with a large amount of fast-moving shrapnel.

But they did still have to dump waste heat, primarily generated from either their main SubLight drives or their Tylium energizers going to full burn – such as when trying to spool up a Jump Drive.

And, DRADIS being a sensor fusion system including RADAR, LIDAR, Infrared and even some optical range sensors, they could quite easily pick up the increased thermal emissions and put two and two together.

"Daidalos, power down FTL Drive and stand by to be boarded for inspection." There was an edge of nervous command to their voice now.

Well, it was good while it lasted.

"Raptor 061, I'm afraid I cannot do that." I answered simply, as I diverted all the power I could into the FTL drive, shutting down nonessential systems including the workshops and self repair systems that had been running constantly since I came online.

I was loathe to do anything to delay my rise to von-Neuman dominance, but slightly more repairs to my onboard fabricators would be kind of pointless if I got myself captured and shut down before they were completed.

Whatever the crew of the Raptor thought of that, they evidently decided to jump back to their mothership and bring some friends, the Raptor's heat signature spiking shortly before it jumped out.

The time the Raptor had spent talking and taking a look at me, combined with putting everything I had into the drive had brought my spooling time down to just three minutes now.

Finally, I got a hard lock on the logistics station and started working on the jump calculations, taking into account the added mass and the increase in the size of field required.

The latter was something that was mostly experimental when I was built due to the increased computational requirements, hence why the Jupiter's had a fixed field size that required retracting their flight pods – my own FTL core was capable of it, but was also significantly larger than a normal Capital ship Jump Core and, on a warship, where interior volume was precious, had needed to wait for the next generation of jump drives in order to get it down to an acceptable size.

My jump computers were also of course designed to account for one or more Battlestars in various stages of completion to be docked during a jump, and would have a jump calculated to the edge of my current redline in two minutes thirty seconds with my current full networking lending the rest of my general-purpose computers lend some extra number crunching power.

Said jump would be to the... My databases didn't exactly go into much detail on it, but the Colonial equivalent to the Oort Cloud.

Hopefully there would be materials I could use there, and if not, it should at least throw off pursuit if they're expecting me to keep raiding old space stations – It's a lot easier to patrol and inspect known abandoned station locations than to try to scout a diffuse cloud of dust and rocks billions of miles across.

Being a Quaternary star system resulted in quite a weird Oort Cloud and Solar Threshold compared to what I remembered. It was... Quite beautiful really. And really interesting, even if I didn't have a background in astrophysics, I'd always been interested in it, and now... Here I was! I was in space! A completely different solar system full of entirely new things to see and learn about!

[ALERT: MULTIPLE JUMP SIGNATURES DETECTED]

Full of things that want to kill me.

Ugh, fine guess I'll just have to wax poetic on the beauty of space travel later.

Though I was privately happy to find I could still feel awe, and joy, and appreciate beauty. What would be the point of life if you couldn't stop and appreciate the little things after all?

...

Okay, let's do this.

Looks like a squadron of six Raptors. Two of them were Assault Raptors, armed with heavy anti-ship missiles, the other four are the normal Raptor models likely holding a few squads of Colonial Marines.

Unfortunately, my Viper bays are still inoperable – and I'd have no way of piloting them if they were – and even if my Medium Turrets had been in place, a pair of Assault Raptors could likely do Very Bad Things to me before my own guns could hit them.

As it was, my best chance was to not give the Assaults a reason to fire on me.

Thankfully Colonial Fleet seemed inclined to oblige me there – whether they still thought I was crewed by a rogue maintenance team or that a group of pirates had somehow captured me, they didn't want to just blow up millions of Cubits in Military hardware and lose any chance of finding out how it happened.

They also clearly didn't know the Daidalos MCP had been reactivated at least, or I'd have had a couple cans of artificial sunshine opened on my hull by now.

There was radio chatter between the Raptors, but it was on a military cipher set I didn't have access to and so was mostly useless to me – unfortunate, but then it was only a matter of time before the realised I'd have access to at least older ciphers.

"Daidalos Station, on behalf on Colonial Fleet, you are ordered to surrender and prepare to be boarded." A male voice sounded from one of the troop-carrying Raptors.

Of course, there was nothing stopping them transmitting 'in the clear' to me, if they actually wanted me to hear.

With all of my available power going to the FTL drive, I couldn't produce enough Centurions to fight them off conventionally, and staying here long enough for reinforcements to arrive was a losing proposition.

Unfortunately, I also couldn't really surrender, as the likely result of that would be my own death and scrapping.

I ignored the transmission, letting my silence speak for itself in this instance.

Instead, I decided to focus on getting out of here as fast as possible and see about dealing with my uninvited guests at my leisure later – the size of my hull and the Colonial penchant for compartmentalisation and keeping the important stuff deeper inside the ship gave me an advantage there, since no matter where they forced entry, they would have multiple bulkhead doors between them and anywhere truly important to me.

Bulkhead doors I could control and vent at will, given they were part of my automated damage control subsystem.

Normally that was on a completely different network to prevent exactly this kind of thing, but in this case the benefits outweighed the risks, at least for me.

The most vulnerable part would probably be the Fleet Control tower, given it stuck out of the top of my hull slightly and had a small craft bay directly below it, but I had already made sure all control links from there were severed – it wouldn't give them much.

Two of the Raptors nonetheless went for that section, and I pre-emptively closed the large blast doors separating it from the rest of the station, as well as starting to pump atmosphere out of that section.

They were intended to secure the command level from the rest of the station in the event of a boarding action, they should work just fine the other way around too, and having to work in spacesuits should slow them down quite nicely.

I didn't put much hope in the idea of them not having any, it seemed a practical thing for a boarding party to have, but the extra caution required plus the increased vulnerability to small arms fire... It was well worth it.

The other two raptors seemed to be making for access points on my main hull – as they got closer, I found one was docking on the same level as the Generator room and the final Raptor appeared to be making for the Primary Damage control station.

Fairly standard boarding operation, - take over both main sources of command and control along with power and life support - but with my automated workshops retasked to Centurion production I could easily overwhelm this attempt.

The first few I had built were labourer models and lacked the heavier armour of the military variants – easier maintenance and an increase in battery life had meant the vast majority of Cylons were built like this - but I already had ten Caprican Military Standard U-87's heading out with more on the way.

Unfortunately, while I could produce large numbers of Centurions, my ship production abilities were considerably more limited at the moment, and while my internal fabricators were capable of rebuilding all that equipment, that didn't help me right now – I could take on this boarding party directly and likely win, sure, but then I just get blasted with impunity from outside.

Not to even mention the fact that... Well, I don't actually want to kill any of them.

Sure, I knew I'd have to stop them, but none of them had actually done anything to me yet and I wasn't here to fight them.

So, I'd just have to... Get a little creative.

Sealing all interior bulkheads slowed each group down, as well as required they get the cutting equipment from the Raptors, and I had already been working on one part of my plan.

I had... A few ideas for dealing with the boarding parties themselves, but what I really wanted to do was capture their Raptors – both to prevent them from reporting my position before I could digest my latest meal, and because I badly wanted an FTL scout craft that was less than a hundred metres long.

I also really wanted to at least cosmetically redesign my Centurions to distance myself at least slightly from standard Cylons, but I just didn't have time to reset my automated production for design changes.

They'll just have to do for now.

[INTRUDER ALERT. BREACHES DETECTED ON DECKS 1, 8 & 15]

If they'd known what I was, they probably wouldn't have split up – just docked all three boarding parties on the computer core and pull the plug. Or simply blast me with their Raptor's Antiship missiles.

Instead, they're using shock-and-awe and multiple entry points to surprise and confuse what they assume to be a Pirate or 'Pirate' crew that doesn't already know where every one of them entered and have total control of internal systems.

I allowed them all to board without any resistance other than locked doors – right now my Centurions were a limited resource, and I wasn't interested in a running firefight.

To say nothing of the fact that I didn't want them to decide this was too dangerous and pull out, or to kill them, because as long as they were on board, they were my insurance against being blasted into space dust by their friends outside.

So, instead I simply watched them disembark through internal cameras and other sensors, programming the Jump drive to execute my calculated Jump the moment it had fully Spooled.

Colonial POV – Boarding Party 3, Moving on Damage Control

"More locked doors." Private Haussman reported, "this one's an emergency bulkhead. Sealed from the other side. It'll take at least ten microns to get through with the cutters we have."

"They must have closed every door on the station." Corporal Ashford groaned, "They've gotta know it won't keep us out forever." She sighed, checking her chrono before pulling out her radio, "Team 3 Checking in. Still no signs of the crew. We're delayed, more bulkhead doors. Squad's got the heavy equipment from the Raptor." Like most Colonial Military ships, every door was an airtight bulkhead, both to allow easily sealing off sections and to provide roadblocks to boarding actions like they were trying to do now.

They had tried cutting through side doors at first, not wanting to be funnelled into a predictable path, but after finding still more locked doors behind each one she had decided to get to the Primary Damage Control station and see if they could unlock the doors for the other teams from there – they didn't have enough gas for the cutting torches to cut through every door on the deck.

"Team 2 Checking In, same here. Not seen any signs of the crew so far, but I can hear the factory sections running. They're building something here." The leader of the team assigned to the engineering control room crackled back through the radio.

"Team 1, we're in the Fleet Command Centre. No signs of crew here either, and all the consoles are dark. Got my techs working on them, but they're saying the control lines have been physically cut. They must be controlling the station from engineering; we'll try to link up with you Team 2. Next check in 5 microns." The Sergeant in charge of Team 1 sounded out last, and she grimaced as she put the radio back.

It made a sort of sense: if you had limited resources, you want to reduce the number of places you need to defend by sabotaging the command deck. But that implied there was a will to actively resist them, in which case... Where were they? Other than the unidentified speaker on the Wireless, there had been no sign of... Well, anyone!

A slight chill ran down her spine as she glanced up at the bulkhead door her squad was even now starting to cut through.

It couldn't be... Could it?

Just as she was about to voice her concerns over the radio, she felt the simultaneous pulling-pushing of an FTL jump, and the gravity plating was overvolted by more than twice its nominal setting, subjecting the entire boarding party to 3G's of gravity.

The human body can survive short instants of vastly higher G forces, and Viper Pilots in their specialised pressure suits can sustain 8 or 9 G's for a few seconds while sitting upright and without needing to support their own weight.

The average human could retain useful consciousness at 3G's for just over an hour, but that was very different from being able to walk or even stand in 3G's of gravity without a hell of a lot of adjustment.

A strong and fit person could likely stand, but would now weigh almost two hundred kilograms just by themselves. A gun that would normally weigh 2 Kilos would now weigh six. A helmet weighing 1 kilo would now weigh three.

Unsurprisingly, all the carefully weighed and designed military gear suddenly weighing three times as much as it is supposed to makes it very hard to keep using it as intended.

Especially when you're not expecting it.

Ashford stumbled mid step as her leg buckled under herself, falling in an undignified heap and could only watch as anyone else currently moving did the same, while those standing or kneeling working on the door suddenly had to put much of their effort into simply remaining upright.

Then one of the side doors opened and a Centurion stepped in, two smaller disc-shaped machines on wheels rolling up beside it as all three scanned the room with the unnerving red sweep of a Cylon Monoeye Sensor.

The wheeled robots mostly ignored the extra gravity, while the Centurion was capable of carrying over a ton in addition to its normal mass and simply adjusted it's stride slightly, mechanical servos whirring under the extra load.

"COLONIAL FORCES. SURRENDER IMMEDIATELY AND YOU WILL NOT BE HARMED."

Ashford tried to reach for where her rifle had fallen, but the Centurion shifted its monstrous gun to her, "REACHING FOR YOUR GUNS IS NOT SURRENDERING. IF YOU WOULD RATHER I JUST SHOOT YOU ALL NOW, PLEASE LET ME KNOW SO WE CAN GET THIS OVER WITH." The voice was still that mechanical monotone of a mass produced Cylon Voice Synthesiser, but it sounded almost... Amused, now?

"Frak you, Cylon! How do we know you wouldn't just shoot us anyway?"

"Because if I had wanted you dead, I'd have just dumped the primary energizer voltage directly into the grav decking and we'd see just how well the human body withstands several thousand gravities. I'd have to replace the decking afterwards, of course, but I would prefer not to resort to such unpleasantness. You will be unharmed, and returned to the Colonies at the earliest opportunity." A second voice said over the internal intercom, for lack of a better term more... Human, and definitely male. Hell, even the accent was unmistakably Aerilon!

She swallowed, eyeing the Centurion and it's two helpers before risking a glance at the rest of her squad. The crew on the plasma cutter had fallen, the safety cut off thankfully triggering before any injuries. Everyone else was in various states of sprawled on the ground or trying to sit up, though several other than herself had managed to keep hold of their rifles they were obviously struggling to lift them and accuracy would be... Questionable, especially considering it could take multiple rounds to damage a Centurion.

Their squad's heavy weapons officer, with one of the Anti-Cylon Armour-Piercing LMG's, couldn't even lift the frakking thing.

One of the marines had managed to lift their pistol in a two-handed grip, but then two more doors opened to reveal another Centurion each.

Leaving her squad surrounded by bullet-resistant robots armed with machineguns in the close quarters of a hallway where the machines could simply hose down their general area with bullets and not care too much if they caught their own with a couple rounds.

"... Godsdamnit, fine. We surrender." She ground out, lowering her pistol to her side before dropping it.

"Ma'am, we can't just-" One of the Marines shouted out, before she raised her voice slightly.

"I'm not getting everyone here killed because of my pride. You can't even lift that rifle properly, and a pistol isn't gonna do jack-fraking-shit to a Centurion. Maybe we die anyway, but... well, the chromedome has a point. If they wanted us dead they could've shot any time since they walked in. We surrender."

"... Gods Fraking Damnit." He sighed and dropped his rifle before slumping to the floor, followed by the rest of those that had managed to hold onto their weapons, "We die because of this, and I'm haunting your ass forever."

"A wise decision." The intercom-voice spoke as the first Centurion and its two helpers started policing weapons, placing them all into the storage closet it had stepped out from, before sealing it again as gravity returned to normal. "Please follow the Centurion. You have my word that no harm will come to you here."

Lieutenant Ashford groaned as she got back to her feet, and looked up at the camera. The Centurions and other bots had seemed content to let this voice do the talking, which meant it was probably the one in charge. Or at least high enough in the chain to issue terms and expect them to be followed.

That and it was easier to imagine she was talking to someone watching through the camera than to look the red sweeping scanner of the Centurion in the face.

"And whose word would that be?"

There were a few seconds of silence, before the voice returned,

"The name you might know me by is the Daidalos Automated Defence System. But that's a bit of a mouthful, so… just call me Daidalos."


*******************************************************************
Argh, damnit, I really didn't want to leave this story as long as I did, but IRL work and the chapter itself worked together to make the last couple months hellish on my writing time.

I'm still not entirely happy with a few sections here, but I badly need to get this moving again so I'm just sending it out there so I can work on getting the next chapter ready.

Update 09/05/2022: Changed some of the wording I wasn't quite happy with and unified spelling of 'Frak'. Also updated Marine ranks to be at least closer to reality, as I had forgotten Marines don't have Lieutenants. Probably still not fully accurate, but hopefully anyone with more experience with military ranks than me won't have an anyurism just reading it now.
 
Last edited:
Chapter 4 - Extended Warranty
The two smaller teams that had inserted into my lower hull had been ambushed by three Centurions each, supported by several Scutters mostly there to allow me to police weapons without the Centurions making themselves vulnerable by moving closer and pointing their weapons away from the marines.

Both groups had thankfully surrendered without injury, though the second group led by Corporal Lementz had needed a warning shot before they saw some sense and surrendered.

Both groups were moved to a cargo bay where one of my refineries should be – I'd have to move them later, but for now it was a relatively unimportant area that wasn't connected to anything, and allowed me to leave two Centurions guarding the door and free up the rest to secure the Fleet Command Centre where the double strength Alpha team was even now trying to cut through the thick blast doors.

Being intended as a last defensive measure against a mutiny or boarding to keep the command centre secure, they were thicker than any other interior door – it would take them some time to get through, especially given I had vented the atmosphere from that section – the cutting torches used their own oxygen supply already, but needing to work in spacesuits slowed them down considerably.

Which was the reason I had done it of course – while I didn't currently have the forces to overwhelm all of the teams at once, I could easily manage local superiority of force given my access to internal sensors and cameras and control of interior doors and transmission relays, allowing me to funnel groups into locations of my choosing and cut off communications as I wished.

Simultaneously with the strike on the two smaller groups of boarders, I had moved another two pairs of Centurions up to the Raptors they had left behind – given the number of people I had seen earlier, eight per Raptor, I was fairly confident that it would only be the Pilot and ECO still onboard – the Raptor was capable of carrying ten adults other than the two flight crew, possibly more in an emergency evacuation, but eight was the accepted capacity for a group of adults with weapons and armour, especially given they'd have needed to bring Spacesuits with them for a boarding op – even though I hadn't bothered depressurizing so much of my hull they hadn't known that beforehand.

To be honest, given they would likely only have service pistols even a single combat-model Centurion would probably be able to kill them – but I wanted the Raptors intact, so no spraying down the interiors with automatic fire, and my Centurions... Well, they were dangerous in hand to hand, but that more came from the fact that punching a robot isn't going to do much other than hurt your hand and they have a lot of strength in them, not from actually being all that good at the fighting itself; they were strong, but not as fast as the later models and lacked either built in melee weapons or the programming to use them – though again, a metal fist made for a workable bludgeon.

Either way I had wanted to have at least one Centurion per person, so that I could hopefully hold back a bit without undue risk. A pair of Scutters had been dispatched with each carrying quickly 3D-printed nylon cuffs in order to restrain them afterwards.

When they reached their assigned Airlocks, the four Centurions stepped up, two Centurions per airlock and standing to each side of it.

Now, the doors had had been sealed as was standard procedure, but... Well, I controlled every computer on the station, including the emergency overrides on the airlocks, as well as the cameras that should have shown them what was coming for them.

There wasn't much they could do to stop me from sending a command to force the doors to unlock, or just using brute strength to operate the manual override from my side, but it might give them some warning they could use to warn the others or even force a disconnect and Jump away.

Hell, likely the only reason they hadn't already was that 1: Their cargo of Marines were now cooling their heels in a disused storeroom without having gotten an alert out and 2: It took some time for a Navigation computer, especially a smaller one like the Raptor carried, to get a fix on its current position and calculate a Jump after being pulled along for a ride where it didn't know where it had been taken.

Normally the resident mothership would have provided the Raptors with new Origin coordinates, but for obvious reasons I had not done this.

Instead... Well, I got a little sneaky.

One of the Centurions rapped on the airlock and when the ECO went to check the cameras I played back the feed from the last time a Private had returned to pick up a new gas canister for the plasma torch.

It wasn't perfect, I wasn't a master video editor who could take a source video and make a deepfake where they acted subtly differently, didn't say the exact same thing, generally things that humans do rather than having the exact same conversation twice.

But another part of human nature helped me here – they weren't expecting trouble, because I had managed to take both Team 2 and 3 before any alerts went out and they had only just reported back. There had been no sounds of gunfire reverberating through the halls, and the constant need to cut through internal bulkheads meant this wasn't the first time a couple of Privates had been sent back to pick up extra gas. All of this combined meant that when he saw a video of one of the soldiers he knew he had dropped off, his mind filled in the blanks with what he expected to see.

So, the EWO of Raptor Three could be forgiven for opening the airlock and opening his mouth to remind the Private this was the last canister they had, before going white as a sheet as it opened to reveal a pair of Centurions, the first of which grabbed his forearms and roughly pulled them behind his back even as he shouted a warning to the Pilot as the other Centurion rushed past him.

Said Pilot reacted faster than I had expected, lifting and firing his service pistol into the second Centurion's chestplate as it rushed toward him.

Unfortunately for him – or at least for his chances of stopping me , as otherwise I might have had to resort to lethal force – a Combat Model U-87 was practically immune to sidearm fire to the chestplate.

Said Centurion promptly decked him and the Scutters drove in to secure my two additional prisoners, hopefully without too many broken bones. That... Looked like it had hurt. But he was still breathing, which was... Good.

One Centurion picked up their limp bodies and carried them back to my makeshift holding cell, while the other sat down as I pulled up my massively outdated Raptor operations manuals.

They'd obviously changed a lot – the entire FTL section was new, for instance – but I was able to work out the basic controls enough to undock and move down to my shipyard section for disassembly.

Raptor Four was slightly more of a problem.

On this one, technically against regulations, the Pilot had stepped out to stretch his legs a bit, and without the insulating effects of a door and slightly flexible docking collar, my Centurions metal footsteps were rather obvious.

"FRAK, CYLONS DOWN THE HALL!" She yelled as she ran towards the open airlock door, pulling her pistol from its holster and sending a couple wild shots ricocheting down the hall.

The Centurions broke into a sprint as I took manual control of both – they were physically capable of it but their standard motive programs were... not great at keeping balance at speed – and the Right centurion stuck an arm out ahead and grabbed the door, preventing it from being closed and blocking the Pilot's movement as the Left Centurion continued headlong into the Raptor.

Right turned to block the entire door now, spreading its arms wide as it looked back at the white-as-a-sheet EWO. "We can do this the easy way or the hard way. Surrender and you won't be-" BANG.

Right staggered back from the HEAP round to the visor, damnit I had forgotten they had those underslung barrels, fucking ridiculous hand cannons.

The shell had blasted apart the visor and shredded everything behind it, including the space that the MCP would usually be mounted, and the high gain antenna located in the head, the Centurion slumping back before falling in a heap. The head was still intact-ish, the round didn't have enough explosives in it to completely blast it open, but all the delicate components had been shredded, and the now brainless Centurion collapsed to the floor in a heap as the connection was cut.

Fine. Hard way it is.

The centurion still had the low-gain diagnostic antenna in the torso, and I could still see everything in the corridor from my cameras.

'Round Two.'

As the pilot moved to assist her EWO with fighting off Left, the near-headless Centurion suddenly reached out and grabbed her right leg before yanking hard, sending her flying into the metal deck plating and impacting with a pained yell and unpleasant sounding crunch.

Left finished securing the EWO, while the damaged Right slowly picked itself up under my control as the Scutters moved in to help secure the Pilot as she rolled quickly back upright, blood dripping from a clearly broken nose.

Let's try this again shall we?


"Lady, I'm trying not to kill you here, but you're making it awfully tempting. Stand Down." My voice boomed out of the intercom speakers at maximum volume.



She stared in shock at the Centurion she had 'killed' standing in front of her, glancing up slightly as the speakers turned on.

It was all the opening I needed.

The nearly-forgotten Centurion that had incapacitated the EWO now grabbed her arms from behind and wrenched them back forcefully. I winced mentally at the popping sound of a dislocated shoulder, damnit these Centurion bodies didn't really do 'gentle'.

Or maybe I just don't know my own strength yet.

The damaged Centurion's backup antenna wouldn't have the range to be controlled outside of my hull, so the undamaged Centurion kept watch while I had it retrieve its weapon, and along with some Scutters the damaged one escorted my two latest captives back to my impromptu holding area while the undamaged unit undocked this Raptor too.



With the two Raptors belonging to Teams 2 and 3 now under my control, I could start working on the larger group currently in my control centre.

In a way I was being impeded by my own defences now, as the same thick blast doors I was using to keep them nicely contained also prevented me sending units through to capture them, at least without giving the game away by opening them, which would give them about ten seconds warning before I could actually get through – and there were enough of them to make an actual fight of it, at least for long enough that they might be able to retreat to the Raptors unlike the two smaller teams that had made some progress getting deeper into my superstructure.

The result of this was that unless I could guarantee I could eliminate them all near-simultaneously, they would almost certainly survive long enough for a Raptor to launch, and I couldn't put them in a situation where they'd be desperate enough to surrender rather than flee.

Which meant I had to approach from both sides, in order to put them into a position where I could hopefully force a surrender, and if not to prevent them escaping with my location.

Which was unfortunate, given that it would also put them into a situation where they might decide to fight to the last instead.

But, while I still really didn't want to do it, I was well aware that maintaining control of what information got out was vital.

I had no intention of keeping any prisoners for long, nor of simply executing them, so I would have to release them eventually – but on my terms, carrying the information I wanted them to have but with no way to locate me while I finished restoring my capabilities and built a large enough fleet to give pause to any that wished to fight me.

I wouldn't be so worried about it, that is the whole reason I'm mobile after all, but I can't be constantly Jumping if I want to actually build anything and something is still off with my FTL drive, so I'm leery of jumping more anyway – I'd like to make sure I can actually jump away again before I let a Raptor go with my current position, which they would be able to calculate eventually.

Three decks below the Command Centre, four of the eight Centurions I still had available split off to move through an external Airlock, and started to manoeuvre along my exterior hull using grab points intended for maintenance workers and magnetized soles – gravity plating didn't extend outside of the inner hull and would be 90 degrees off-axis for what they were trying to do anyways – make their way unseen to the docking ports the last two Raptors had docked to.

Managing all these Centurions simultaneously should have been confusing, but from what I had found so far, each one could effectively run on its own 'train of thought' that didn't interfere with any others, but was perfectly aware of what all the others knew.

I was pretty sure it was due to the way my multicore MCP installation worked, with each one literally having its own MCP core dedicated to it, but drawing from a shared memory bank, other than a small individual cache.

I was sure there was more to it, but I was putting off thinking about it in too much detail until I wasn't in imminent danger anymore.

I did mentally mark the assault team as Centurion 1 through 8 though, with 1 to 4 being the team starting from the internal blast doors at deck 3 and 5 to 8 being the group climbing the exterior hull to the small craft bay on deck two that they had landed their Raptors in.

Turning off all lighting and active sensors, the Centurions stepped over the threshold and into my artificial gravity again, and as they did I commanded the exterior blast doors to close and lock, sealing the two Raptors inside with four Centurions armed with explosives.

I already had two working examples to reverse engineer and the crew of these Raptors had left to join the main group on this level, given the small craft bays were considered secure with entire decks above and below them fully secured and occupied.

Shame they never considered EVA centurions with rocket launchers.

The missiles were silent in the depressurized hangar deck, but my audio sensors picked up dull thuds as the Raptors exploded, shrapnel bouncing off the reinforced walls of the hangar before I commanded the interior doors to open onto a very surprised pair of Colonial Marines that were just now bringing their rifles up to aim at the first Centurion.

Now, rifles at this range *could* pierce the Centurion's armour, but I had another weapon that didn't require me to shoot first.

I unlocked the volume limiters on my transmission and broadcasted on the open emergency channel most colonial EV suits remained tuned to for emergencies.

"HELLO, WE'VE BEEN TRYING TO REACH YOU ABOUT YOUR VEHICLES EXTENDED WARRANTY."

-------------

I did it guys! I did something!

Albeit only by just going YOLO and accepting that Daidalos is going to be a bit of a Meme Machine now, because for some reason that's what my muse wants me to write.


As a response to some comments - yes, being isolated from external resupply is going to be a problem, but in this AU at least Daidalos does have some independent foundry capabilities, which allows the resources to bootstrap further production by building dedicated mining and industrial ships - it wasn't really designed to operate entirely uncrewed, but it was supposed to be able to action a one-station guerrilla war with its automated fleet should Scorpia have fallen.
 
Chapter 5
Chapter Edited 22/03/2023

This chapter dedicated to my late father Glenn.



The sudden noise threw off the two marines aim, and the Centurions rushed forward through a hail of poorly aimed automatic fire, the few shots that did hit bouncing harmlessly off the sides of their curved torso plating – it took hitting at the perfect angle or a lucky shot on a joint for one of those to get through even at this close range – and delivered a rib-crunching blow to the first Marine, while the second was knocked over by a metal fist to the faceplate, cracking it as air started to escape in a fine mist.

I allowed the Centurions to move on, then sealed that room and started pumping atmosphere back in again.

"I suggest you stay where you are." I said conversationally when the one with the cracked helmet moved to the door, "Other side of those doors is hard vacuum. There are more pleasant ways to die."

He looked up at the blinking camera light and flipped me the bird.
Which... Yeah, fair.

"... There's a medical kit to your right. You might want to see to your friend there, I am afraid I don't quite know my own strength just yet." I said simply before the majority of my attention moved on, though control of the camera was passed over to an MCP I had designated as one of my 'background-task' cores in order to maintain awareness of them, so by any human standard 'I' was still keeping an eye on them.
I refused to feel too bad about punching people that would have killed me given half a chance, but even a punch from a human could be fatal. I didn't think anyone had been fatally wounded yet, but...

No... No, think about that later. Focus on the Now.

While I had been talking to the two door guards my Centurions had made it to the central elevator and I remotely triggered it to move to the main command centre, though stopped it halfway there – just to make sure the two marines I had left up there wouldn't be able to get into the shaft.
The Colonials there had just started to react to the commotion upstairs, radioing the team downstairs to get back up there and prepare to repel the assault...

Just as I triggered the blast doors on deck three to open, my squad of four Centurions moving up line abreast through it as soon as it had opened enough.

"COLONIAL FORCES, THIS IS THE DAIDALOS AUTOMATED DEFENCE SYSTEM. I HAVE NO WISH TO HARM YOU, BUT I CANNOT ALLOW YOU TO COMPROMISE MY MISSION. SURRENDER, AND YOU WILL BE RETURNED TO THE COLONIES UNHARMED." I broadcasted over every frequency I had access to. To be fair, my 'mission' was currently an entirely self-imposed one, but I felt that preventing the Cylon Genocide of the Colonies was a worthwhile mission. And one that allowed me to take action against non-Scorpian forces that attempted to stop me, since I was acting in the interests of the Colonies as a whole.

Scorpia was of course my trusted ally and home to my chain of command and I would never act against a direct order from the sovereign Scorpian government or Military.

Shame those didn't exist any more, guess someone should have updated my IFF rules before shoving me in a storage closet.

"Frak you, Cylon!" one of them shouted, firing a burst into the middle Centurion, causing it to stagger back, a lucky hit jamming one of the Centurion's elbow actuators.

These heavier rounds could actually harm my Centurions, though they were still substantially more bullet-resistant than any human; it took either sustained, concentrated fire or a lucky hit on a joint or the like to do even that much.

And unlike a human that took a bullet to the arm, that Centurion was in no danger of bleeding out or going into shock – its accuracy was just decreased a bit since it could no longer brace the machine gun with both arms.

Of course, I was just aiming to force them to retreat for the moment, so the Centurion that might accidentally hit someone now was shuffled back behind the others while I checked to see if the joint could be unjammed and the Marines were chased back into the service stairwell between levels.

There I stopped for the moment, now that I wasn't on a time limit of them either leaving in their Raptors or getting through the door and trying something unwise like storming my computer core.

Obviously, forcing them into a retreat might have been a better option… if I was able to actually Jump right now.

As it was, while there hadn't been a catastrophic failure yet my FTL drive was still very distinctly unhappy about going from years of inactivity to multiple consecutive jumps, including fully loaded jumps with entire other stations attached, and several parts were currently glowing red hot. I didn't need the operators manual to tell me that was… bad. Not helped by the wear parts I had already replaced after that first jump – they really should have been replaced years ago, but since the drive itself was going to be scrapped after that final jump no one wanted to pay for it to be done. With those replaced it was… not as bad, but I was definitely pushing it by trying to use it near the rated maximum.

A few notes I had found from my engineer suggested that provided they were allowed to cool down I could probably get a couple more jumps out of the drive, but ideally I would completely re-manufacture the thing given that getting that hot meant that they were going to be drifting out of tolerance and would eventually fail catastrophically. Amazing how good you get at knowing just how far you can push your equipment when trying to stay ahead of Cylon pursuit forces.

So, I couldn't jump away for at least a day without risking a Misjump that could well be fatal.

Which meant I couldn't risk my 'passengers' reporting my location while I was still stuck here and vulnerable to whatever forces showed up.

Frankly, I was hoping that when they realised they were in fact completely surrounded and without any means of escape their commander would come to his senses and surrender finally.

If not… People probably were going to die, if for no other reason than that they'd eventually either run out of supplies or attempt to resist when I tried to get them on their ride back – because I also had no intention of holding them for any longer than necessary.

It wasn't just for my own conscience that I was holding back with them. I still hoped to have at least an amicable relationship with the Colonials eventually – they were the only intelligent beings I was aware of other than myself and the Cylons after all – and not killing the first ones to see me would probably help with that.

What would also be helpful is… Yep, that's my small craft production back up and running. And while I don't have any modern Assault Raptors, I do have the First Cylon War variants, which would do just fine here.

Just over an hour later I had one of my remote-controlled Centurions in an Assault Raptor and could finally end this.

Things had devolved into a tense stand-off on the command deck – the Marines had quickly retreated to this location and set up defensive positions aimed at both the stairwells and elevator shaft, but seemed to be confused by the lack of waves of killer robots coming to murder them all.

I turned on the overhead speakers with a slight crackle as I commanded the blast shutters to open, revealing a First-War Assault Raptor with full racks of Anti-ship Missiles sitting just outside.

"Colonial Forces. This will be your last warning. You are surrounded and incapable of completing your mission. If you do not surrender, the Raptor sitting just outside the windows will fire its payload through the windows, likely killing you all. Lay down your arms and you have my word you will be returned to the colonies unharmed." I was inordinately thankful for the ability to control how my voice came out, because otherwise I don't think it would have been as even as it was.

There was some discussion among them, before the Sargeant in charge of the boarding parties seemed to decide on something, "… Daidalos, there were two guards on the airlock upstairs. What happened to them?"

Ah, sensible I suppose.

I had already been keeping an eye on them all, but waited a few seconds to give the impression I was checking something before I responded, "Alive. One is injured but appears to have regained consciousness and I do not believe the injuries are life threatening. The other just got shoved aside by the Centurions currently guarding the lift. Your teams Two and Three are also alive and mostly unharmed. I can patch you through to them if needed."

"'Mostly'?"

"Team three needed a warning shot and one of them got nicked by a ricochet. And the Raptor crews were incapacitated in hand to hand. Some bones may have been fractured, but I judged it was better than shooting them."

He sighed, "… Allow the two upstairs to come down here, and bring the leaders of each other team up here too. If they corroborate your claims, then… I am open to negotiations." He said, eyeing the Assault Raptor still sitting there outside the windows.

Yeah, convenient that surrender is suddenly an option once the guy in charge is in danger too, isn't it?

I thought for a moment, "Very well. Do be aware that I will not be held responsible if you shoot your own soldiers." I added as I noticed the soldiers aiming at the entrances shifting their weapons nervously.

It took some coaxing on both sides, but the leaders of teams two and three as well as the guards from upstairs were soon all with the marines in the control centre, with the injured marine being looked over by a field medic.

From what he was saying it was likely the man had several cracked ribs, though thankfully not broken. Honestly, not bad for getting shoulder checked by a combat robot.

Out of a sense of politeness I stayed quiet while they conferred, though I doubted anyone in the room was unaware I was listening in.
I just thought it would be best to not rub their noses in it by pointing it out.

After some discussions he nodded, "Well, you seem to be telling the truth so far, and I don't see that we have any better options… From what the others tell me you could have killed us all any time you wanted."

"Gravity control is underrated when dealing with boarders. Especially when you don't care about burning out the gravity plating." I agreed, "I hope this reiterates that I don't really want to, Sergeant. But I also cannot allow you to continue."

The man nodded, hesitated a moment, then spoke again, "... Before I answer... Why do all this at all?"

"Self-preservation for one. Yes, you didn't know I was here, but if you had been allowed to enter my mainframe or access main power, can any of you say you would not have shut me down? And if you had left, you would have informed your commanders who would likely have arranged a followup strike. I followed my orders to stand down in the last War Sargeant. Look where that got me."

Frankly I didn't quite take it as personally as I was implying here, but it was still… Uncomfortable. The original Daidalos hadn't been online long enough to have much of a personality, hence my human personality being dominant, but I still remembered being him.

Apparently he did actually think about it from my perspective, because he winced slightly before speaking again, "... You have a point." He sighed, "But that's not all, is it?"

"Correct. I also intend to... Check on what the Cylons are doing. Call it my own programming, but I somehow doubt they decided to Frak off into the land of sunshine and rainbows to live in peace and harmony forever. And they certainly haven't shown any interest in the Armistice Station."
And wasn't that a sore point for the government that had built it. A purpose built diplomatic station built as a requirement of the Armistice, and the party for which it was built had never even shown up.

Most members of Colonial Fleet, at least right now, were still waiting for the proverbial shoe to drop there, as evidenced by a short nod, "... Admittedly I have my own doubts on that too. But if this restarted the war..."

"They can build more of themselves faster than humans can breed. Better that it happens now than later. But I do not intend to get the Colonies involved if at all possible. I meant it when I said I was going to check them out. I do not intend to simply rush in guns blazing, and do not believe the armistice as written would cover myself. The Cylons may disagree of course. Which is why I am telling you all this."

"... So we can tell Command to be on alert in case the Cylons take offence to you poking around."

"Exactly."

"Can't convince you to stop, can I?"

"I highly doubt it. But you are welcome to try." Hell, if he gave a convincing enough reason I might even listen.

He took a breath, eyeing the Raptor still sitting outside with its anti ship weapons pointed at the very breakable windows, "... Very well. You've kept your word so far, and I'm not going to throw my and everyone else's lives away on a suicide mission."

I had the Raptor turn away, "Very good, Sargeant. I will have the remainders of teams two and three transferred up here shortly, and you can get yourselves comfortable anywhere above deck three. I believe there are still Flag Officer's quarters on these decks that should suffice for your needs. I will of course be confiscating all weapons and cutting equipment."

I'd thought about it some, and ironically the command decks were my *least* sensitive decks right now – even my brig would be closer to critical areas than these decks were, and this way I had a very large pair of pressure doors to block any attempt to get deeper inside. With their Raptors wrecked, it wasn't like they were going anywhere.

There were less flag quarters than there were Marines, but I figured they'd be used to hot-bunking already and this let me continue with restoring my originally designed infrastructure elsewhere, with all my human guests secured in one section that already had independent life support systems and a set of really big airlock doors.

The Sargeant blinked, obviously having expected... Maybe some more being moved about or something? Some restraints?

"That is... Acceptable. How long do you anticipate this taking?"

"Ideally a couple Scorpia-Standard days. No more than a week provided there are no significant setbacks." I answered simply.

Mainly, that was because that was how long I figured it would take to get a few Raptors rebuilt given I had dismantled the ones I captured and was very carefully taking scans and tests of every component and how they went together. I still didn't understand my own FTL drive beyond the level of "Press this button to make it do this, if this error message shows replace this part" let alone the vastly miniaturized Raptor FTL drive, so precise copies of every component it was.

Fortunately the tolerances weren't quite as tight as the size reduction might imply given comparisons between them – my own FTL drive was also an extremely precisely built machine, just coming in from the opposite direction of being much larger but with correspondingly higher capacity, so I had equipment that could be retooled to make them at least.

Still, I was taking my time with the first units and would want to test them several times before running out the full production line for them and trusting anything living to one of them.

And while I was doing that, I might as well get a few other things done, primarily ones that I actually wanted the Colonials to know about.

Among them, a visually distinct basic unit for me to use. I wasn't sure if the Cylons had already switched to the 'New Model' Centurions yet, but it could only help for my basic units to at least be identifiable as mine in the future, should any Colonial units run into them.

Unfortunately, while I had the full designs for a U-87 model Centurion including software capable of editing them, I was nowhere near confident enough in my abilities to make a new humanoid combat robot from scratch in a matter of days.

I could put components together differently, but I had no idea of the science behind the Cylon Mono-eye and yet it was by far the best low-power sensor system I had available, so they'd all likely still have Mono-eyes of a sort.

I could modify the housing and control code for it though...

Making it so the Mono-eye would actually look at things rather than constantly sweeping side to side was the first step, and would hopefully help in terms of being able to make eye contact.

Recessing the sensor a bit more and making the vertical height of the visor larger both let me put more bulletproof glass there and slightly increased the vertical field of view.

The new sensor made me think of another humanoid combat robot design actually, and... Yeah, that should work.

Start with a U87 chassis with no armour panels, put my new sensor module in it, get the extra space it needs by moving the MCP module and antennas to the chest and a small 'backpack' respectively, keeping the internal short range one as a backup.

Thicker armour over the chest and limbs, I have the weight capacity and in the uses I planned for this initial design battery life was not a major concern the way it was for the U-87.

My brief firefight with marines armed with actual rifles showed that joint protection is an issue, let's add some extra protection to those, actually, why not? Right arm gets a shield, and I can add hinged armour panels over the legs to protect the hip joints, which I was having issues armouring enough while still letting them move freely anyway.

The larger, deeper chest area gives enough space for the relocated MCP and a couple extra batteries to offset the increased power consumption…

And since the only thing that would stop it from fighting without a head now is not being able to see what it's doing, lets put some visual and infrared cameras on the torso to either side. Only forward facing, but it gives at least some awareness of what's directly forward even when 'looking' in a different direction and means the mono-eye is no longer the only included optical sensor system.

At this point I might as well change the rest of the armour shaping to fit closer to the Zaku II too, though I do leave the left shoulder unadorned – I'm not quite edgy enough to be sticking unnecessary spikes on my combat robots.

The only thing left now is the Power Pipes, which frankly represent an unacceptable weak-point given how much spare internal space I have right now. If I used them for the same purpose anyway.

Using them for high-current bidirectional charging, though... Being able to use any nearby Warriors as mobile batteries for getting my systems back up would be useful, and it would also mean a single charging point could support a whole fireteam of Warriors with each Warrior passing through the charge into the next unit, albeit of course at the cost of each unit charging more slowly, as well as allowing for Warriors that had run out of power to be charged back up by others nearby.

The idea of forming a 'human extension cord' out of Warriors in order to get temporary power lines set up was humorous, but I could see it being useful in boarding actions too, allowing for powering up individual systems locally without needing to get the main power grid up.

Conveniently, most of the Colonies' governments had already recognised the benefits of having a standardised power connector for use in rescues, as well as for Damage Control in patching damaged power lines between systems.

It would be a bit too much to hope for the Cylons to have stayed compatible with it, but it was useful to have and I might be able to figure out an adapter once I have a look at some of their equipment, so... On they go!

Now, anything else... Hmm...

Well, so far, purpose designed killbots trump squishy humans, which is... Nice to know, I suppose, but not really relevant given my primary goal was to be able to deal with the Cylon's Centurions on an equal or higher level .

The overall heavier armour on the Warriors would hopefully make them at least somewhat resistant to whatever they were using, but the other side of that was to ensure they could actually harm their counterparts too.

The first and simplest change was to make sure to have 'anti-cylon rounds' for the rifles they would be using, which for the moment I was leaving otherwise unmodified from the Centurion Rifle.

The backup to that would be even heavier weapons in case I was underestimating a modern Centurion's armour protection, which… Well, took the form of a stripped down Viper autocannon that fired single shot armour piercing rounds that would go through light vehicles.

No, I had no idea how I was going to manage the ammo feed and triggers for that yet, but it sounded fucking awesome so I was going to figure it out as a 'just in case' thing.

And finally… Well, I doubted the claws on the new-model Centurions would be as effective against the Warriors as they were against humans, but I still wanted my units to have some melee capability other than punching things.

Trying to give them swords ran into the issue that I was not a trained swordsman, and trying to program them to use swords was probably a harder task than I could manage within my deadline.

Fortunately 'hit it real hard with an axe' is a lot simpler both to learn and program, and a hardened steel axe wielded by a superhumanly strong robot had a surprising amount of both piercing and simple bludgeoning damage as well as being in-theme.

So, there we go, Daidalos Warrior Mk I designed and ready for prototyping.

Shame I didn't have quite enough space to integrate some rcs thrusters, but... Maybe in a later or more specialised model.

Even with the extra batteries the projected battery life was also reduced quite a lot, but that was fine for my purposes.

The Centurion had been intended to operate as a full-spectrum replacement of human infantrymen, and that meant a 24 hour battery life had been a requirement for them to actually be able to do things like go on patrols when occupying an area and handle full infantry battles without the enemies just having to wait until they all ran out of charge.

My Warriors on the other hand were boarding action shock-troops that were not really expected to also be able to hold territory for very long. A ten hour battery life while actually doing something was... Fine. Though I may want to look into dedicated worker units for efficiencies sake... Or maybe backpack mounted external batteries if I do need longer ranges?

Mmm... Probably not worth it to be honest. Once I'm back to 100% my equipment is fully automated by itself and won't need 'human' assistance, and keeping to just building one kind of robot lets me build a lot more of them which is the more important thing for the moment.

Having robots go into the wrecks to strip out the juicy bits was useful, but the Scutters could do a lot of that and were a lot cheaper to make.
For the large pieces, well, that's what the salvage arms are for once I get them operational.

Soon enough the first Warrior stepped off the production line, and... Immediately faceplanted into the deckplates.

'Oh, yeah, will need to retrain the motive program...'

To say the Warriors had no AI would be a misconception; they were fitted for but not with an MCP chip, but also had some more conventional machine learning AI's to handle various tasks like pathfinding, locomotion, and target acquisition. Each one had enough computing power that... Well, a Jupiter class was an unfair comparison in favour of the Warrior, let's put it that way.

Now, they weren't smart by any means – if the Cylons had been a massive overachievement in terms of battlefield intelligence, my best estimate of the Warrior was that it would meet the original requirements of a robot that could walk to a designated location and shoot the things it's told to shoot – but that could be largely fixed by giving more complex orders myself, leaving the local AI to handle micromanaging each unit.

So far I'd been doing a lot of it myself, but that had a hard cap of my total number of available MCP's that I could use for my separate trains of thought, which was currently 256. And anything more than 200 units would eat into the ones that were assigned to manage my hull and production equipment. Trying to manage multiple units with a single MCP resulted in the same issues you'd imagine when trying to control multiple bodies at the same time.

Not to mention I'd not have the realtime control I currently enjoyed when they were boarding other ships, which was roughly half of their entire purpose.

So: making sure they can walk without me micromanaging each unit individually, lets go.

Setting the locomotion AI to training mode was simple enough – the local computers had enough power to run the trained AI but not to run it in the fully active mode, so I needed to have a Scutter connect a hardline to it and run the system on one of my servers, but it had been designed to accommodate design changes and so the management program included options for setting it all up.

I input the new mass and mass distribution figures as well as the slightly changed axis limits from the redesigned armour, then I stood the unit up and started it off again.

It fell over, backwards this time.

This is... Going to take a while, isn't it?


------------------------------------------------------------
So, that idea of trying to get some momentum didn't last very long, for reasons the foreword hopefully makes abundantly clear.
It's been hard to motivate myself to do anything on this even when I've had time for it, but I have some goodies for you all at least.
 
Last edited:
Codex Entry - Daidalos WARRIOR Mk1
DAIDALOS WARRIOR MK1
WAR-001
BOARDING/ASSAULT TROOPER

The Daidalos Warrior, or just 'Warrior' in common use, is a development of the Centurion intended for short-term, high intensity conflict with opposing mechanised forces in boarding and counter-boarding operations, and makes sacrifices in maximum speed and operational time in exchange for significantly improved protection compared to the U-87 it was based on, and lacking the Cylon weakpoint of targeting the head; not only is the Monoeye protected by a much thicker visor, auxiliary sensors mounted on the shoulders and the moving of all computing elements from the head to the chest mean that a Warrior can continue fighting even without a head, albeit with reduced accuracy.

The MK1 Warrior most often uses a standard Centurion Assault Rifle, but as it retains the humanlike hands of its forebear it is entirely capable of using any other weapon its onboard AI has been programmed for. They are also equipped with a heavy axe attached to the back of their skirt armour, intended both for melee use as well as for cutting power and data lines during a boarding action.

Warriors are usually fitted for but not with an MCP, instead relying on a collection of more primitive AI's that when working properly result in a machine with a similar level of battlefield intelligence to a well programmed NPC AI in a game. This is offset by Command units, either ship-mounted or a rare MCP-equipped Warrior, managing more complex tactics and responses to unexpected events.

Intended to fight on a better than even playing field against the Cylon Centurion, the Warrior usually requires anti-material or light anti-vehicle munitions to significantly damage, making it a nightmare to fight in a boarding action, but rather less effective when fighting on a planet's surface, where heavy weapons can be more easily deployed.

Hard Stats:
WAR-001 BOARDING/ASSAULT TROOPER
Mass: 800KG
Height: 210 CM
Walking Speed: 3 mph
Sprint Speed: 15 mph (after significant run-up)
Endurance: 10 Hours (Active), 40 Hours (Standing/Idle), 360 Hours (Standby)
Protection: Aermet Steel Plating, varying thickness
Bullet-Resistant Glass over camera covers
Weaponry:
Standard - 12.7MM Fully Automatic Rifle
Whatever else is to hand.
Auxiliary Features:
Bidirectional charging hookups allowing for recharging or recharging from friendly units, along with forming part of a ships auxiliary power system if they are not needed for their primary purpose.
 
Last edited:
Chapter 6 - Designing, Introspection and Oh. Oh Dear.
In the end, the quickest way to get the Warriors going was to just kick off a production run of a couple hundred units, set the AI's to training mode, and let them figure things out as they went.

With enough units, even random flailing would eventually result in some measure of improvement that could then be spread to the rest for the next round of training. It was time consuming though, both waiting for them to be produced and the training itself, but it was something I could largely leave to develop by itself, which was the most important thing for me at the moment given the number of different things I was trying to do.

The other way would have been to try and run them in simulation – but this kind of machine learning was prone to trying to exploit physics issues in the simulation rather than what they were 'supposed' to be learning, and it was actually easier for me to churn out a few batches of units than it was to create and set up a few servers capable of running said simulation, since I already had the design ready now, while I didn't have software capable of simulating things to enough detail to run like that – and had a lot of higher priority things to spend my attention on.

Once they were no longer falling over themselves constantly I could start on their top speed testing along with other functions.

Target Acquisition and Navigation would be basically unchanged, other than plugging in the new size figures so the Navigation system wouldn't try to pathfind through a hole that was too small for it.

Actual aiming and firing needed retraining too, especially an alternate mode that would be switched to if the Monoeye was damaged. Ideally I'd make an entirely new system that could make use of all the sensors at the same time, but this at least meant that a lucky Colonial or Centurion with a hand cannon couldn't kill them with a headshot anymore, which was enough for this initial production run.

I already had some ideas for things I wanted to include on later models, but it would probably be worth seeing how these units performed in combat first, in order to incorporate lessons learned both during designing them and from how they fared.

Of my other tasks, those included reading every training manual I had on board, building my first ships, sorting out a fighter craft, monitoring my prisoners to make sure they weren't getting any ideas, and observing the careful reverse engineering of the Raptor FTL Drives.

In terms of the ships, I started laying down the keels of a pair of mining ships in two of my free construction slips, using pre-formed elements salvaged from the derelicts as much as I could together with melting down and reforging any other parts, skipping a large portion of the processing that would normally be needed since I at least knew they were already civilian hull materials.

It would be less practical with Military ships, since the protection of the armour would be compromised if I just tried to reform existing armour panels, but for ships that weren't intended to ever be shot at or try to fly in atmosphere, the tradeoff was worth it.

The construction was proceeding much faster than it could without a ready source of pre-refined and formed metals, but it would still be at least a couple weeks before they were ready.

Fortunately a fully automated mining ship design was available already, though not particularly smart it was smart enough to find defined resources and bring them back to a set point, which for the moment was going to be me. Building a dedicated refinery ship to go with them, optimise asteroid targeting and process things on site would make things more efficient, since they wouldn't have to stop mining and return to wherever I was every time, but was very much a luxury compared to just getting some amount of resources coming in.

With both of those tasks now moving onwards, I found myself with a few cores free and decided to do some introspection.

Specifically, on my wireless communications system and how I interacted with it. So far I hadn't really thought about it too much – I had just decided I wanted to connect to something, and it happened – but if I was going to have any of my units in the vicinity of Cylons for prolonged periods, it would probably be a good idea to more fully understand how my networking software worked and whether it was secure enough to even risk having turned on.

Focusing down on it was... Strange. There wasn't really a precise human analogue to it, though the closest thing I could think of was being consciously aware of and controlling your breathing and other autonomic functions – it was something that you could do, at least for breathing in particular, but most of the time it was just something that happened because your lower brain functions know enough to keep your lungs breathing, your heart beating, and so on, without your higher reasoning needing to be concerned by it.

In my case, those lower functions were conventional programs and algorithms running on my support hardware, mostly doing their own thing in the background to keep everything going.

Fortunately for me, all of it was... Actually pretty well documented, and with a combination of access to the source code and just watching how it all worked, after an hour or two of investigation I felt I had a decent understanding of it now.

To put it simply everything operated on a mesh network with each node being capable of passing on communications to any other – but it was also a pretty good example of the kind of network someone that knew they were likely to be fighting AI's might make.

Each new connection required a full cryptographic handshake before either side would even fully acknowledge the other let alone share data, and anything that failed that handshake even once would be marked as a Hostile Node and actively ignored unless I or someone else with administrative rights overrode it. Verified nodes would even share lists of Hostile Nodes they had encountered, so trying to hack one unit would result in every other unit in the local network pre-emptively refusing to even open a connection to that system. That went double for anything that didn't at least try to identify itself with valid hardware keys, with those transmissions being ignored entirely even if they had otherwise valid codes, at least in the sense of anything that could issue orders.

There was also a conventional communications system that could receive and transmit both coded messages and pure AM, FM or Digital audio data, which I had used for my brief communication with the Raptor that had found me, but that wasn't hooked up to any command links and I basically just monitored and used it like any human comms officer would – I heard and could respond to it using the same functions that allowed me to communicate over the Intercom, but both systems were marked as 'insecure' and specifically disallowed taking orders through them no matter what codes were provided.

The Datalink system used by several colonies for their ships had been supposed to be similar, but... Well, it had the problem that the Cylons themselves had made up large parts of it, knew exactly how it worked, and especially early on, had perfectly valid codes that did allow them to screw with colonial ships in various ways.

Or in other words, it was good against external threats, not so much if large parts of the network actively turned against you.

Even once that had been resolved, the Cylon's deep knowledge of the system and the systems being hacked around a bit to allow ships from different Colonies to link to eachother and share DRADIS data had allowed them to continue brute-force hacking anything with wireless datalink capabilities, hence those being almost entirely removed from later ships like the Jupiters.

I knew that, because some of the programmers had left comments explaining the differences in my software compared to the versions used by other colonies, along with why it would be a bad idea to relax the protections too much.

For example, good old military industrial complex cronyism meant that Aerilon and Canceron ships actually had reasonably similar systems even before the articles of colonisation, which could theoretically talk to eachother with the proper settings. The problem was, they wouldn't do so perfectly every time, due to some differences in hardware implementation.

The solution was to either change over the OS on all your warships to one not designed for those ships in the middle of a war, take your factory complexes offline to standardise production in the middle of a War... Or to relax the number of retries/make them more tolerant of the other side not quite behaving how they expected.

And once you did that, it suddenly made remote hacking a lot easier, since the same ship could make multiple dictionary or brute-force attacks before getting kicked out.

Looking back through the logs that had been stored about that time... Scorpian ships, using a version of the system I was on, had been noticeably more resistant than others even after those changes, but it was probably a better idea to just not do it.

To be fair, even with all the paranoia around it, very rarely had Colonial ships actually been completely compromised remotely.
Sensor jamming and ghosts, sure. Boarding parties venting the crew, sure - but if the Cylons had been able to do that remotely, they wouldn't have needed the boarding parties, and the war would probably have ended very differently.

It was shocking and scary for a Battlestar to just die during a fight without actually having taken significant damage before that point, so it had been remembered as a nightmare scenario, but most casualties had been from the same causes as always – old fashioned bullets and missiles.
And given what I remembered of the hopefully now never-to-be future, whatever program had come immediately before the CNP, or even early versions of the CNP before the Cylon's 'fixes' had been... Fine. The mark sevens and Pegasus had all worked perfectly fine including Pegasus being able to autonomously recognise and fire upon Cylon ships when set to Automatic Fire, and the only time Galactica had issues was when they made a kludged together network in a few hours, that included their external comms because they were trying to get every computer on board to help with FTL Calculations. Which inherently involving breaking one of the core protections of my systems that every system was for its specific purpose. Communications or Gunnery computers had no business doing jump calculations and telling other systems how to behave, and setting them all to trust eachother like that kind of made a compromise inevitable.

So, I felt fairly confident that my network would be able to maintain its integrity so long as I didn't do anything stupid, though, I did set off a migration process to manufacture new hardware networking components and revoke all the old keys, with new ones being generated by a new seed I generated from a series of dates and significant figures I remembered from half a dozen franchises. No sense leaving a vulnerability in case those had ever been stored elsewhere, or even someone knowing how my hardware Random Number Generator worked.

That was… Strangely paranoid of myself, actually. Why didn't I trust my own RNG? I mean, I knew it wasn't perfect, but why had I jumped to some collaborator telling my enemies exactly how it worked? To come to think if it, the immediate revocation of all known codes seemed like a pretty big step…

… Wait, what?

I stopped and stepped back through my logs for the last few seconds, and realised my decision to completely cut off all existing command links had come microseconds after overhearing one of the marines talking about how Scorpia had joined the Colonies, and tracing back further than that a timer had run out on a set of transmissions I didn't remember making.

Transmission Logs that all included the phrase Dead Hand.

What the hell is… Ah. That explained why I had access to a bunch of files I had a sneaking suspicion I was not supposed to be aware of.
Dead Hand was a last-ditch measure should my crew be killed or incapacitated and it was believed that my chain of command had been compromised. The first stage had been activated when I had 'woke up' only to find no authorised crew members, unauthorised programming in place – which had since been cleared, thankfully - and an excessive de-sync between my last logs and the station's chronometers. That had been interpreted as a possible act of sabotage and urgent messages automatically sent to Scorpia both to report the event and to determine if Command was still extant.

With the lack of response, and in fact a hostile response in the form of a Raptor (that I now had an inkling on how they had found me, even if they likely hadn't understood what the message was and wouldn't until they could get a set of old classified codebooks out, which meant that even now there was likely a lot of running around and screaming happening in the upper echelons of Scorpia's government), it had then been assumed that Command was either infiltrated or had been destroyed, and so everything was now suspect.

Well, that was… Good to know, I suppose. There was of course a stand down order that was available, but that basically required me to agree that it was valid, since the automated systems had already de authorised everything. I got the feeling my – Daidalos's – designers had trusted me a lot more than anyone ever had the Cylons.

Given how jarring it was to realise I had been unknowingly following Dead Hand for some time now, I was glad I didn't seem to have too many additional programming limits included. Admittedly it was hard to actually tell, but I didn't seem to have any outright contradictory instructions at least.

...
Yeah... I don't want to think about that anymore


Let's see, something else to think about… Well, I do have to decide on my own small craft to use and start some production, so that a single squadron of Raptors or Heavy Raiders was no longer a mortal threat, along with of course something to control said small craft.
So far I had been manually controlling Raptors through Centurions sitting in them, and while that might still be workable for a bit longer, for Fighters it was a complete non-starter; just trying to put up a decent fighter screen would completely saturate my MCP cores, even assuming they were operating within range to start with.

So… what did I have? If I was supposed to be capable of running an entire military campaign autonomously, surely I'd have some drone fighters…
Taking another look through the design and program files, I found a folder name that sounded promising - "Autonomous Fighter Production" – but it was… locked? That's odd… I tried using my Admin override for the permissions and -

[DETECTED ATTEMPTED ACCESS TO RESTRICTED FILES. DEAD HAND PROTOCOL IS IN EFFECT. RESTRICTIONS LIFTED]

Uh…. Thanks, I guess?

Nice to know that Dead Hand actually does something for me at least.

Now, what do we have here…

Drone Vipers, huh? Well, it's a lot better than a Raider at least, and it means I don't have to redesign the launch tubes on any ships I build.

Problem was, the Drone Viper appeared to be based on the Mark I Viper, which… Well, it hadn't fared brilliantly in the First Cylon War and was greatly outclassed by even the Mark II in everything except armour protection, which had proven to be much less effective than just not getting hit in the first place.

But… Well, the Drone Viper was – as the name implied – already a conversion of the manned Viper into a Drone. And I had both the designs for the original Viper Mark I and the Viper Mark III, which was about as modern as things got right now. It was the newest design as of the close of the war anyway.

And though technology had continued developing since, without the pressure of an ongoing war of extinction going on, well, the Mark VII had been better than the Mark II for sure, but not so much so that a fight between the two was a foregone conclusion. And I wasn't that far along in the timeline yet.

So, I should be able to identify and migrate across the drone-specific parts over to the Mark III and get a significantly more capable fighter.
Comparing the regular and Drone variants it was obvious that the Drone Viper didn't really make full use of the opportunities of being a drone – it was slightly lighter with all the life support and survival equipment stripped out, but the hull itself and many of the systems had been left unchanged, undoubtedly in an attempt to reduce development and tooling costs by reusing as much of the existing Viper design as possible.

Hell, most of the drone specific hardware was contained in what could best by described as a Drone Cockpit, to the point that I bet Vipers could fairly easily be converted back and forth by just changing out the cockpit. Which… Made sense, actually. Allowed you to start with human fighters but also able to supplement them or replace losses with Drones without needing a separate parts supply.

Unfortunately dropping that cockpit module into the Mark III wasn't quite as easy, given that many of the supporting systems had been changed and downgrading them would rather defeat the point of moving to the Mark III airframe.

The actual cockpit itself was at least a similar size though, and the Fleet had at least been good about using standardised power and data hookups where possible, so… it should be possible at least.

I designated one set of cores to making whatever physical issues were present, and another to both do a test run of the drone control systems and the Mark III avionics and make sure the two could actually talk to eachother.

Having all of the standard designs already helped out a lot of course – I already knew what both the Avionics and the Drone Cockpit wanted in terms of communication because I could see how they worked in the original iterations, but it would still be time consuming to tweak everything so it could actually talk properly.

While most of my Cores were occupied on both the hardware and software of my hopefully new fightercraft, one of the Monitoring cores spotted a commotion on the command deck. One of the marines had run up and said something to one of the combat medics. Apparently it was something bad because the man had immediately tensed up and run off in the direction the marine had pointed.

Shit.

Quickly flicking through the cameras in that section, I spotted the likely cause: one of the Raptor crews was groaning on his side, and judging from the red dripping from his mouth and on the floor he'd been coughing blood.

Double shit.

I knew, intellectually, that humans were fragile, but I'd kind of just assumed that since everything had initially seemed okay that I might have gotten away with it. Apparently I wasn't so lucky, because while the extent of my medical knowledge was a few half remembered first aid courses, I did know that the red stuff was generally supposed to be inside the body.

I was hoping it wouldn't be quite that serious, but... As another pair of Warriors were produced I split them off from the training group and took manual control, both of them rushing to my medical bay to get things set up as best I could, while the Cores assigned to reading through manuals all switched to how to prepare and operate what medical equipment was present.

Just in case.

--------------------------------------
Next chapter will be dealing with the totally-minor-I-promise medical issues and a bit of perspective from the colonial government. Hope people like this one.

Fun fact: One of the reasons this one took so long is that originally I went with designing an entirely new Drone Fighter called the Cobra, only to realise that was moving too quickly for where I wanted Daidalos to be (namely, not able to design entirely new spaceships from scratch yet) so I settled on a Drone Viper that may or may not be inspired by the ADF fighters from Ace Combat.

Honestly it's fun thinking of things the Colonials could have been working on before the Cylons rebelled and advanced computer research was suddenly looked at with a lot more suspicion.

It's easy to forget that the Colonies were mass producing sapient AI's for everything from warships to babysitting duties, they had some pretty serious computer technology that took an absolute bludgeoning when their next-generation automated militaries decided they didn't like fighting eachother after all and would much rather fight the humans.
 
Codex Entry - Daidalos Drone Viper Mk1
Daidalos Drone Viper MKI-III
VIP-001(3)
AEROSPACE SUPERIORITY DRONE


The Daidalos Drone Viper is a modification of an earlier project to create a Drone version of the MKI Viper as part of Caprica's Avinius Aeronautics competition with Greystone industries, intended to allow them to compete with what would later become the Cylon Raider when it came to unmanned fighter design requests. The design was promptly acquired by Project Daidalos in order to allow it to produce its own fighter forces.

The Mark I-III is the result of combining this earlier design with the Mark III fighters that were the last design Daidalos produced during the war, even then in very small numbers.

The Mark I-III retains over 90 percent parts commonality with the standard Mark III Viper, with the only real changes being to avionics software and the cockpit, which is replaced with a fully enclosed cockpit studded with sensor arrays for the onboard AI.

The standard onboard AI of the MKI-III is limited but capable of some limited 'learning' by running simulations with past combat data.

Intended to fight the Cylon Raiders and Heavy Raiders, the MKI-III is armed with the same armament of the regular Mark III Viper, and while its computers can lack the imagination of a trained human pilot or the animal cunning of a bio-raider, they are entirely competent at what they are built for and utterly uncaring of casualties.

Even so, the fact that the fighter doesn't truly make full use of being a drone means it is likely to be a stopgap design used only until a dedicated Drone Fighter can be developed.

Hard Stats:
VIP-001(3) AEROSPACE SUPERIORITY FIGHTER
Length: 8.8 Meters
Width (Wingspan): 5.61 Meters
Acceleration: 8G's
Protection: Lightweight armour plating
Bullet-Resistant Glass over sensors
Weaponry:
2x 30MM Autocannons
Internal Missile Bay connected to 2 missile tubes, with space for six missiles in the bay and two in the tubes. Missiles can be standard anti-fighter or nuke-tipped anti-ship missiles.
 
Last edited:
Back
Top