Scify
It always starts with a lighthouse.
Okay, so... Ran some numbers. If we go in guns blazing, shields up, and FTL activated for the Athens (since I got the impression that that was a part of their fighting style)... We're left with 80 CPU. I'm not sure what effect that would have on our decryption efforts, given that I imagine the battle won't take an entire month, but... It's something to consider. Regardless, it is an option. I suspect the combat would work more with the FTL going on and off as necessary, but that would still represent a significant computer load.
So! Provisional plans:
[X] Plan 1: Fight!
-- Go in guns blazing. These guys are clearly hostile, and they may well come after you if you stick around much longer. Besides, those resources will look better in your shiny new cargo ship than in their grubby old mining vessel.
---- Minimal/No Decryption during the fight: Can't afford to not have computing cycles when you need them.
---- Target the comms and engines/drive cores (as possible)! They might have friends. Don't let them bring them in.
---- Keep the Jonas and Contessa back. These aren't fighting ships, they have no place being in close combat.
---- Spend the rest of the month harvesting, repairing, and looking at nearby star systems. Nothing stands out as needing to be built.
[X] Plan 2: Maybe we just got off on the wrong foot?
-- Move in close to Group 3, but with our offensive weapons powered down. Try and hail the mining vessel.
---- If they seem to be attacking, enact Plan 1.
[X] Plan 3: Ping the weird thing!
-- Who needs to pick a fight when there is science to be done? That weird object needs investigating.
---- Use the survey drone to try and send a message to it. It (probably) wouldn't hurt to see if it can talk--and if it gets angry, hey, it's just a survey drone.
---- If that doesn't work, send an assault ship in to investigate (with the FTL primed and ready). Give it a good old shot-over-the-bow to try and elicit a response.
---- Have the entire fleet ready to run if it gets angry at our prodding.
Research Priorities (in descending order):
Unknown Data Bank 1 - 500 CPU
Unknown Tiny Module - 80 CPU
Unknown Module 1 - 150 CPU
Unknown Module 3 - 150 CPU
Unknown Fighter Craft - 100 CPU
So! Provisional plans:
[X] Plan 1: Fight!
-- Go in guns blazing. These guys are clearly hostile, and they may well come after you if you stick around much longer. Besides, those resources will look better in your shiny new cargo ship than in their grubby old mining vessel.
---- Minimal/No Decryption during the fight: Can't afford to not have computing cycles when you need them.
---- Target the comms and engines/drive cores (as possible)! They might have friends. Don't let them bring them in.
---- Keep the Jonas and Contessa back. These aren't fighting ships, they have no place being in close combat.
---- Spend the rest of the month harvesting, repairing, and looking at nearby star systems. Nothing stands out as needing to be built.
[X] Plan 2: Maybe we just got off on the wrong foot?
-- Move in close to Group 3, but with our offensive weapons powered down. Try and hail the mining vessel.
---- If they seem to be attacking, enact Plan 1.
[X] Plan 3: Ping the weird thing!
-- Who needs to pick a fight when there is science to be done? That weird object needs investigating.
---- Use the survey drone to try and send a message to it. It (probably) wouldn't hurt to see if it can talk--and if it gets angry, hey, it's just a survey drone.
---- If that doesn't work, send an assault ship in to investigate (with the FTL primed and ready). Give it a good old shot-over-the-bow to try and elicit a response.
---- Have the entire fleet ready to run if it gets angry at our prodding.
Research Priorities (in descending order):
Unknown Data Bank 1 - 500 CPU
Unknown Tiny Module - 80 CPU
Unknown Module 1 - 150 CPU
Unknown Module 3 - 150 CPU
Unknown Fighter Craft - 100 CPU
Last edited: