Thargoid invasion - Next target systems?

Has anyone remained to finish Gliese 3050? That has been at 98% for a long time; I could jump the Carrier over there and help finish it, though I had hoped to make a credible push to secure the effort put into Bi Dhorora.
 
There we go; victories in Gliese 3050, Heng and Bi Dhorora! That makes twenty-five systems this cycle; very well done to all!

I will leave it an hour or so before capturing a final scan just before it ends.
 

Week 17, 23rd March 3309​

Report
Alert repelled in HIP 6913, Col 285 Sector VN-Z b14-6, Putas, Gliese 9035, Vogulu, HIP 20485, Lahua, HIP 26688, Cephei Sector CQ-Y b3, Pegasi Sector NY-O a7-2, Poqomathi, Ge, Kagutsuchi, Yan Zangata, Pegasi Sector NY-O a7-3.
Hez Ur, Col 285 Sector UD-G b12-2, Hyades Sector AV-O b6-5, Nu Guang, Namayu, HR 1403, HIP 26274, Ahol, Bhotepa, Baudani, 69 Upsilon Tauri, Elboongzi, Pathamon defended from Invasion.
Control evicted from Ceti Sector ZU-Y b3, Col 285 Sector OM-B b14-7, Col 285 Sector BA-P c6-10, Col 285 Sector TH-C b13-3.

Targets updated at 06:40 30th March 3309
Senocidi Invasion 84% — Taranis 20 Ly, 1 port, 184 Ls starport attack, 467k Ls 0.14g planet damage
Pegasi Sector EB-W b2-2 Alert 70% — Raijin 24 Ly, empty
HIP 20491 Invasion 58% — Indra 23 Ly, 3 ports, 3197 Ls 0.2g planet attack, 3194 Ls 0.19g planet damage
Muruidooges Invasion 50% — Hadad 18 Ly, 2 ports, 7321 Ls outpost attack, 7320 Ls 0.4g planet damage
Paeni Invasion 46% — Taranis 27 Ly, 4 ports, 23k Ls 0.16g planet + 22k Ls planet attack, 571 Ls outpost + 23k Ls 0.4g planet damage
Arietis Sector UO-R b4-4 Alert 44% — Leigong 31 Ly, empty
Col 285 Sector VD-G b12-1 Alert 44% — Cocijo 27 Ly, empty
Pegasi Sector DG-X c1-6 Alert 44% — Raijin 21 Ly, empty
63 Eridani Invasion 42% — Taranis 20 Ly, 1 port, 1698 Ls starport attack, 432 Ls 0.9g planet + 2726 Ls outpost damage
Chelka Invasion 40% — Oya 25 Ly, 1 port, 807 Ls outpost attack
H Puppis Invasion 38% — Hadad 26 Ly, 3 ports, 320 Ls 1.6g planet attack, 1239 Ls outpost damage
Lovaroju Invasion 38% — Taranis 27 Ly, 4 ports, 90 Ls 0.5g planet attack
Awara Invasion 34% — Taranis 22 Ly, 3 ports, 7972 Ls 0.3g planet + 8322 Ls outpost attack, 7971 Ls 0.3g planet + 7962 Ls outpost damage
Laumas Invasion 32% — Cocijo 29 Ly, 3 ports, 255 Ls 0.4g planet attack
HIP 16954 Invasion 28% — Thor 33 Ly, 1 port, 984 Ls starport attack, 964 Ls 0.12g planet damage
HIP 22052 Invasion 28% — Taranis 29 Ly, 3 ports, 174 Ls outpost attack
HR 1812 Alert 28% — Taranis 27 Ly, 1554 Ls planet
HIP 28150 Invasion 24% — Hadad 31 Ly, 3 ports, 122k Ls 1.3g planet attack, 1154 Ls outpost + 122k Ls outpost damage
80 Tauri Control 22% — Indra 26 Ly
Hyades Sector DQ-O b6-4 Alert 22% — Taranis 29 Ly, empty
Imeut Alert 16% — Taranis 19 Ly, 12 Ls outpost, 54k Ls planet
Nihal Control 16% — Taranis 21 Ly
Aurus Invasion 14% — Raijin 26 Ly, 4 ports, 1121 Ls outpost attack
Yukait Invasion 14% — Hadad 26 Ly, 1 port, 74 Ls outpost attack, 108 Ls outpost damage
HIP 116360 Invasion 12% — Raijin 21 Ly, 4 ports, 861 Ls 0.3g planet attack
Arietis Sector VO-R b4-3 Control 10% — Leigong 29 Ly, empty
Aruntei Invasion 10% — Thor 46 Ly, 3 ports, 364 Ls outpost attack, 66 Ls 0.2g planet damage
Col 285 Sector AF-P c6-1 Alert 10% — Cocijo 25 Ly, empty
Col 285 Sector YY-F b12-3 Alert 10% — Cocijo 29 Ly, empty
HIP 20890 Invasion 10% — Indra 22 Ly, 3 ports, 6876 Ls 0.4g planet attack
HIP 26926 Invasion 10% — Taranis 28 Ly, 2 ports, 2055 Ls outpost attack, 475 Ls outpost damage
Pegasi Sector MY-O a7-2 Alert 10% — Raijin 25 Ly, empty
Arietis Sector HG-X b1-3 Alert 8% — Indra 22 Ly, empty
Arietis Sector KM-T a4-0 Alert 8% — Indra 25 Ly, empty
Arietis Sector VO-R b4-1 Alert 8% — Leigong 33 Ly, empty
Col 285 Sector TS-Z b14-4 Control 8% — Hadad 23 Ly, empty
Col 285 Sector ZE-P c6-20 Alert 8% — Cocijo 28 Ly, empty
HIP 8825 Control 8% — Oya 20 Ly
Auaker Invasion 6% — Thor 36 Ly, 2 ports, 386 Ls 0.4g planet attack
Col 285 Sector TS-Z b14-2 Control 6% — Hadad 21 Ly, empty
HIP 19781 Invasion 6% — Indra 26 Ly, 0 ports, 262 Ls outpost damage
Unktety Invasion 6% — Thor 25 Ly, 3 ports, 38 Ls 0.6g planet attack, 92 Ls outpost damage
Chibis Invasion 4% — Cocijo 25 Ly, 0 ports, 880 Ls outpost damage
HIP 19157 Invasion 4% — Indra 22 Ly, 2 ports, 1277 Ls outpost attack, 217 Ls 1.4g planet damage
HIP 21380 Alert 4% — Indra 27 Ly, 155k Ls planet
HIP 22566 Invasion 4% — Indra 24 Ly, 3 ports, 4922 Ls 0.12g planet attack, 4908 Ls 0.12g planet damage
HIP 37520 Alert 4% — Cocijo 30 Ly, 312k Ls outpost
Hyades Sector LI-K b8-2 Alert 4% — Leigong 27 Ly
Kalkaduna Alert 4% — Thor 39 Ly
Vaipacnali Control 4% — Thor 19 Ly
Arietis Sector EW-N b6-2 Alert 2% — Leigong 28 Ly
Bumbo Control 2% — Oya 22 Ly
Cephei Sector DQ-Y b2 Control 2% — Oya 22 Ly, empty
Ceti Sector DB-X b1-0 Control 2% — Leigong 49 Ly, empty
HIP 21654 Control 2% — Indra 26 Ly, empty
HIP 6442 Invasion 2% — Leigong 28 Ly, 0 ports, 816 Ls outpost damage
Haitchane Invasion 2% — Leigong 30 Ly, 0 ports, 558 Ls outpost damage
Matshiru Control 2% — Taranis 20 Ly
Tagin Invasion 2% — Raijin 23 Ly, 0 ports, 636 Ls outpost damage

Week 16, 16th March 3309​

Report
Alert repelled in HIP 2422, Wolf 121, Neites, Jaoi, Hyades Sector LN-K b8-3, Col 285 Sector WN-Z b14-6, HIP 20492, Bi Dhorora.
Col 285 Sector AF-E b13-5, HIP 29596, Cao Tzu, HIP 19757, Muncheim, Asletae, Minawara, Vukurbeh, Ebisu, Bormuninus, Cabarci, Isla, Yemaki, Gamil, Heng defended from Invasion.
Control evicted from Hyades Sector IM-L b8-5, Gliese 3050.
 
Last edited:
Has anyone considered using the tissue sampling method to try and clear HIP 8825? It is an inhabited Control system, but since it has no neighbours within 10Ly if we clear it it’ll stay cleared and provide a staging post for doing stuff in Maelstrom Oya.
 
A thought has come to mind. We are losing for now, no doubt. The thargoids now have over 1k control systems. That being said, do we have a set of systems we wish to keep defended as beachheads in each maelstrom sector? This way when we do figure this out, we don't have a slog from outside in but instead have ready jumping off points within their sphere's of influence.
 
A thought has come to mind. We are losing for now, no doubt. The thargoids now have over 1k control systems. That being said, do we have a set of systems we wish to keep defended as beachheads in each maelstrom sector? This way when we do figure this out, we don't have a slog from outside in but instead have ready jumping off points within their sphere's of influence.
HIP 23716 will be that for Taranis - nobody seems to want to lose the site of our first victory against the Thargoids. If we can recapture HIP 8825 it'll stay as a permanent cleared system near Oya, and Hyades Sector KN-K b8-4 and HIP 28240 can already be used for attacking Leigong and Hadad respectively if we don't mind using just carriers.
 
Ceti Sector ZU-Y b3 just updated and is at 58% - this is the system I want to clear to see what happens if you cut off control systems from the maelstrom.

Sounds good! I am not going to worry too much about trying to list those in-progress given how quickly such can be completed between full scans, though definitely anyone looking for a Thargoid fight can consider it an announcement that help is welcome in Ceti Sector ZU-Y b3.

If something incredibly advantageous occurs, I will be eyeing the procession of empty Control systems which started at M. Hadad and seems to be forming a Thargoid tunnel in the direction of the Coalsack. I forget its shape and may be imagining things without access to a Galaxy map at the moment, though if I recall, carving a plane through that could make a larger disjoint region.


Has anyone considered using the tissue sampling method to try and clear HIP 8825? It is an inhabited Control system, but since it has no neighbours within 10Ly if we clear it it’ll stay cleared and provide a staging post for doing stuff in Maelstrom Oya.

Mind that such should be considered a hypothesis prediction for the moment; otherwise, the direct answer is yes—some are aware indeed that new Alerts seem to need 10 Ly distance from a Control system, and that HIPs 8825 and 24329 are isolated under that hypothesis. I think it will be interesting either way; even if they enter Alert again, that would still contribute to our knowledge (for example, one possible explanation is that a Maelstrom can impose Alerts from further away).


A thought has come to mind. We are losing for now, no doubt. The thargoids now have over 1k control systems. That being said, do we have a set of systems we wish to keep defended as beachheads in each maelstrom sector? This way when we do figure this out, we don't have a slog from outside in but instead have ready jumping off points within their sphere's of influence.

If it helps to consider, only around a fifth of those are populated! I am also quite sure that if half of the present combat capacity were to try research, we would then be clearing out well over 100 systems per cycle, perhaps approaching 200. In any case, my suggestion for M. Hadad is the Muruidooges system; presently in Invasion for the fourth time, having been defended on the previous three.
 
Mind that such should be considered a hypothesis prediction for the moment; otherwise, the direct answer is yes—some are aware indeed that new Alerts seem to need 10 Ly distance from a Control system, and that HIPs 8825 and 24329 are isolated under that hypothesis. I think it will be interesting either way; even if they enter Alert again, that would still contribute to our knowledge (for example, one possible explanation is that a Maelstrom can impose Alerts from further away).
It's fairly unlikely that the Maelstrom has that much extra range. Hyades Sector KN-K b8-4 is closer to Leigong than HIP 8825 is to Oya, and it's never been Alerted. That said, I agree with your wider premise that we can't be sure if the Thargoids have tricks up their sleeves (if they have sleeves!) to reach isolated inhabited systems. Only one way to find out!
 
Whilst I'm on the subject of liberating systems, I have a couple of questions whilst I'm planning out my tissue-sampler runs.
1. Can you attach multiple research limpets to an Interceptor at once? If so, what's the maximum limit?
2. Can you store samples on a carrier without losing their effect?
3. Can you carry collected samples over a Thargsday cycle without them losing effect?
 
Whilst I'm on the subject of liberating systems, I have a couple of questions whilst I'm planning out my tissue-sampler runs.
1. Can you attach multiple research limpets to an Interceptor at once? If so, what's the maximum limit?
2. Can you store samples on a carrier without losing their effect?
3. Can you carry collected samples over a Thargsday cycle without them losing effect?

1. Yes; it appears to have no direct limit, only those limpet controllers you can carry. The class 7 Universal multi-limpet provides eight (eventually...), or you could use a smaller Xeno multi-limpet if you do not mind having only four from it, though either way you can also use additional class 1 Research limpet controllers. I have ten Research limpets total, though occasionally I reserve one Universal limpet to be a Collector or a Repair (mostly to keep the canopy healthy).

2. Yes; every single sample I have delivered, completing several systems that way, has been into my Carrier hold first before being loaded onto a purpose-built corrosive cargo ferry Anaconda.

3. Yes; from Controlled System Reclamation Project:
I tested alert systems gathered the week before a system went to invasion, and they worked for the invasion state, so I suspect the only thing tracked is system of origin. That said, I don't know where you would keep these stashes. Someone would have to dedicate their fleet carrier to one system per interceptor type. And I don't think it's safe to assume there won't be a nerf coming for this method, which would leave a lot of that work useless after-the-fact.
 
1. Yes; it appears to have no direct limit, only those limpet controllers you can carry. The class 7 Universal multi-limpet provides eight (eventually...), or you could use a smaller Xeno multi-limpet if you do not mind having only four from it, though either way you can also use additional class 1 Research limpet controllers. I have ten Research limpets total, though occasionally I reserve one Universal limpet to be a Collector or a Repair (mostly to keep the canopy healthy).

2. Yes; every single sample I have delivered, completing several systems that way, has been into my Carrier hold first before being loaded onto a purpose-built corrosive cargo ferry Anaconda.

3. Yes; from Controlled System Reclamation Project:
So it is a slight risk, but I could save up samples to make an attempt at HIP 8825 next week. Might be worth doing, and we'll probably be told about a nerf before the cycle finishes so I could deliver them if neccessary.
 
I am also quite sure that if half of the present combat capacity were to try research, we would then be clearing out well over 100 systems per cycle, perhaps approaching 200.
So we would be doing 4x-8x the progress, with half the effort.

I don't wanna use the E. word... but...
 
Last edited:
If something incredibly advantageous occurs, I will be eyeing the procession of empty Control systems which started at M. Hadad and seems to be forming a Thargoid tunnel in the direction of the Coalsack. I forget its shape and may be imagining things without access to a Galaxy map at the moment, though if I recall, carving a plane through that could make a larger disjoint region.

Wait, no!
I need those for doing the Hutton Hyperspace Hop!
 
Good solid start; the quest to create a disjoint region in Ceti Sector is going very well, Invasion defence seems underway, and the movement at three Alerts by M. Hadad has decided what I will be doing for now. Col 285 Sector VN-Z b14-6 is particularly fortuitous, because that was where my Fleet Carrier was parked from last cycle, so I will be helping that one alongside Putas and Vogulu.

Top targets at 19:00 23rd March 3309:
Ceti Sector ZU-Y b3 Control 80% — Leigong 36 Ly, empty
Hez Ur Invasion 46% — Cocijo 22 Ly, 1 port, 446 Ls starport attack, 236 Ls outpost damage
HR 1403 Invasion 18% — Indra 25 Ly, 3 ports, 62k Ls outpost attack, 194 Ls 2.5g planet + 2483 Ls 0.13g planet damage
Elboongzi Invasion 16% — Oya 27 Ly, 3 ports, 1158 Ls outpost attack
Muruidooges Invasion 8% — Hadad 18 Ly, 2 ports, 7320 Ls 0.4g planet damage, pending attack report
Putas Alert 8% — Hadad 23 Ly, 572 Ls starport, 861 Ls outpost
Col 285 Sector TS-Z b14-2 Control 6% — Hadad 21 Ly, empty
Vogulu Alert 6% — Hadad 21 Ly, 336 Ls starport, 35k Ls outpost
HIP 20485 Alert 4% — Indra 21 Ly, 27 Ls starport, 35 Ls planet
Hyades Sector AV-O b6-5 Invasion 4% — Taranis 24 Ly, 2 ports, 22 Ls 0.16g planet attack


So we would be doing 4x-8x the progress, with half the effort.
I don't wanna use the E. word... but...

I can only apologise for not understanding your reference; otherwise, I think so! For example, as it is now, one system per Commander each cycle is perfectly viable with a relatively basic time investment needed to secure an unpopulated system oneself. Having more time to offer translates to taking a populated system, or taking multiple systems. Multiply that by even a conservative estimate of combat Commanders participating actively and I think the evictions will outpace the new Alerts at least once over.


Wait, no!
I need those for doing the Hutton Hyperspace Hop!

We are not jeopardising Human space, much less Imperial space, just so that you can continue misbehaving!
 
I can only apologise for not understanding your reference; otherwise, I think so! For example, as it is now, one system per Commander each cycle is perfectly viable with a relatively basic time investment needed to secure an unpopulated system oneself. Having more time to offer translates to taking a populated system, or taking multiple systems. Multiply that by even a conservative estimate of combat Commanders participating actively and I think the evictions will outpace the new Alerts at least once over.
He's calling the tissue sampling method an exploit.
 
Seems possible, I doubt they realized the multi-limpet controllers could be used to collect so many samples simultaneously (previously the only possibility was using multiple size 1 research controllers).
 
Back
Top Bottom