My stupidest rebuy after thargoid fight
29 Jun 2020Miraka
So here I am at the Bugkiller crash site as friend of mine wanted to collect materials. I decided to keep myself entertained so I got 2 meta alloys on board my cutter and headed down to the planet. Couple of seconds after we arrived at the crash site 2 goids arrived: Cyclops and Medusa. I let the Medusa scan me, but it didn't do the usual "please give meta alloys" cry so when she decided to leave I gave her proper send out ramming her into her hyperspace portal.
Everything was quiet for few minutes and then I heard COVAS saying "Frameshift anomaly detected". Turns out 2 new goids came: Basilisk and Cyclops. This time they were hostile, I guess because of my previous ram of the Medusa. After my ship recovered from EMP I decided to punish the Basilisk first for attacking me.
It was pretty much normal fight with the Basilisk, ignoring the Cyclops the whole time. Now after Basilisk is deleted I turned my attention to the Cyclops, but Cutter against Cyclops doesn't feel fair so I decided to give up my shield and turned off my shield generator (this cutter have only 2400k hull).
I was keeping the fight close to Bugkiller location so my friend can enjoy the show while collecting materials.
When Cyclops had 2 hearts left and I started my attack run to take his third heart I heard COVAS saying "Frameshift anomaly detected". It was another Basilisk, so I quickly took the third heart and boosted while FA OFF to avoid damage while my ship is disabled from the Basilisk EMP.
When my ship recovered from the EMP I turned my attention to the Basilisk while Cyclops shield was still up. I took his first heart and boosted away to avoid his lighting attack.
In the meantime Cyclops shield went down and I gained some distance from the Basilisk so I decided to take the last heart of the Cyclops. While I was sniping the Cyclops heart Basilisk gave up his lighting attack and decided to shoot at me... at that moment I got message "Thrusters offline - zero thrust capability".
It turns out that Basilisk decided to snipe my thrusters. I quickly rebooted while adrift and under fire hoping that my hull will hold up until I get my thrusters back.
When my ship came back on I noticed that my hull is holding on promises and electrostatic forces.
I quickly deployed heatsink and boosted past the Basilisk to gain some distance and in that moment I decided to stop and reboot to get my shields back. I did fly-by, gained some distance, stopped, rebooted and no shields... hmm, maybe I took some damage - time to try again. In the meantime I was using repair limpets to repair hull while gaining distance.
Second try of rebooting and no shields - odd, but Basilisk is fast, maybe he came in range and I took some damage while rebooting.
Fly-by again and after gaining distance I tried rebooting for the third time and still no shields.
My hull is over 50% now, but I continue to repair it while gaining distance from the 2 goids.
Just before forth reboot I realised that I forgot to turn the shield generator back on
Silly meThis time I got my shields back and I quickly finished the Cyclops and then turned my attention to the Basilisk. After his third heart I hear COVAS saying "Frameshift anomaly detected" - another Cyclops came.
After the EMP I continued to fight the Basilisk and ignoring the Cyclops.
The final shots are landed on the Basilisk and now the question is "do I delete the Cyclops too?".
I decided that I already synthed ammo for the second Basilisk so I will delete this Cyclops too. Again - Cutter vs Cyclops is not fair so I disable my shield generator again and start attack run.
I took out the first heart and Cyclops now wants to use his lighting attack on me... so I let him - what is he going to do? drop my shield?
He started the lighting attack and I boosted to ram him and drop his shield. Imidiately after his shield went down I started my attack and took his second heart.
This time I decided not to ram, but to avoid caustic missiles, because I didn't wanted to overheat to burn the caustic (my thrusters are at 1%) so I boosted, but it turns out I boosted straight down not realising I will crash at the ground and most probably die (thats what happens when you fight close to the ground at night time)... in that moment Cyclops decided to use his lighting attack and stopped me from crashing.
Now I don't want to kill him anymore, but he continues to attack me so I took his third heart and boosted FA OFF to avoid damage while my ship is disabled from the EMP.
My ship recovered from the EMP and I am wondering what to do now. In the meantime the Cyclops is attacking me so I took his last heart and decided not to kill him - I left him at 3% and told my friend to log with me to despawn the goid so I don't need to kill him.
We logged off and then on and for my surprise I saw my Cyclops friend still there scanning things with 3% hull. I got 15 seconds timer when I logged so I guess my friend came back just before I log off. Anyway - the Cyclops wasn't hostile so I landed and rebooted to get my shields back.
Now when we're friends with the Cyclops I decided to give him the meta alloys in my cargo hold.
I dropped the meta alloys near the Bugkiller conda, but the Cyclops couldn't get them (I guess they can't scoop from planet surface) and he went to the srv wreckege which is 4 km from the Bugkiller conda.
In the meantime I landed and deployed myself in my srv to collect the meta alloys.
While I was scooping the meta alloys I saw my Cyclops friend returning to Bugkiller conda to scan things there, but he crashed into the hill and exploded
I felt a little guilty, but I admit - I laughed very hard. After a minute or two I started wondering why my srv don't get caustic damage - my Cyclops friend exploded just in front of my srv.
At one point I got message "Mothership hull is critical"... then I realised that my srv doesn't care about caustic damege, but my ship is
I rushed to the ship and stopped at the boarding position, but the ship exploded while I was boarding it.
So long story short - after defeating Basilisk and Cyclops together 2 times in a row a third Cyclops managed to destroy me by killing himself by crashing into the hill