Thargoid invasion - Next target systems?
- Thread starter Aleks Zuno
- Start date
I am picking up Indra BioCapsules today and offloading them tomorrow at cycle reset
Last edited:
I was just thinking the same—even if nothing else, your Carrier holds a quite valuable system strength test! After delivering it, the systems 37 A1 Tauri, 77 Theta-1 Tauri, 92 Sigma-2 Tauri, Arietis Sector JR-V b2-3 and Hyades Sector LC-U b3-4 should be checked for their precise progress, ideally with one extra check at (for example) Hyades Sector QI-S b4-2 to account for any peripheral progress.
In the completion context, that will get two peripheral Control systems started, and I am quite confident that the progress at those three closer systems can be put to use! We should be mindful of a sunk cost fallacy, but otherwise I think it a good idea to schedule Friday evening here for completing one of those (most likely 77 Theta-1 Tauri), then respond to week 79 as it transpires with a background goal of completing the others if we can.
I doubt that anybody can give a well-informed answer to that, although with combat specifically I think we can presume it requires Conflict zone completions, making the answer conditional upon those being present.
A quite satisfying conclusion could occur if it receives a strong drive to complete wounded Escape pod missions, given that mission completions should be also much stronger now!
They are still there. Just, not around the outpost itself - it would just lend itself to killing Scythes in large numbers.
Week 79, 30th May 3310
Maelstrom IndraAlert:
Invasion:
Spire: After those Alerts above, peripheral progress will be maximised. HR 1358 is next by distance, although HIP 19870 now has partial progress.
Since this week began, Hyades Sector DX-H a11-1 has been reinstated as a Spire site again.
Control: Conflict zone completions are good for finishing peripheral systems.
These should become
Report
Twenty-one Alerts repelled at HIPs 20492, 21918, 20056, 21380, 21946, 20491, 18857, 117762 and 18513, 69 Upsilon Tauri, 78 Theta-2 Tauri, Hyades Sector FB-X c1-17, Nu Guang, Tvasu, Ngolite, Jawul, Wanmi, Col 285 Sectors YT-F b12-3 and AU-F b12-1, and Pegasi Sectors EB-W b2-3 and VK-L a9-3.
Nine Invasions defended at Nibelaako, HIPs 20616 and 37520, Asletae, Wogaiawong, Bormuninus, Laumas, Unktety and Kissi.
Twelve Control evictions at 77 Theta-1 Tauri, Arietis Sectors JR-V b2-3, DQ-Y c9, KM-T a4-2 and HG-X b1-4, 92 Sigma-2 Tauri, 37 A1 Tauri, HIPs 20741, 21788 and 20482, and Hyades Sectors LC-U b3-4 and QI-S b4-2.
One Matrix system cleared at HIP 19870.
In addition to the defended Invasions, one recaptured system starting Recovery is HIP 20741.
Targets updated at 06:30 6th June 3310
70 Tauri Control 66% — Indra 21 Ly, 3859 strength
HIP 19789 Control 44% — Indra 24 Ly, 3722 strength
Hyades Sector ST-Q b5-2 Control 42% — Indra 24 Ly, 3853 strength
Ixbaksha Control 36% *37% — Raijin 23 Ly, 7012 strength
Synuefe OU-D b45-0 Alert 36% *36.8% — Thor 30 Ly
Hyades Sector AR-J a10-0 Control 36% — Indra 24 Ly, 4264 strength
Hyades Sector ST-Q b5-3 Control 30% — Indra 24 Ly, 4667 strength
Hyades Sector DX-H a11-1 Control 28% *28.2% — Indra 24 Ly, 4762 strength
HIP 20146 Control 26% *26.6% — Indra 23 Ly, 4892 strength
Col 285 Sector BA-P c6-3 Alert 24% — Cocijo 30 Ly
Col 285 Sector AF-E b13-5 Control 22% — Cocijo 26 Ly, 8460 strength
Arietis Sector FL-X b1-0 Control 22% — Indra 23 Ly, 5205 strength
HIP 20899 Control 20% — Indra 23 Ly, 8924 strength
Col 285 Sector KL-E b12-5 Control 14% — Thor 31 Ly, 5382 strength
Pegasi Sector PI-S b4-1 Alert 12% *13% — Raijin 28 Ly
Pegasi Sector MY-O a7-3 Control 12% — Raijin 27 Ly, 5716 strength
Almar Control 12% — Thor 32 Ly, 9119 strength
Col 285 Sector DA-E b13-1 Alert 12% — Cocijo 30 Ly
55 Tauri Control 12% — Indra 23 Ly, 5893 strength
Scythia Control 10% *10.1% — Indra 20 Ly, 10.3k strength
HIP 20890 Control 10% — Indra 22 Ly, 10.1k strength
Arietis Sector TY-P a6-0 Control 10% — Indra 23 Ly, 6034 strength
Arietis Sector NH-V b2-0 Control 8% — Indra 22 Ly, 6187 strength
HIP 112595 Control 8% — Raijin 24 Ly, 6132 strength
HIP 17897 Alert 6% *7.8% — Thor 28 Ly
Arietis Sector LM-V b2-5 Control 6% *7.6% — Indra 22 Ly, 6228 strength
HIP 22524 Control 6% *6.8% — Indra 20 Ly, 10.6k strength
HIP 21261 Control 6% — Indra 20 Ly, 10.7k strength
HIP 20815 Control 6% — Indra 22 Ly, 6361 strength
Col 285 Sector YY-F b12-6 Alert 6% — Cocijo 30 Ly
58 Tauri Control 4% *5.8% — Indra 22 Ly, 6339 strength
Arietis Sector LM-V b2-3 Control 4% *5.8% — Indra 20 Ly, 6455 strength
Hyades Sector TO-Q b5-2 Control 4% *5.2% — Indra 23 Ly, 6371 strength
Arietis Sector HG-X b1-0 Control 4% *5.1% — Indra 21 Ly, 6437 strength
Tagin Control 4% *4.9% — Raijin 23 Ly, 10.6k strength
Arietis Sector JR-V b2-4 Control 4% *4.8% — Indra 20 Ly, 6539 strength
Varlawoth Control 4% *4.7% — Thor 29 Ly, 10.1k strength
Hyades Sector ST-Q b5-5 Control 4% *4.5% — Indra 22 Ly, 6462 strength
Arietis Sector JR-V b2-1 Control 4% *4.3% — Indra 22 Ly, 6450 strength
HIP 20187 Matrix 4% *4.1% — Indra 15 Ly
79 b Tauri Control 4% — Indra 19 Ly, 6616 strength
HIP 22688 Control 4% — Indra 22 Ly, 6461 strength
Col 285 Sector ZE-P c6-11 Control 4% — Cocijo 29 Ly, 10.2k strength
Hyades Sector ON-S b4-6 Control 4% — Indra 23 Ly, 6449 strength
Col 285 Sector AP-F b12-2 Alert 4% — Cocijo 30 Ly
Col 285 Sector ZE-P c6-18 Alert 4% — Cocijo 30 Ly
97 i Tauri Control 2% *3.3% — Indra 21 Ly, 11k strength
HIP 22496 Control 2% *3.1% — Indra 22 Ly, 10.9k strength
Arietis Sector KR-V b2-1 Matrix 2% *2.9% — Indra 10 Ly
HIP 20480 Control 2% *2.9% — Indra 16 Ly, 11.4k strength
HIP 19198 Control 2% *2.7% — Thor 17 Ly, 11.4k strength
Pegasi Sector VK-L a9-4 Control 2% *2.6% — Raijin 29 Ly, 6226 strength
Col 285 Sector LB-O c6-1 Control 2% — Thor 32 Ly, 6090 strength
Col 285 Sector US-H b11-1 Alert 2% — Cocijo 30 Ly
Balak Control 2% — Raijin 23 Ly, 10.9k strength
Col 285 Sector SH-C b13-1 Alert 2% — Thor 35 Ly
Col 285 Sector AP-F b12-4 Control 2% — Cocijo 32 Ly, 6071 strength
Col 285 Sector OS-T d3-82 Control 2% — Cocijo 32 Ly, 10.1k strength
Col 285 Sector TC-J b10-0 Control 2% — Cocijo 32 Ly, 10.1k strength
Col 285 Sector US-H b11-5 Control 2% — Cocijo 33 Ly, 10.1k strength
HIP 39186 Control 2% — Cocijo 34 Ly, 5994 strength
HIP 39468 Control 2% — Cocijo 30 Ly, 6169 strength
Pegasi Sector BQ-Y d46 Control 2% — Raijin 28 Ly, 6277 strength
Pegasi Sector FB-X c1-24 Control 2% — Raijin 28 Ly, 6270 strength
Pegasi Sector GW-W d1-92 Control 2% — Raijin 29 Ly, 6265 strength
Pegasi Sector HH-U b3-7 Control 2% — Raijin 29 Ly, 6254 strength
Pegasi Sector JH-V c2-26 Control 2% — Raijin 28 Ly, 6273 strength
Pegasi Sector KH-V c2-6 Control 2% — Raijin 29 Ly, 6265 strength
Pegasi Sector LN-S b4-0 Control 2% — Raijin 29 Ly, 6264 strength
Pegasi Sector LY-O a7-1 Control 2% — Raijin 28 Ly, 6279 strength
Notes
Another rules revision will begin next week.
The Alert report lists predicted attackers.
Week 78, 23rd May 3310
ReportTwelve Alerts repelled at Col 285 Sectors EA-Q c5-15, JG-O c6-13 and RW-D b12-0, HIPs 20019, 19781 and 20948, Arietis Sectors NS-R a5-1 and KM-T a4-1, Hyades Sectors ST-Q b5-4 and IH-U b3-3, Obamumbo and Isla.
Ten Invasions defended at Koko Oh, Vistnero, Theemim, Col 285 Sector OS-T d3-146, HIPs 22566, 20509, 117177 and 19757, 65 Kappa Tauri and Kagutsuchi.
Fifteen Control evictions at Col 285 Sectors HP-H b10-3 and HF-G b11-2, Arietis Sectors OS-R a5-0, TY-P a6-1, TY-P a6-2, LM-V b2-2, DA-Z b3 and KM-T a4-0, Hyades Sectors PI-S b4-1, JH-U b3-4 and BR-J a10-0, and HIPs 22203, 22422, 21008 and 21099.
The defended Invasion systems will start Recovery.
Titan Hadad has overheated and exploded.
Last edited:
And the answer to what happens at the Spire site we left at Hadad?
It's dead, just like the ones at Taranis.
It's dead, just like the ones at Taranis.
So Indra is next objective ?
Thank you for checking!
I imagine the next related observation is once again whether an expended Spire site can be reoccupied, after the 18.06 change which clearly has prevented Spire reinforcement. That would be an interesting application of using HIP 19870 first, or any similarly-inner Spire—given a large enough Maelstrom to complete and presuming they do reactivate, it seems sensible to start the respite time of an easily-reactivated system sooner rather than later.
Insofar as it has most other Commanders defending it who would be most grateful for your kind support, yes!
Any and all Alerts are good to complete, with 69 Upsilon Tauri, HIP 21380, Hyades Sector FB-X c1-17 and 78 Theta-2 Tauri being most important to complete quickly. Wing Orthrus-hunting is very powerful now even with just two Commanders, especially with Supercruise Overcharge, and very especially with Python 2s using Supercruise Overcharge.
Alongside those, any outer Control progress would be splendid, noting indeed that the Conflict zone completion reward seems to be very strong. The specific systems are Hyades Sector LC-U b3-4, Arietis Sector KM-T a4-2, Hyades Sector QI-S b4-2, 37 A1 Tauri, HIP 21788, HIP 20482, Arietis Sector DQ-Y c9, HIP 20741, Arietis Sector HG-X b1-4 and Hyades Sector DX-H a11-1.
Has its spire still not reactivated? (I’d just look for myself in the game, but can’t right now)
The site is very much dead, although even if it were active, I imagine the lack of Galaxy map recognition means the system would behave normally!
Noticing that 77 Theta-1 Tauri gained a small sliver shy of 36% (specific amount 0.359957), I checked that against the 2295 stored payload listed here and found the resulting strength to be a quite large amount lower than estimated earlier. Given that other systems there have not moved except for a point of peripheral progress, I presume this was an independent attack (thank you!)—in which case it becomes pertinent for @XenosAurion to deliver the Aquitaine cargo. We can visit it as the first thing later this evening, if help is needed with the amount!
If that 36% progress actually was a partial delivery which somehow avoided the payloads for any other systems, either it was supplemented with other actions or the strength line has already changed, the unlikelihood of which has me suspecting a separate attack.
If that 36% progress actually was a partial delivery which somehow avoided the payloads for any other systems, either it was supplemented with other actions or the strength line has already changed, the unlikelihood of which has me suspecting a separate attack.
Some testing;
HIP 21946 - Indra - Populated Alert - 24.11 Ly
50 Injured with 10 Injured Missions (Mission Board)
Before - 0.006891
After - 0.010682
Difference = 0.003791
50 Passengers with 10 Refugee Missions (Passenger Board)
Before - 0.010682
After - 0.017918
Difference = 0.007236
100 scout samples
Before - 0.017951 (difference between 0.017918 and 0.017951 is assumed to be scout kills while sampling)
After - 0.042071
Difference = 0.02412
From this we can calculate it would take 4146 samples to clear the system.
Another 50 Injured with 10 missions
Before - 0.042071
After - 0.045799
Difference = 0.003728
The small difference between 0.003728 and 0.003791 can be assumed to be minor variations in the number of passengers per mission.
This represents a reversal of priority for rescues. Formerly, Injured were worth more than Refugees but now it is the other way round. May still be different for Wounded and Critically Wounded, this is untested atm.
The data above makes it possible to express Injured, Refugees and Samples as fractions of each other.
1 Orthrus Kill
Before - 0.045799
After - 0.045971
Difference = 0.000172
2 More Orthrus kills
Before - 0.045971
After - 0.046316
Difference = 0.000345
0.000345/2 = 0.0001725 so this fits to 6dp when rounded up.
HIP 21946 - Indra - Populated Alert - 24.11 Ly
50 Injured with 10 Injured Missions (Mission Board)
Before - 0.006891
After - 0.010682
Difference = 0.003791
50 Passengers with 10 Refugee Missions (Passenger Board)
Before - 0.010682
After - 0.017918
Difference = 0.007236
100 scout samples
Before - 0.017951 (difference between 0.017918 and 0.017951 is assumed to be scout kills while sampling)
After - 0.042071
Difference = 0.02412
From this we can calculate it would take 4146 samples to clear the system.
Another 50 Injured with 10 missions
Before - 0.042071
After - 0.045799
Difference = 0.003728
The small difference between 0.003728 and 0.003791 can be assumed to be minor variations in the number of passengers per mission.
This represents a reversal of priority for rescues. Formerly, Injured were worth more than Refugees but now it is the other way round. May still be different for Wounded and Critically Wounded, this is untested atm.
The data above makes it possible to express Injured, Refugees and Samples as fractions of each other.
1 Orthrus Kill
Before - 0.045799
After - 0.045971
Difference = 0.000172
2 More Orthrus kills
Before - 0.045971
After - 0.046316
Difference = 0.000345
0.000345/2 = 0.0001725 so this fits to 6dp when rounded up.
Interesting; after update 18.06 there were two main reasons to stop attacking a Spire system, and that change addresses the greater of them at least. Of course, remaining is the matter of expending Spire site progress against Alert systems, which I would still consider not fungible with progressing Control systems due to the Orthrus presence and the extreme power of hunting them, especially with all the new toys—Python 2, Supercruise overcharge, Shard cannons with Anti-guardian resistance. That view could change though; for example, if Commanders start favouring Conflict zones generally then it would be as well to use Spire progress on Alerts instead.
Admittedly the HIP 20492 completion was not quite what I had in mind to open the week, although definitely everyone has done a great job both there and now at 69 Upsilon Tauri! Despite not being in-session officially until this evening, V and I did some light Orthrus-hunting in 78 Theta-2 Tauri yesterday and seemed to move around 25% for one hour; definitely it is quite nice to see it cross 50% now, and the initial progress at HIP 21380 is a quite nice start. There is also Hyades Sector FB-X c1-17 to clear quickly if possible, although I know that system is placed inconveniently around the other side of the Maelstrom!
Admittedly the HIP 20492 completion was not quite what I had in mind to open the week, although definitely everyone has done a great job both there and now at 69 Upsilon Tauri! Despite not being in-session officially until this evening, V and I did some light Orthrus-hunting in 78 Theta-2 Tauri yesterday and seemed to move around 25% for one hour; definitely it is quite nice to see it cross 50% now, and the initial progress at HIP 21380 is a quite nice start. There is also Hyades Sector FB-X c1-17 to clear quickly if possible, although I know that system is placed inconveniently around the other side of the Maelstrom!
Also interesting testing! From that I gather that something seems potentially inconsistent with Orthrus kills; from here we had:
That was an empty system, so I understand that the Orthrus value expressed in Research units was therefore wrong at the time, but the surviving fact should be that one Orthrus was worth ~1%.
Noting that our empty Alert hunting was 24.6 Ly away and without having checked our exact Orthrus kills, definitely it would have corresponded to one kill for one Commander being around 1% there, or perhaps a bit lower. It would have been around 12 kills counted twice due to a wing with two Commanders, and the system did gain around 24%.
This test seems very much different:
That system is populated and 24.1 Ly such that some smaller progress change is expected, but not quite as small as one Orthrus being worth less than 0.2%! Definitely it is at least possible that a populated Alert is some five times stronger than an empty Alert; that is a stark difference with Control systems though, where the populated strength is just under double the empty strength.
That was an empty system, so I understand that the Orthrus value expressed in Research units was therefore wrong at the time, but the surviving fact should be that one Orthrus was worth ~1%.
Noting that our empty Alert hunting was 24.6 Ly away and without having checked our exact Orthrus kills, definitely it would have corresponded to one kill for one Commander being around 1% there, or perhaps a bit lower. It would have been around 12 kills counted twice due to a wing with two Commanders, and the system did gain around 24%.
This test seems very much different:
That system is populated and 24.1 Ly such that some smaller progress change is expected, but not quite as small as one Orthrus being worth less than 0.2%! Definitely it is at least possible that a populated Alert is some five times stronger than an empty Alert; that is a stark difference with Control systems though, where the populated strength is just under double the empty strength.
The good thing is that with the buff to rescues populated Alerts at least are much faster to clear with them. Op Ida have almost done 69 Upsilon Tauri and they only started this morning. Even us as a smaller group are 25% into HIP 21918, which we started just before them.
So it's only empty Alerts that still rely on rng to get Orthruses with.
I did go back and kill two more, and saw similar results each time. By any chance, did you wait for the next hour to tick around? Sometimes kills right at the end of the period get shoved to the next hour.
The Orthrus kills may not be correct in my case now because since then war progress jumped a little more with nothing else going on, so possibly they did not register fully at first. Will try to kill a few more later. The rescue stats are good though, no issues there.
Indeed the Orthrus kills in populated Alert systems will be difficult to separate from missions in the background, but that could be worth another look as convenience allows. I notice also that I missed a decimal place earlier, such that the reported effect on a populated Alert would be less than 0.02%, or over fifty times stronger system than at an empty Alert—a definite cause for suspicion!
In any case, it is well that missions are powerful enough that Orthrus-hunters can know to go directly for empty Alerts, as if being one of the few non-Research actions possible there was not already reason enough!
In any case, it is well that missions are powerful enough that Orthrus-hunters can know to go directly for empty Alerts, as if being one of the few non-Research actions possible there was not already reason enough!