Thargoid invasion - Next target systems?

Shouldn't AV-Y b4 be under Clean-up? It's not inhabited.
Oops, yes—thank you! Our thingy is supposed to be marking empty systems automatically, but it seems to be just setting the present ports to zero, which makes it more like an Invasion in its final week as opposed to a system with zero total ports.
Fixed that now, cheers @Starsong!

I wish there were some way of knowing where there were more CMDRs at a certain planet base under attack. It's sort of annoying to travel to a planet base and there not really being enough players there.
Conceptually at least, there may be! One would need a live view of it, but I am quite sure that the same reports used to detect attacks could also be counted over a short time, or displayed over the last few minutes. If nothing like that exists at the moment, I will discover whether that is something the Imperial Navy mathematics department can piece together!
Wanted to follow this up, I made a quick prototype to demonstrate the basic idea - try this? @Genar-Hofoen
That isn't using all possible EDDN messages yet and could/should show a bit more info, but see if it helps to find other pilots.
Also it doesn't know the game modes so those could be private group or solo, but it could still lead you to other pilots there in open who weren't feeding EDDN.

SNPX did some Scout harvesting. 331 scout samples gave us round 10% progress... So let's go, it is doable til tomorrow evening.
I thought Scout samples would have a lower worth. But in control systems it may be the same than samples from interceptors...
That matches our Cyclops samples, if 1303 was +38.9426% then 331 would be about +9.89%.
This gives me an EPIC idea for improving open harvests - if you're finishing MCC 105, I'll grab Aleksandra later to help test it around Hadad (will need 2 pilots).
At the moment the open process is clever but pretty crazy to execute and needs min 3 pilots, all just to bypass the swarms.
I think I can turn one of its side effects into a way for 2 pilots to bootstrap an instance with only scouts!
 
Wanted to follow this up, I made a quick prototype to demonstrate the basic idea - try this? @Genar-Hofoen
That isn't using all possible EDDN messages yet and could/should show a bit more info, but see if it helps to find other pilots.
Also it doesn't know the game modes so those could be private group or solo, but it could still lead you to other pilots there in open who weren't feeding EDDN.

Nice work! I was faintly thinking about doing something like this myself but I lack the energy & motivation for even doing stuff to Captain's Log at the moment, let alone doing something on a web site :)

Yes something like this. Of course FDEV has all the information needed, to produce something like this in-game, rather than leaving it up to 3rd party devs. Imagine if they included information like this for the Thargoid war status in the Galaxy and System maps!
 
Do we have any numbers on how much Orthrus kills help to move the chevron? If no Orthrus turns up is it better to scoop and sell the Sensor or destroy it?

Around Oya we found out that one Orthrus gives aprox 1% in inhabited und 4% in uninhabited systems.
I played around a bit with Thor's alerts. This would be solo, so without any wing multiplier. I'm not 100% sure on the inconsistencies, there may be a benefit to "completing a scenario" which includes just jumping in to a NHSS with a probe and nothing happening. These are all uninhabited.
1684936273469.png
 
Arietis Sector JR-V b2-2 unpopulated alert, has two high intensity ax conflict zones. For anyone tracking odd behavior.
I can confirm this. Does anyone know if it's been Thargoid Control at any point in the past? (And does anyone have the time to finish it off, it's pretty close to clearing and would be a shame to lose)
 
Victories in Namayu, HIP 20491, MCC 105 (thank you @Shayan al Nasarwa!) and HR 1812 (thank you @Darkman Returns)!

Invasions at 18:00 24th May 3309:
HIP 116360 Invasion 82% *85.6%Raijin 21 Ly, 3 ports, 861 Ls 0.3g planet attack, 462 Ls 0.2g planet damage
Very slightly behind:

Yan Zangata Invasion 54% *55%Hadad 22 Ly, 2 ports, 98 Ls outpost attack
Surplus:

Jawul Invasion 40% *40.6%Raijin 27 Ly, 5 ports, 3028 Ls outpost + 3040 Ls outpost attack
HIP 19757 Invasion 38% *39.9%Indra 25 Ly, 4 ports, 1098 Ls 0.4g planet attack
HIP 19157 Invasion 32% *33.2%Indra 22 Ly, 3 ports, 217 Ls 1.4g planet attack, 1277 Ls outpost damage

Alerts, Wednesday caution:
Senocidi Alert 88% *88.7%Taranis 20 Ly, 184 Ls starport, 3144 Ls outpost, 467k Ls planet
Unlikely:

69 Upsilon Tauri Alert 54% *55.2%Indra 26 Ly, 3628 Ls starport, 3697 Ls outpost, 1474 Ls planet
Bi Dhorora Alert 44% *44.1%Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet

Clean-up:
Arietis Sector JR-V b2-2 Alert 88% — Indra 26 Ly, empty
Col 285 Sector TS-Z b14-2 Alert 48% *49.8%Hadad 21 Ly, empty


I can confirm this. Does anyone know if it's been Thargoid Control at any point in the past? (And does anyone have the time to finish it off, it's pretty close to clearing and would be a shame to lose)

Indeed; it was a completed Control eviction in Week 18! These seem to be leaving Conflict Zones everywhere, including in now-empty systems, many of which I see when moving the Fleet Carrier around into systems we have cleared previously. With a new Alert in Arietis Sector JR-V b2-2, definitely it is fortuitous that it retained a Conflict Zone!


I was also stacking cyclops and scout killing missions from an Alert system (Muncheim) and fulfilling them in MCC 105. This shouldn't have made any difference to progress in MCC 105 but I mention it here in case there is a connection.

Actually, it does! The Mission completions will have counted for Muncheim, but those kills will have counted for MCC 105.
 
Do those conflict zones actually work? Since the changes with update 15 mean that conflict zones in invasions cease to function when the system progress completes...
the one I dropped into had ax conflict. got it to interceptors showing up, Edit:
**but it's at the driven thargoids back stage now. so Haven't checked after it's "done" stage.

Arietis Sector JR-V b2-2 Done.
 
Last edited:
Indeed, victories in Col 285 Sectors KW-M c7-25, RN-T d3-84, XN-Z b14-5, and XN-Z b14-6, Senocidi, HIP 116360 and Arietis Sector JR-V b2-2! Very well done to everyone at Senocidi for moving it through to completion where many often withdraw, and to @Spacerschoice-00 for the extra clean-up of course. That makes fifty-nine systems, which means Week 25 replaces Week 18 for being the highest ever, and becomes the first to reduce the total number of war-involved systems!

A lot of clean-up contributed to that of course, but this is really an adjustment to match the same proportion of attacked systems, and it is well to help remove that means of accessing inhabited systems. It works well—to name few examples around M. Hadad, note that we have stopped seeing those once-regular attacks at Neites, Putas, Ahol, H Puppis and Ramandji!


**but it's at the driven thargoids back stage now. so Haven't checked after it's "done" stage.

If it helps with measurements beyond 100%, since update 15 you can now jump back to that system and check your journal file to see the excess, or have it reported automatically by running a utility such as EDMC! This has become incredibly useful for discovering exact difficulty, both due to the reported excess and due to the extra precision it gives.

Speaking of excess completion, the Hyades Sector AV-O b6-5 Overachievement Award goes to Gliese 3050, an unpopulated Alert system which ended with a reported 236%!
 

Week 26, 25th May 3309​

Report
Nineteen Alerts repelled at Arietis Sectors UO-R b4-4, YU-P b5-0, EW-N b6-2 and CQ-P b5-3, Cephei Sector ZZ-Y b3, HIPs 6913 and 20485, Minawara, Gliese 9035, Lahua, Khwal, Pegasi Sectors WK-L a9-1 and LY-O a7-0, HR 1403, Garongxians, Vukurbeh, Vogulu, Col 285 Sector UD-G b12-2, Trianguli Sector BA-A d84.
Eleven Invasions defended at Jawul, HIPs 19757, 21380 and 19157, Aurus, Col 285 Sectors AF-E b13-5 and YT-F b12-3, 69 Upsilon Tauri, Arietis Sector DQ-Y c18, Yan Zangata, Bi Dhorora.
Thirty-five Control evictions at Col 285 Sectors PM-B b14-5, RX-Z b14-0, OB-D b13-2, TS-Z b14-2, HL-O c6-15, PW-D b12-0, ML-E b12-0, YY-X b15-4, QW-D b12-1, QW-D b12-2, YY-X b15-2, QW-D b12-3, OR-B b14-5, KW-M c7-19, GQ-O c6-2, TX-Z b14-0, PB-D b13-5, RN-T d3-61, PR-B b14-1, KW-M c7-27, IB-N c7-2, KW-M c7-10, KW-M c7-20, TH-B b14-3, VS-Z b14-4, XN-Z b14-1, HD-G b12-1 and AF-E b13-0, L2 Puppis, HIP 4617, Nihal, Pegasi Sector GW-V b2-3, Canaharvas, Liu Hef, Cephei Sector YJ-A c8.
In addition to the defended Invasions, four recaptured systems starting Recovery are HIP 4617, Nihal, Canaharvas, Liu Hef.

Targets updated at 06:50 1st June 3309
HIP 23716 Alert 74% *75.7%Taranis 18 Ly, 2314 Ls starport, 2351 Ls outpost, 3051 Ls planet
HIP 20850 Alert 70% *71.1%Indra 27 Ly, 94 Ls planet
57 h Tauri Alert 46% *47%Indra 27 Ly, empty
Lubal Control 24% *24.8%Taranis 26 Ly
Col 285 Sector JW-M c7-11 Alert 24% *24.2%Hadad 23 Ly, empty
Koko Oh Alert 20% *20.9%Raijin 27 Ly, 489 Ls outpost, 489 Ls planet
Trianguli Sector GG-Y c18 Control 18% *19%Taranis 26 Ly
HIP 20056 Control 16% *16.8%Indra 24 Ly
Iduni Control 14% *14.7%Raijin 22 Ly
Pegasi Sector KC-U b3-0 Alert 14% *14.1%Raijin 27 Ly, empty
Wogaiawong Control 12% — Cocijo 32 Ly
Ge Alert 10% *11.1%Taranis 28 Ly, 109 Ls starport, 34 Ls outpost, 45 Ls planet
Kamato Control 6% *7.7%Raijin 27 Ly
HIP 26274 Alert 6% *6.7%Taranis 24 Ly, 4936 Ls planet
Almar Control 6% — Thor 32 Ly
Hyades Sector EX-H a11-1 Alert 6% — Indra 27 Ly, empty
Pegasi Sector KH-V c2-13 Control 4% *4.6%Raijin 25 Ly, empty
Chibis Control 4% *4.5%Cocijo 25 Ly
HIP 25679 Control 4% *4.4%Taranis 17 Ly
Col 285 Sector OC-L c8-11 Alert 4% *4.2%Hadad 29 Ly, empty
Mapon Control 4% *4.2%Cocijo 18 Ly
HIP 19781 Control 4% *4.1%Indra 26 Ly
Trianguli Sector JR-W b1-0 Control 4% — Taranis 29 Ly, empty
HIP 30158 Control 2% *3.8%Hadad 21 Ly
HIP 21946 Control 2% *3%Indra 24 Ly
Njana Control 2% *2.8%Cocijo 26 Ly
HIP 21261 Control 2% *2.4%Indra 20 Ly
HIP 22496 Control 2% *2.3%Indra 22 Ly
Obamumbo Control 2% *2.1%Indra 19 Ly
Col 285 Sector YT-F b12-1 Control 2% — Cocijo 24 Ly, empty
Arietis Sector TY-P a6-2 Control 2% — Indra 26 Ly, empty
Col 285 Sector OM-J b10-1 Alert 2% — Cocijo 31 Ly, empty
Col 285 Sector TS-H b11-4 Control 2% — Cocijo 21 Ly, empty

Notes
The Alert report lists predicted attackers which can be stopped this cycle.

Week 25, 18th May 3309​

Report
Twenty-one Alerts repelled at Gliese 3050, Cephei Sector EL-Y c23, HIPs 2422 and 20527, Arietis Sectors DW-N b6-4, DW-N b6-3, WO-R b4-4, YJ-R b4-3 and JR-V b2-2, Muncheim, Pegasi Sectors QE-N a8-3 and QZ-M a8-0, Awara, Jaoi, Pathamon, 63 Eridani, Col 285 Sector TS-Z b14-3, Ngolite, Namayu, HR 1812, Senocidi.
Sixteen Invasions defended at Paeni, HIPs 29596, 20899, 20890, 21724, 117177, 20491 and 116360, Ebisu, Lovaroju, Kagutsuchi, Imeut, Nu Guang, Bormuninus, Muruidooges, Unktety.
Twenty-two Control evictions at Col 285 Sectors BA-P c6-3, YT-F b12-5, AP-F b12-2, BU-X b15-1, KW-M c7-25, LB-O c6-3, RN-T d3-84, TH-B b14-6, UC-B b14-4, WC-C b13-2, XN-Z b14-5, XN-Z b14-6, YT-F b12-7, ZY-X b15-8 and SX-Z b14-2, HIPs 10921 and 16954, Ceti Sector DB-X b1-0, Arietis Sector NX-U c2-12, Cephei Sectors AV-Y b5 and AV-Y b4, MCC 105.
In addition to the defended Invasions, two recaptured systems starting Recovery are HIP 16954, MCC 105.
 
Last edited:
Actually, it does! The Mission completions will have counted for Muncheim, but those kills will have counted for MCC 105.
Yep. I understand the kills count in the system that they died but was notiing that they were part of a mission. Theoretically the mission completion shouldn't impact the control system, and probably doesn't, but there seemed to be decent progress from kills which was not expected. Other than there being a different weighting in the "targetted for counterattack" systems the only other differences that I can see are the presence of the restoring settlement missions and the (unlikely) possibility that the kill mission completion might have some unexplained influence.
 
Yep. I understand the kills count in the system that they died but was notiing that they were part of a mission. Theoretically the mission completion shouldn't impact the control system, and probably doesn't, but there seemed to be decent progress from kills which was not expected. Other than there being a different weighting in the "targetted for counterattack" systems the only other differences that I can see are the presence of the restoring settlement missions and the (unlikely) possibility that the kill mission completion might have some unexplained influence.
We know that the restoration missions have a significant effect, but MCC 105 progressed much more than the other systems recieving them - might be worth using the new journal? trick to get precise numbers for combat actions on a system that doesn't have restoration activity.
 
Victories in Arietis Sector UO-R b4-4 and Jawul!

Targets at 07:10 26th May 3309:
HIP 19757 Invasion 90% *92.4%Indra 25 Ly, 3 ports, 2256 Ls 0.2g planet attack, 1098 Ls 0.4g planet damage
Yan Zangata Invasion 52% *52.4%Hadad 22 Ly, 1 port, 70 Ls outpost attack, 98 Ls outpost damage
Col 285 Sector AF-E b13-5 Invasion 42% — Cocijo 26 Ly, 2 ports, 283 Ls 0.14g planet attack
69 Upsilon Tauri Invasion 36% — Indra 26 Ly, 7 ports, 3703 Ls 0.4g planet + 3780 Ls outpost attack
Aurus Invasion 22% *22.1%Raijin 26 Ly, 4 ports, 130 Ls 0.6g planet attack
Trianguli Sector GG-Y c18 Control 16% *16.9%Taranis 26 Ly
Nihal Control 16% — Taranis 21 Ly

Alerts:
Minawara Alert 26% *26.1%Oya 23 Ly, 412 Ls outpost
HR 1403 Alert 18% *18.5%Indra 25 Ly, 194 Ls starport
Lahua Alert 16% *16.7%Oya 19 Ly, 7 Ls outpost, 19 Ls planet

Clean-up:
Arietis Sector YU-P b5-0 Alert 46% — Leigong 25 Ly, empty
Cephei Sector ZZ-Y b3 Alert 40% *41%Oya 15 Ly, empty
 
We know that the restoration missions have a significant effect, but MCC 105 progressed much more than the other systems recieving them - might be worth using the new journal? trick to get precise numbers for combat actions on a system that doesn't have restoration activity.
Can you link to how the new journal is found/used?
Would be happy to check out another counterattack system to see what the effect is.
 
Back
Top Bottom