Thargoid invasion - Next target systems?

[Aleks Zuno]

Week 74, 25th April 3310​

Maelstrom Hadad
Spire: 100% peripheral progress and two Spire sites removed!
Most Commanders will be found attacking the alternative Spire site at Col 285 Sector US-Z b14-7 instead.
Peripheral Alerts and Controls: All done!
These are Muruidooges and Col 285 Sectors RM-B b14-4, QM-B b14-2, RM-B b14-3, SH-B b14-4, KW-M c7-12, KW-M c7-30 and QM-B b14-7.
Non-peripheral Controls: Cleared five more than planned! Additional clearance effects and Week 74 targets

Report
Fourteen Alerts repelled at Muruidooges, Col 285 Sectors RM-B b14-4, JG-O c6-15, EA-Q c5-17, IA-G b11-0, IA-G b11-2, KV-F b11-2 and WC-C b13-2, 80 Tauri, HIPs 20527 and 20719, Pegasi Sector ON-S b4-2, Hyades Sector CR-J a10-1 and Arietis Sector NS-R a5-1.
Six Invasions defended at Nu Guang, Auaker, Kagutsuchi, 65 Kappa Tauri, Asletae and HIP 117177.
Seventeen Control evictions at HR 2204, Col 285 Sectors RH-B b14-5, US-Z b14-1, RH-B b14-4, RM-B b14-3, KW-M c7-12, KW-M c7-30, QM-B b14-7, SH-B b14-4, QM-B b14-2, PM-B b14-6, KW-M c7-3, QM-B b14-6, BA-P c6-3, KW-M c7-2 and RN-T d3-78, and Arietis Sector XJ-R b4-0.
Two Matrix systems cleared at Col 285 Sectors VS-Z b14-3 and SX-Z b14-0.
In addition to the defended Invasions, one recaptured system starting Recovery is HR 2204.

Targets updated at 06:40 2nd May 3310
Chibis Invasion 98% *98.2% — Cocijo 25 Ly, 3 ports, 1149 Ls outpost attack
HIP 20485 Alert 58% *58.4% — Indra 21 Ly, 27 Ls starport, 677 Ls outpost
HIP 37844 Invasion 46% — Cocijo 28 Ly, 1 port, 1699 Ls outpost attack
Isla Alert 40% — Raijin 24 Ly, 888 Ls starport, 1649 Ls outpost
Laumas Alert 26% *26.4% — Cocijo 29 Ly, 255 Ls starport, 255 Ls planet
Pegasi Sector OY-O a7-0 Alert 22% *22.5% — Raijin 28 Ly
HIP 113535 Control 20% *21% — Raijin 20 Ly, 3448 strength
Hyades Sector JH-U b3-5 Control 18% — Indra 26 Ly, 646 strength
Arietis Sector LM-V b2-2 Control 18% — Indra 25 Ly, 703 strength
Hyades Sector BR-J a10-0 Control 18% — Indra 26 Ly, 697 strength
Arietis Sector DA-Z b3 Control 18% — Indra 25 Ly, 706 strength
Hyades Sector LC-U b3-4 Control 18% — Indra 25 Ly, 702 strength
Hyades Sector UO-Q b5-2 Control 18% — Indra 26 Ly, 648 strength
Col 285 Sector RS-H b11-4 Alert 16% *17.1% — Cocijo 29 Ly
Pegasi Sector JS-Q a6-2 Alert 16% — Raijin 28 Ly
Pegasi Sector KH-V c2-25 Alert 16% — Raijin 28 Ly
Obamumbo Alert 14% *15.7% — Indra 19 Ly, 10 Ls starport, 17 Ls outpost
Scythia Control 14% *15.5% — Indra 20 Ly, 3794 strength
Col 285 Sector VY-Q c5-7 Alert 14% — Cocijo 29 Ly
Pegasi Sector SP-L a9-1 Alert 12% — Raijin 28 Ly
Pegasi Sector HH-U b3-7 Control 12% — Raijin 29 Ly, 453 strength
HIP 20948 Alert 10% *10.1% — Indra 24 Ly, 56k Ls planet
Pegasi Sector LC-U b3-4 Control 8% — Raijin 27 Ly, 600 strength
HR 8536 Alert 8% — Raijin 28 Ly
Pegasi Sector KC-U b3-1 Alert 8% — Raijin 28 Ly
Pegasi Sector PE-N a8-1 Control 8% — Raijin 27 Ly, 600 strength
Desurinbin Control 6% *6.3% — Cocijo 25 Ly, 1442 strength
HIP 30502 Control 4% *4.1% — Hadad 14 Ly, 20.4k strength
Col 285 Sector TH-C b13-3 Alert 4% *4.1% — Thor 22 Ly
Col 285 Sector AF-E b13-0 Alert 4% — Cocijo 29 Ly
HIP 113076 Control 2% *3% — Raijin 24 Ly, 1862 strength
HIP 37520 Alert 2% *2.9% — Cocijo 30 Ly, 312k Ls outpost
Montioch Control 2% *2.9% — Hadad 13 Ly, 29.3k strength
Col 285 Sector DA-E b13-3 Alert 2% *2.9% — Cocijo 30 Ly
Col 285 Sector RH-B b14-3 Control 2% *2.5% — Hadad 13 Ly, 12.5k strength
Mapon Control 2% *2.3% — Cocijo 18 Ly, 9140 strength
HIP 21261 Control 2% *2.3% — Indra 20 Ly, 4378 strength
Bormuninus Alert 2% — Raijin 24 Ly, 45 Ls outpost
Col 285 Sector US-Z b14-3 Control 2% — Hadad 11 Ly, 18k strength
Col 285 Sector BP-F b12-2 Alert 2% — Cocijo 29 Ly
Col 285 Sector LL-E b12-3 Control 2% — Thor 35 Ly
Col 285 Sector RH-B b14-0 Control 2% — Hadad 16 Ly, 6017 strength
Col 285 Sector GP-H b10-3 Control 2% — Thor 36 Ly
Col 285 Sector HP-H b10-3 Control 2% — Thor 39 Ly
Col 285 Sector YY-F b12-3 Alert 2% — Cocijo 29 Ly
Col 285 Sector ZE-P c6-11 Control 2% — Cocijo 29 Ly, 1484 strength
Hyades Sector MM-M b7-1 Control 2% — Thor 36 Ly
Pegasi Sector NY-O a7-3 Control 2% — Raijin 25 Ly, 878 strength

Notes
The Alert report lists predicted attackers.

Week 73, 18th April 3310​

Report
Eighteen Alerts repelled at HIPs 29217 and 21099, Col 285 Sectors OB-D b13-0, RM-B b14-7, OR-B b14-9, VS-Z b14-1, OR-B b14-8, VS-Z b14-6, GF-G b11-5, KB-O c6-10, MQ-F b11-3, SH-C b13-1 and QX-U d2-47, 78 Theta-2 Tauri, Pegasi Sector VK-L a9-3, Hyades Sectors IH-U b3-3 and JH-U b3-4, and HR 1403.
Six Invasions defended at Koko Oh, Unktety, HIPs 20492, 19781 and 20616, and Hyades Sector ST-Q b5-4.
Seven Control evictions at Col 285 Sectors SH-B b14-2, VS-Z b14-0, PM-B b14-1, PM-B b14-2, SH-B b14-6, US-Z b14-0 and RM-B b14-2.
The defended Invasion systems will start Recovery.
Titan Oya has overheated and exploded.

 

[Cmdr Daedalus Spyke]

My carrier, LLV Negotiator (V1J-L0K) is able to accept samples for Col 285 Sector US-Z b14-1 and is in the HIP 32764 system in-between planets A3 and A4 (131 Ls out)

 

[Aleks Zuno]

My carrier, LLV Negotiator (V1J-L0K) is able to accept samples for Col 285 Sector US-Z b14-1 and is in the HIP 32764 system in-between planets A3 and A4 (131 Ls out)

Listed, and thank you! Every involved Commander is a most precious blessing, at a time when every bit of help eases the weeks ahead.

For a little future insight, we have planned things forward using around the same amount of clearance we are achieving at present; very much due to Alerts, the result is that week 78 leaves three systems including HIP 30439, for a Titan attempt in week 79. One extra quite strong Alert prevention in week 77 causes week 78 to leave only HIP 30439; even better would be 5–6 impromptu extra clearances over the next two weeks, which could turn week 78 into a Final Ten scenario.

 

[Cyanidex]

@Aleks Zuno Spyke forgot to set his carrier's docking permissions before he leave for work. He will fix that later

 

[Cyanidex]

Target System​	Demand	Held	Carrier Name	Carrier Location
Col 285 Sector RH-B b14-4	-	5833	[TRGE] TCG Samsun (H9V-6XY)	HIP 28913

Completed.

 

[Aleks Zuno]

Opening-later-note added, and entry for Col 285 Sector RH-B b14-4 listed!

INIV is going to attempt a fairly heavy week, including the previously-tentative Col 285 Sector RH-B b14-5. The other three non-peripheral Control systems are more directly important because they expose HIP 31223 just before it attacks; the reasons for considering Col 285 Sector RH-B b14-5 are:

• I have a quite wild hypothesis about outer attacks which agrees almost entirely with the present model for attacks, but aims to explain a few discrepancies. It is difficult to test because it changes so many attackers that it would need a simulation to establish a different version of events. Without expectation of course, if it does apply then taking Col 285 Sector RH-B b14-5 now should guard Vogulu.
• Even with the likely outcome of not doing so, that one extra system (plus normal future planning!) will cause future peripheries to reach Col 285 Sector US-Z b14-3 before it attacks in week 77. This has a quite large effect; it means the difference between fighting the farthest Titan with resistance 1 instead of resistance 3, noting that an extra week to remove HIP 30439 is always possible if we need zero.

Obviously if we can clear yet another system during that time—or if said hypothesis becomes fruitful, of course—that will give us resistance 0 on the original timing.

 

[Grimscrub]

Given the... 'target rich environment'

and multiple crashes to desktop reported during Oya, I will admit concern whether zero resistance is a blessing or a curse if that led to those spawns - though how much of that was the patch is hard to judge.

More relevantly, jumping carrier to buy for that final non-peripheral - second closest system as closest was full.

Col 285 Sector RH-B b14-5

[AXI] Invicta (X5Q-83N)

Col 285 Sector JW-M c7-11

 

[Kira Goto]

Counting the number of Scouts in that picture could be some kind of cognitive function test.

On another front, Thargoids around Raijin aren’t happy. Paid a visit to Ampere Port in Nu Guang* with my (in-situ) AX FDL on the alt and hoo, it’s something, alright. Enough to qualify as chaos, that’s for sure. Even had a total of three Glaive drop-ins, or at least those were the ones I witnessed, throughout a single run. None of them fried my shards though, so that’s something.

The Hydras were also fun. In no small part thanks to one spontaneously deciding to become a zombie and resurrect with 5 hearts despite being killed prior already. I think I got my share of excitement for the day… or several… in that one run.

*Oya has met the hammer and I’ve not really got much of an investment in the other Titans so that (Raijin)’s where I’ll be if I fancy some adrenaline rushes.

 

[Jack Brolin]

Mercenary Mercantile is back in Col 285 Sector VS-Z b14-6 (many thanks to those who cleared the alert last week!) and I've installed a shipyard to make life easier for anyone headed to VS-Z b14-3 with an SCO drive - the jump's 7.92 ly

 

[Cmdr Daedalus Spyke]

Okay, LLV Negotiator is open and ready for business. Sorry about the delay. One of these days I'll figure out my login so I can post from my phone but I'm happy enough just using my PC for now.

 

[Aleks Zuno]

Very well done to all at the M. Hadad Spire sites—one-fifth peripheral progress in a day still astounds me!

HR 2204 actually is much of the way to completion; we delivered a sizeable boost, and yet more of the remainder awaits delivery. The combined order is updated such that completing both Carriers should complete the system, and I will try to notify if other progress there reduces the amount needed.

Okay, LLV Negotiator is open and ready for business. Sorry about the delay. One of these days I'll figure out my login so I can post from my phone but I'm happy enough just using my PC for now.

No worries! A suggestion though, given that a visit to Col 285 Sector US-Z b14-1 is planned next—is a move to the quieter and asteroid-free Col 285 Sector SX-Z b14-1 possible? If HIP 32764 is also your parking for Col 285 Sector US-Z b14-7 then definitely remain there instead, noting that we may end up doing a direct delivery for partial progress depending on wing preference.

 

[Cmdr Daedalus Spyke]

Yeah, I can move my carrier there if it's easier for the samplers; lord knows there's fewer carriers to sort through as well there.
HIP 32764 is my parking for the Spire but I really don't mind making two jumps instead of one (currently using a shard-conda with SCO drive for Orthrus mulching).

In short, consider it moved and now around the main star in Col 285 Sector SX-Z b14-1.

 

[Aleks Zuno]

Thank you—it should see at least much of its order satisfied this evening!

---

As an aside, I have a general preference question which really involves everyone here! We have the realistic weekly clearance planned all the way until we reach T. Hadad; this assumes the normal simulation rules of course, and accounts exactly for Alerts appearing along the way. There is some room for adjusting to choose exactly what occurs at the end, though:

• With the present plan, week 77 leaves the popular 9th place Spire at Col 285 Sector US-Z b14-7 alive. Two Alerts appear, thus Week 78 begins with 11 systems and leaves just one, the final Spire at HIP 30439. Presumably, we then attack the Titan with resistance 1.
• Option: For the fairly steep cost of 21063, we can move the popular Spire to 8th place, thus Week 78 begins with 10, thus leaves none.
• Option: For a much cheaper cost, we can advance one more system in an earlier week, although this will topple the popular Spire in Week 77. Week 78 still begins with 10 and ends with none, just with HIP 30439 as the only Spire to do so.
• Option: For a clearance rebate of 3311 in Week 75, we could make Week 78 end with two systems, although this would be purely for science!

We have no preference here; to us, it matters not what remains as long as the attacks stop. That said, other Titan attackers may want resistance 0 rather than resistance 1, or other Commanders may want fully-cleared space, or we may discover some Titan problem with leaving a Spire standing.

The unlikely science option would reveal what becomes of a Spire site after its Titan explodes, and whether it can still be used to advance the residual systems afterwards. Resistance 2 may be a quite unpopular choice, though!

 

[Leadfoot]

Rescue missions include a wanted criminal in the group???

Running an evacuation from Muruidooges and on departure, get scanned it shows one of the people (and I can't tell which one) is wanted.

"Hey, would you like to have me hit the eject button on that guy so you can scoop him up?"
"No, we'd just rather blast your imperial cutter with all those refugees to space dust."
"Gee, thanks for the lack of options there."

Is there something in the missions you're accepting when picking groups of people that says "BTW, one of our people is wanted." ?
If not, if they could add that little detail in there...

 

[Kira Goto]

Rescue missions include a wanted criminal in the group???

Running an evacuation from Muruidooges and on departure, get scanned it shows one of the people (and I can't tell which one) is wanted.

"Hey, would you like to have me hit the eject button on that guy so you can scoop him up?"
"No, we'd just rather blast your imperial cutter with all those refugees to space dust."
"Gee, thanks for the lack of options there."

Is there something in the missions you're accepting when picking groups of people that says "BTW, one of our people is wanted." ?
If not, if they could add that little detail in there...

I don’t know if it states it anywhere, but it’s a silly/nonsensical bug(maybe, Frontier never commented if intentional or not) which appeared with the update that added the VIP evac missions and turned the bulk evacs into “semi-bulk” personal evacs with economy cabins as an option at the same time.

But it would be too sensible to stop caring about that during a mass evacuation scenario, would it?

 

[MartinG]

Are there Spire Sabotage missions available this week for any of Hadad’s spires? I would like to put the stuff I harvested in Week 72 at Oya’s spire to good use

 

[Grimscrub]

Are there Spire Sabotage missions available this week for any of Hadad’s spires? I would like to put the stuff I harvested in Week 72 at Oya’s spire to good use

Rescue ship Foerster in the Xinca system should be offering some missions for several of the spires near Hadad last time I checked -

You could cross-reference those with the Google Doc some of the Canonn folks had set up previously to see if the supercruise distance, gravity, etc. for a given system's spire works for you - work at any active spire in the region will progress the outer systems, just not every spire will be getting missions.

From some tests by the XSF folk, it appeared doing the actual sabotage has an impact even without a mission, but of course if you can get a mission hey, more rewards are nice, and the missions to grab materials and get more compound to Keep sabotaging are helpful.

 

[Planewalker]

Rescue missions include a wanted criminal in the group???

Yea i had one of those too yesterday.
-just assumed it was due to the passenger being from an anarchy faction. XD

It kinda adds to the tention, so i don't mind it that much. -advance notice would be nice as you point out.

 

[MartinG]

Is there something in the missions you're accepting when picking groups of people that says "BTW, one of our people is wanted." ?

In fact, there is, although it is quite well hidden in the part of the UI that seasoned pilots (myself included) tend to forget exists:

 

[Shurimal]

In fact, there is, although it is quite well hidden in the part of the UI that seasoned pilots (myself included) tend to forget exists:

This is a VIP evac, right? Does it also show passenger status for non-VIP (bulk) evacs? Because I can't recall finding anything that would give passenger legal info for bulk missions...