Thargoid invasion - Next target systems?

[Aleks Zuno]

Victory in Jaoi! That makes seven, and everyone is doing quite well that the outlook is still 5–6 more.

Top targets at 09:25 21st February 3309:
HIP 26274 Invasion 88% — Taranis 24 Ly, 2 ports, 4935 Ls planet attack
Juipedun Alert 88% — Oya 24 Ly, 39 Ls starport, 114k Ls planet
HIP 20890 Invasion 62% — Indra 22 Ly, 2 ports, 2983 Ls planet attack, 6876 Ls planet damage
HIP 116360 Invasion 50% — Raijin 21 Ly, 3 ports, 462 Ls planet attack, 1211 Ls outpost damage
Vogulu Invasion 40% — Hadad 21 Ly, 5 ports, 471 Ls outpost + 35k Ls planet attack
Yan Zangata Invasion 34% — Hadad 22 Ly, 2 ports, 98 Ls outpost attack

At this point I feel really compelled to just buy a FC and haul stuff myself...

If you need it, I will fund that. I have some Alexandrite laying around which works for passing credits to others, albeit not as fast as with Meta-Alloys, and I could do so later today!

 

[Retyu Ranger]

You are missing it. Each system has the name of the closest maelstrom as the first piece of extra information, so you know which ones are grouped together.

Holy crudola. THanks. Braiin fart.

 

[Aleks Zuno]

Victories at Juipedun and HIP 26274!

Top targets at 17:30 21st February 3309:
HIP 20890 Invasion 72% — Indra 22 Ly, 2 ports, 2983 Ls planet attack, 6876 Ls planet damage
HIP 116360 Invasion 56% — Raijin 21 Ly, 3 ports, 462 Ls planet attack, 1211 Ls outpost damage
Vogulu Invasion 42% — Hadad 21 Ly, 5 ports, 471 Ls outpost + 35k Ls planet attack
Yan Zangata Invasion 36% — Hadad 22 Ly, 2 ports, 98 Ls outpost attack

Surplus:
Vistnero Invasion 28% — Raijin 21 Ly, 4 ports, 147 Ls planet attack

 

[BDelacroix]

Thanks for clearing out Juipedun. Didn't want to have to bug out. Tried to help along but rarely found any activity. My passenger ship was transformed into a storm rider to probe the maelstroms so I was left with the occasional fight and picking up escape pods and black boxes.

 

[ToxicCMDR]

Yesterday in HIP 20890 I had a perfect session with another four skilled CMDRs. They all new what to do and we served both Hydras nice and relaxing way.
I usually need a restock/repair after two first hearts but that time I restocked after a hydra was killed still having ~70% of hull in my AX Conda.

 

[Weps]

If you need it, I will fund that. I have some Alexandrite laying around which works for passing credits to others, albeit not as fast as with Meta-Alloys, and I could do so later today!

Thanks for the offer, but I have the funds. This war is making me rich. And now seeing as how Juipedun was won, maybe it's actually more efficient to source from a nearby system and skip the carrier leg.. I dunno.

Yesterday in HIP 20890 I had a perfect session with another four skilled CMDRs. They all new what to do and we served both Hydras nice and relaxing way.
I usually need a restock/repair after two first hearts but that time I restocked after a hydra was killed still having ~70% of hull in my AX Conda.

Same place, same experience today for me. Got an invite by some nice CMDRs, they took out both Hydras and even shared missions with me - even though in my gimballed MC Clipper I was doing nothing but have the Hydra spam more missiles

 

[Spaceman-FXL5]

Last day off today- work tomorrow, so I will concentrate on HIP 116360 (looks to be 85ish%?) - didn't like HIP 20890 as only planetary ports for repairs.
I prefer invasions with outposts and HIP 116360 is great for me as after some time combat in AXCZ, I either take a break, or go get Critically Wounded in damaged outposts, take to rescue ships, for a change of pace.

We may even get Vogulu done!

 

[Aleks Zuno]

Victory in HIP 20890! HIP 116360 should close easily some time this afternoon, Vogulu has a decent margin, and Yan Zangata is on the cusp. As with Bi Dhorora last cycle, it would be a nice treat if Yan Zangata avoids narrowly costing 133% rather than 100%, though taking a break and relaxing a bit is also quite fine. Fresh Alert activity spotted in Namayu!

Top targets at 09:35 22nd February 3309:
HIP 116360 Invasion 88% — Raijin 21 Ly, 3 ports, 462 Ls planet attack, 1211 Ls outpost damage
Vogulu Invasion 48% — Hadad 21 Ly, 5 ports, 471 Ls outpost + 35k Ls planet attack
Yan Zangata Invasion 40% — Hadad 22 Ly, 2 ports, 98 Ls outpost attack

Surplus:
Vistnero Invasion 32% — Raijin 21 Ly, 4 ports, 147 Ls planet attack

Yesterday in HIP 20890 I had a perfect session with another four skilled CMDRs. They all new what to do and we served both Hydras nice and relaxing way.
I usually need a restock/repair after two first hearts but that time I restocked after a hydra was killed still having ~70% of hull in my AX Conda.

I love seeing these updates, with those gradual improvements! I have yet to assemble a six-weapon vessel which can destroy a Cyclops directly, given that high speeds are not something I find myself able to trade away easily, although I enjoyed reaching the point of becoming able to remove a Cyclops without spending a heat sink or taking damage.

Last day off today- work tomorrow, so I will concentrate on HIP 116360 (looks to be 85ish%?) - didn't like HIP 20890 as only planetary ports for repairs.
I prefer invasions with outposts and HIP 116360 is great for me as after some time combat in AXCZ, I either take a break, or go get Critically Wounded in damaged outposts, take to rescue ships, for a change of pace.

We may even get Vogulu done!

I was thinking while reading that; surely Vogulu and Yan Zangata nearby would be better for you, with their actual Outpost attacks! Either way, it is refreshing to hear of an active preference for Outposts where most prefer Planetary for having no Swarms, and secondarily Starports for having large pads. That gives your fleet a quite valuable adaptable element!

You will be quite pleased to know that Vogulu looks quite fine at 12th with 1257%. Yan Zangata is the borderline case here; it came to 13th with 1301%!

 

[Uiros Ueramos]

I am so bad at using EDSY—it seems like the only place with all the appropriate numbers collected together, but is otherwise terribly confusing. When I looked for the shot speed, I saw the following and selected the gold ones:

View attachment 346165

Taking a second look at it, I can see that there are normal missiles with 750 speed and "ENH" with 1250 speed... but then, what are those gold missiles? From their numbers I presume they have High Capacity ("HC") and Rapid Fire ("RF"), making them far superior as far as damage is concerned.

As so many have already replied, those Golden ones are the Sirius Modified AX Missiles (from Normal AX). Better DMG than AX Missiles, but same shot speed.

Enhanced AX Missiles have same DMG as AX Missiles but higher shot speed.

 

[Aleks Zuno]

Victory in HIP 116360! Yan Zangata is looking more out of reach for this cycle, although Vogulu is still a good candidate for completion, both being physically nearby. Yan Zangata and Vistnero are past the 33% threshold for surplus activity to carry over; conversely, please note that 29 e Orionis should not be used for surplus despite approaching 33%, because it is entering the Control state.

Top targets at 18:40 22nd February 3309:
Vogulu Invasion 56% — Hadad 21 Ly, 5 ports, 471 Ls outpost + 35k Ls planet attack

Surplus:
Yan Zangata Invasion 42% — Hadad 22 Ly, 2 ports, 98 Ls outpost attack
Vistnero Invasion 34% — Raijin 21 Ly, 4 ports, 147 Ls planet attack

As so many have already replied, those Golden ones are the Sirius Modified AX Missiles (from Normal AX). Better DMG than AX Missiles, but same shot speed.
Enhanced AX Missiles have same DMG as AX Missiles but higher shot speed.

I got it, thank you! Those non-Guardian options seemed quite important in the upcoming sense, and that Sirius version is far superior.

 

[Aleks Zuno]

Week 13, 23rd February 3309​

Report
HIP 20485, HIP 20492, HIP 2422, Lahua, Lovaroju, Namayu, Neites, Pentam, Vogulu, Yan Zangata defended from Invasion.

Targets updated at 06:40 2nd March 3309
Luggerates Invasion 84% — Oya 22 Ly, 4 ports, 1473 Ls planet attack
HIP 20899 Invasion 68% — Indra 23 Ly, 3 ports, 2988 Ls planet attack
Khondo Po Invasion 48% — Oya 24 Ly, 2 ports, 37 Ls planet attack, 37 Ls outpost damage
Muchihiks Invasion 36% — Oya 20 Ly, 3 ports, 210k Ls planet attack, 1228 Ls planet + 2946 Ls planet damage
Kagutsuchi Alert 30% — Indra 22 Ly, 42 Ls starport, 55 Ls outpost
HIP 30158 Invasion 24% — Hadad 21 Ly, 2 ports, 543 Ls outpost + 6284 Ls planet attack, 6333 Ls planet + 6285 Ls planet damage
Holvandalla Invasion 24% — Raijin 21 Ly, 3 ports, 43 Ls planet + 1112 Ls planet attack, 19 Ls outpost + 43 Ls outpost damage
Obamumbo Invasion 18% — Indra 19 Ly, 0 ports, 10 Ls starport damage
HIP 20527 Invasion 16% — Indra 23 Ly, 3 ports, 834 Ls outpost + 4806 Ls planet attack, 4805 Ls planet + 595 Ls outpost damage
Nibelaako Invasion 16% — Raijin 22 Ly, 6 ports, 519 Ls planet + 16k Ls outpost attack
Patollu Invasion 14% — Leigong 22 Ly, 2 ports, 999 Ls planet attack, 992 Ls outpost damage
Putas Alert 14% — Hadad 23 Ly, 572 Ls starport, 861 Ls outpost
Vistnero Invasion 14% — Raijin 21 Ly, 3 ports, 365 Ls outpost attack, 147 Ls planet damage
Haitchane Invasion 12% — Leigong 30 Ly, 4 ports, 2794 Ls planet attack
Theemim Invasion 12% — Thor 30 Ly, 3 ports, 2718 Ls planet attack, 2726 Ls planet damage
Ge Alert 8% — Taranis 28 Ly, 109 Ls starport, 34 Ls outpost, 45 Ls planet
Poqomathi Alert 8% — Oya 24 Ly, 14 Ls outpost, 14 Ls planet
Balak Invasion 6% — Raijin 23 Ly, 0 ports, 9 Ls outpost damage
HIP 20948 Invasion 6% — Indra 24 Ly, 2 ports, 55k Ls planet attack
HIP 30260 Invasion 6% — Hadad 29 Ly, 3 ports, 3717 Ls outpost attack
HIP 6442 Invasion 6% — Leigong 28 Ly, 4 ports, pending attack report
Wangakwan Invasion 6% — Taranis 21 Ly, 2 ports, 317k Ls planet attack, 317k Ls outpost damage
Chibis Alert 4% — Cocijo 25 Ly, 1149 Ls outpost, 596 Ls planet
HIP 20616 Invasion 4% — Indra 22 Ly, 3 ports, 176k Ls planet attack, 176k Ls planet damage
HIP 9764 Invasion 4% — Leigong 24 Ly, 0 ports, 945 Ls outpost damage
Kaurukat Invasion 4% — Raijin 17 Ly, 1 port, 139 Ls starport attack, 23 Ls outpost + 283k Ls planet damage
Lunguni Invasion 4% — Leigong 23 Ly, 4 ports, 21 Ls outpost attack
MCC 105 Invasion 4% — Oya 22 Ly, 3 ports, 505 Ls outpost attack
Arietis Sector AQ-P b5-2 Invasion 2% — Leigong 24 Ly, 1 port, 2035 Ls planet attack
HIP 22524 Invasion 2% — Indra 20 Ly, 1 port, 3369 Ls planet attack, 3429 Ls planet damage
HIP 8525 Invasion 2% — Oya 18 Ly, 0 ports, 68 Ls starport damage
Khwal Invasion 2% — Cocijo 22 Ly, 4 ports, 89 Ls outpost attack
Nihal Invasion 2% — Taranis 21 Ly, 0 ports, 868 Ls outpost damage
Pegasi Sector GW-W d1-115 Invasion 2% — Raijin 23 Ly, 2 ports, pending attack report
Picenile Invasion 2% — Cocijo 25 Ly, 2 ports, 395k Ls planet attack
Senocidi Alert 2% — Taranis 20 Ly, 184 Ls starport, 3144 Ls outpost, 467k Ls planet
Wogaiawong Invasion 2% — Cocijo 32 Ly, 0 ports, 85 Ls outpost damage

Week 12, 16th February 3309​

Report
Alert repelled in Juipedun.
Ahol, Bi Dhorora, Gliese 9035, HIP 116360, HIP 20890, HIP 26274, HIP 6913, Imeut, Jaoi, Paeni defended from Invasion.

 

[Aleks Zuno]

Victory in Vogulu, eventually! That one was a 98% for quite a while, though sending a Medusa falling to the ground over Steiner hopefully contributed, as did what sounded like some dead Hydras via System chat.

It is as well for those still at M. Hadad to jump over to Yan Zangata nearby (and probably onward to Neites after that!), meanwhile Lovaroju has a healthy surge at M. Taranis. I see the next band forming nicely at M. Indra, including a spot of Alert activity at Kagutsuchi, though that (or any Alert) will need a coordinated push to begin within a couple of days at most. As it is now, unfortunately Alerts must have a successful prospect within their single cycle to be worth considering.

Top targets at 03:30 24th February 3309:
Lovaroju Invasion 28% — Taranis 27 Ly, 4 ports, 90 Ls outpost attack
Yan Zangata Invasion 20% — Hadad 22 Ly, 1 port, 70 Ls outpost attack, 98 Ls outpost damage
HIP 20485 Invasion 10% — Indra 21 Ly, 3 ports, 34 Ls starport + 35 Ls planet attack, 97 Ls outpost damage
Neites Invasion 10% — Hadad 26 Ly, 4 ports, 2002 Ls planet attack
Vistnero Invasion 8% — Raijin 21 Ly, 3 ports, 365 Ls outpost attack, 147 Ls planet damage
HIP 20492 Invasion 6% — Indra 24 Ly, 3 ports, 5791 Ls planet attack
HIP 20899 Invasion 6% — Indra 23 Ly, 3 ports, 2988 Ls planet attack

 

[Aleks Zuno]

Victory in Lovaroju! If it helps those still at M. Taranis who do not wish to move too far (~50 Ly), the initial push at Namayu has placed it quite well for completion later this cycle. We have Putas and Chibis returning as Alert activity along with newcomer Ge, various returning Invasion systems, and Pentam joining the fight!

At present, the Alert at Kagutsuchi forms part of the block of systems projected to complete in theory, although for this to occur it will need the type of early attention which may be difficult to procure with the trade-based Community Goal ongoing. Unfortunately there is no way to give objectively good advice there, and realistically one can only continue observing it for another half-day or so before decision time.

Top targets at 08:20 25th February 3309:
HIP 20485 Invasion 34% — Indra 21 Ly, 3 ports, 34 Ls starport + 35 Ls planet attack, 97 Ls outpost damage
HIP 20492 Invasion 32% — Indra 24 Ly, 3 ports, 5791 Ls planet attack
Neites Invasion 32% — Hadad 26 Ly, 4 ports, 2002 Ls planet attack
Yan Zangata Invasion 26% — Hadad 22 Ly, 1 port, 70 Ls outpost attack, 98 Ls outpost damage
Lahua Invasion 16% — Oya 19 Ly, 2 ports, 19 Ls planet attack, 10 Ls outpost damage
HIP 20899 Invasion 14% — Indra 23 Ly, 3 ports, 2988 Ls planet attack
HIP 2422 Invasion 14% — Oya 24 Ly, 7 ports, 325 Ls starport + 192 Ls planet attack
Luggerates Invasion 14% — Oya 22 Ly, 4 ports, 1473 Ls planet attack
Namayu Invasion 12% — Taranis 27 Ly, 3 ports, 255 Ls planet attack
Kagutsuchi Alert 10% — Indra 22 Ly, 42 Ls starport

 

[MVBanks]

Players in Indra area have a choice HIP 20485 starport attack or HIP 20492 planet attack. Planet attack in HIP 20485 is not active, no AX CZ, I checked last evening and also AXI reported it.

 

[Aleks Zuno]

Players in Indra area have a choice HIP 20485 starport attack or HIP 20492 planet attack. Planet attack in HIP 20485 is not active, no AX CZ, I checked last evening and also AXI reported it.

Interesting! Indeed Vlamingh's Claim shows in Navigation and the System Map as being under attack, and its docking service uses emergency protocols, but it does not start a Conflict Zone. Were it not for the attack at Bachman Port, starting a fight there could still have been useful for the restock service.

For a moment I thought the system might have been acting wrongly for its number of ports, but it seems correct:

• HIP 20485 has seven ports; five orbital, two planetary.
• There should be a five-week Invasion where the remaining ports number 7, 5, 3, 1, 0.
• Indeed we are at the third week with two abandoned from week 1, two damaged from week 2, and two attacked prior to week 4.

Everything else seems fine; the only problem seems to be the lack of Conflict Zone at Vlamingh's Claim specifically. I updated my list to note the damage at Fancher Orbital, for which the last public report must have been prior to being attacked last cycle.

 

[Ned Flandalorian]

Somebody has created an issue report for the bugged way thargoids behave when somebody docks inside a large station that is under attack: https://issues.frontierstore.net/issue-detail/58010

 

[Blaggerdy]

Thanks for that @Ned Flandalorian, I had three scout missions I wanted to complete earlier today and having read your comment I realised why a scout remained at 88% while I unloaded a pair of AX multicannons onto it for far too long. So out of open and into my player group, and all was good. Added to the report you referenced

 

[IM2D]

It is much better than having to post and read images manually—running it will use an open Galaxy map to check through every single listed system, and it reports all of the states and percentages. Right now, the DCOH list reports 14 non-complete, non-Recovery systems, whereas our list from over two hours ago has 18 of those. For example, DCOH is showing no progress in Gliese 9035, when actually it has 2%.

I answer with a question; would DCOH like to be relieved of having to update systems that way?

While DCoH is reading messages manually and have players input progression updates, it comes with a bias and it leans toward those who follow priorities from groups that assigns weekly defensive targets. In terms of updating the progression of systems in our database, we feel that CMDRs who have joined the DCoH community should feel obligated to collaborate in defending systems as a group and report back the progression of their defensive strategies.

We understand that there will be a discrepancy between machine-read data vs player-input data, however any source of data is great to the community as a whole; what we may lack in, another team may specialize towards that field and picks it up for us.

I'm going to try using the dcoh.watch list as an input and see if I can make it post progress updates.
Just as a test, I'll house it somewhere on iniv.space when it's ready.

If you have an API or a github repository, would you be inclined to sharing? Our repository is open-sourced and can be found on Github so if you need our data its open to all to use. As a council member of the DCoH community, I'm impressed by the accuracies that the INIV engine collects and that we're fortunate have both you and Aleks Zuno managing and assigning weekly defensive targets for the users of Frontier Forums to see, outside of the DCoH hub.

 

[CMDR Vulkarius]

If you have an API or a github repository, would you be inclined to sharing?

API, yes - working on it!
The internals are receiving a few ongoing changes at the moment and one major omission needs sorting (exit strategy / un-thargoiding a recovered system).
For a bit of background there, originally our bounty-hunting utility needed to detect invaded systems immediately after update 14 just to avoid sending bounty-hunters to places with no missions or only AX missions, so anything it could do to detect/record/report an invaded system became an emergency update.
Actually its original list format is still available for download, just with limited use by now (no progress / alerts).

When I have it able to clear a system and Aleksandra is happy with how the reports work, an updated JSON download is next.
I planned ahead for that and gave the cycle-specific entries a "source" property, so that you can skip entries if the source says "DCOH".
Entries updated via scan results here will have the source "INIV", though probably most will have matching data - you can consider those systems to be agreed/seconded.
Those are the only sources at the moment, though obviously that has the scope to add more.

 

[Aleks Zuno]

Victory in HIP 20492! The outlook for this cycle is at around 11–12 systems, with those listed below being of reasonable expectation. I see yet more Alert activity at Senocidi and Poqomathi, Balak and Kaurukat returning, and MCC 105 and Lunguni joining the fight!

The Alert in Kagutsuchi is at 18%; realistically, it is not keeping up well enough to imagine it finishing, the projection having slipped a bit (41% down to 35%). I think it is safe to consider it not recommended, insofar as it would need a lot of Commanders all to convene for it, many of whom want to push the present Community Goal above tier 1.

Top targets at 15:40 26th February 3309:
HIP 20485 Invasion 80% — Indra 21 Ly, 3 ports, 34 Ls starport + 35 Ls no-conflict planet attack, 677 Ls outpost + 97 Ls outpost damage
Neites Invasion 78% — Hadad 26 Ly, 4 ports, 2002 Ls planet attack
Lahua Invasion 44% — Oya 19 Ly, 2 ports, 19 Ls planet attack, 10 Ls outpost damage
Yan Zangata Invasion 44% — Hadad 22 Ly, 1 port, 70 Ls outpost attack, 98 Ls outpost damage
Pentam Invasion 42% — Taranis 29 Ly, 4 ports, 214 Ls outpost attack
HIP 2422 Invasion 30% — Oya 24 Ly, 7 ports, 325 Ls starport + 192 Ls planet attack
Luggerates Invasion 30% — Oya 22 Ly, 4 ports, 1473 Ls planet attack
Namayu Invasion 24% — Taranis 27 Ly, 3 ports, 255 Ls planet attack
HIP 20899 Invasion 22% — Indra 23 Ly, 3 ports, 2988 Ls planet attack

Somebody has created an issue report for the bugged way thargoids behave when somebody docks inside a large station that is under attack: https://issues.frontierstore.net/issue-detail/58010

I had noticed that around Starports! It "disappeared" in Solo, which I had supposed was connection problems, but that sounds as if watching a targeted Interceptor while docked in Solo may also show that problem. Either way, that is very much worth me watching short-term and warning soon after if it seems here to stay.

While DCoH is reading messages manually and have players input progression updates, it comes with a bias and it leans toward those who follow priorities from groups that assigns weekly defensive targets. In terms of updating the progression of systems in our database, we feel that CMDRs who have joined the DCoH community should feel obligated to collaborate in defending systems as a group and report back the progression of their defensive strategies.

Indeed! Since then I have noted that there is good value in having more frequent updates for the active systems, and I imagine that having a full scan to detect initial activity would bring those systems into your sights. Those cases are actually much fewer now (good!), which I think is due to some Commanders watching public activity data for listed systems and patrolling the Galaxy map for those in particular.

Thank you most kindly for helping Commanders find the higher-progress targets; this more than anything is what will increase the systems won per cycle, and indeed a close second place is getting eager Commanders out of the completed systems for lack of noticing it is done. Hopefully we can have something online for you soon!