Thargoid invasion - Next target systems?

Well, 7k buy order down, 11k carrier capacity remaining and been asked for another target by them no less... anywhere else that would be, acceptable/positive to take out this week?

-- initial skim, raised Col 285 Sector RN-T d3-78 to take out the future attacker as seemingly best option, not heard back from them though so I may've been a bit late for evening comms.

How many bonus targets will we get through each week... well, gives more time to prep the harder systems later i suppose.
 
Last edited:
Well, 7k buy order down, 11k carrier capacity remaining and been asked for another target by them no less... anywhere else that would be, acceptable/positive to take out this week?
-- initial skim, raised Col 285 Sector RN-T d3-78 to take out the future attacker as seemingly best option.

The general best option is simply the next-weakest system, which by definition provides the greatest increase to the strength value of the next periphery, or to the periphery after that if a Spire site appears. Non-peripheral attackers in a week have more priority that week if it is reasonably economic to do so, and there is some value in choosing not necessarily the next-weakest if it means not having to move the Carrier! Finally, a system may be simply useful to recapture if it will have nice services, or give good asteroid-free Carrier parking.

Regarding economy and as an example, it makes little sense to stop an attacker such as Omumba (27942) this week because its advance of two (including the stopped Alert) costs more than simply advancing four, which it would be as well to do instead. In a more dense Maelstrom scenario, it can be also bad if a deeper cleared system then becomes a target later.

Aiming for the non-peripheral attackers for next week is not a bad idea, although given that they are not attacking yet and do not advance the next periphery (nor any periphery in the context of a fully-planned collapse which already marked them for manual removal), once again the value of delivering one week later comes if a longer respite interval would help in a dense scenario.

Col 285 Sector RN-T d3-78 will be a peripheral attacker—or indeed, has become a peripheral attacker thanks to the absolutely amazing clearance this week—thus loses that priority aspect. As the second-weakest though, it is still a good strength increase! Said increase consists of comparing the cleared system (6731) to the incoming system (7805). It is also closer to your parking spot, albeit just about on the edge of jump range for a harvest vessel!
 
The general best option is simply the next-weakest system, which by definition provides the greatest increase to the strength value of the next periphery, or to the periphery after that if a Spire site appears. Non-peripheral attackers in a week have more priority that week if it is reasonably economic to do so, and there is some value in choosing not necessarily the next-weakest if it means not having to move the Carrier! Finally, a system may be simply useful to recapture if it will have nice services, or give good asteroid-free Carrier parking.

Regarding economy and as an example, it makes little sense to stop an attacker such as Omumba (27942) this week because its advance of two (including the stopped Alert) costs more than simply advancing four, which it would be as well to do instead. In a more dense Maelstrom scenario, it can be also bad if a deeper cleared system then becomes a target later.

Aiming for the non-peripheral attackers for next week is not a bad idea, although given that they are not attacking yet and do not advance the next periphery (nor any periphery in the context of a fully-planned collapse which already marked them for manual removal), once again the value of delivering one week later comes if a longer respite interval would help in a dense scenario.

Col 285 Sector RN-T d3-78 will be a peripheral attacker—or indeed, has become a peripheral attacker thanks to the absolutely amazing clearance this week—thus loses that priority aspect. As the second-weakest though, it is still a good strength increase! Said increase consists of comparing the cleared system (6731) to the incoming system (7805). It is also closer to your parking spot, albeit just about on the edge of jump range for a harvest vessel!
AffaGammaRanna here, I parked a Carrier with 1200 samples buy order for Col 285 Sector RN-T d3-78 on my
"Bitcoin Valley [H0X-BHK]" in Col 285 Sector RM-B b14-2.

(for samples from target Col 285 Sector RN-T d3-78)

We will delivery next week when 85% Spire is reached.
 
AffaGammaRanna here, I parked a Carrier with 1200 samples buy order for Col 285 Sector RN-T d3-78 on my
"Bitcoin Valley [H0X-BHK]" in Col 285 Sector RM-B b14-2.
(for samples from target Col 285 Sector RN-T d3-78)
We will delivery next week when 85% Spire is reached.

Thank you for all the help!

Regarding Col 285 Sector RN-T d3-78, I imagine it will be clear tonight instead:
  • Between @Grimscrub and AIR1, it sounded as if it is a target this week.
  • It has already 24% progress delivered!
I presume the plan was to complete an order at the Invicta then deliver it alongside everything already collected for Col 285 Sector KW-M c7-2; if so, it will be as well to deliver anything you have for Col 285 Sector RN-T d3-78. INIV also should be able to help collect any remainder this evening!
 
Thank you for all the help!

Regarding Col 285 Sector RN-T d3-78, I imagine it will be clear tonight instead:
  • Between @Grimscrub and AIR1, it sounded as if it is a target this week.
  • It has already 24% progress delivered!
I presume the plan was to complete an order at the Invicta then deliver it alongside everything already collected for Col 285 Sector KW-M c7-2; if so, it will be as well to deliver anything you have for Col 285 Sector RN-T d3-78. INIV also should be able to help collect any remainder this evening!
I have 1200 samples for Col 285 Sector RN-T d3-78. Want those delivered tonight? I thought it was for next week ;-)
 
I presume the plan was to complete an order at the Invicta then deliver it alongside everything already collected for Col 285 Sector KW-M c7-2; if so, it will be as well to deliver anything you have for Col 285 Sector RN-T d3-78. INIV also should be able to help collect any remainder this evening!
28% now. I'll try to add a few 128 deliveries to the rescue ship this evening (many hands make light work and all that)
 
I have 1200 samples for Col 285 Sector RN-T d3-78. Want those delivered tonight? I thought it was for next week ;-)

Yes, please deliver those! I had planned originally to clear that system next week, but clearance is moving so quickly that it will be cleared tonight instead—anyone holding Research for Col 285 Sector RN-T d3-78 should deliver it as soon as feasible.


28% now. I'll try to add a few 128 deliveries to the rescue ship this evening (many hands make light work and all that)

Thank you! I would like to discover how much @Grimscrub has before setting out as a full wing, but we will get it finished even if the answer is zero samples. 28% now and 1200 on its way means that at most 3647 remains!
 
Between @Grimscrub and AIR1, it sounded as if it is a target this week.
I did not have full info - there are precisely 0 samples for RN-T on my carrier, flat situation was that I had been asked for another system as a suggestion at midnight on a workday, and offered what i could see before I passed out.

I'm going to go get Col 285 Sector KW-M c7-2 delivered already now that I'm back from work, rested and all.
 
That is quite fine! V has sent INV Astral Flame on its way to Col 285 Sector RN-T d3-79 with an open order for Col 285 Sector RN-T d3-78, which should cover the remainder from the delivered progress plus held progress. We will also start collecting there at some moment within the next hour; that system will be completed!
 
AIR1 are still delivering so, that was Outside the 1200 already gathered/any INIV started gathering in the last hour and change i believe?...

Between that, the 7k just Appearing suddenly for first system I was covering this week, few thousand partial order being filled silently for Astral Flame before...
The support is appreciated mystery forces but, would love to hear from you, know who to credit/have the heads up to avoid over-sampling for a given target =p
 
Indeed—we had barely the arena ready, so that delivery comes very thankfully sooner rather than later! I could not possibly ask for more this week in the context of starting anything anew, so for the moment the presumption is relax-time instead, Galaxy map surprises permitting.
 

Maelstrom Hadad, week 75​

Notes:
  • 100% peripheral progress is desirable to remove two Spire sites Col 285 Sector KW-M c7-15 and HIP 31223, both being attackers.
    • Most Commanders are attacking the inner Col 285 Sector US-Z b14-7 to achieve this.
  • Direct progress in peripheral systems can wait until they reach 85%; consider non-peripheral progress in the meantime!
  • By all means post if you are completing a system, and whether an open Carrier order is involved.
  • The planned clearance will leave two Control in week 78, with the option to clear it or to attack the Titan. See below for other outcomes!

Targets:

Peripheral systems 100%15%HeldCarrier/OwnerLocationNote
Vogulu654[VANS] Scotus KNZ-B9LMuruidoogesDone
Fotlandjera727Done
Bi Dhorora929Done
Col 285 Sector KW-M c7-15Spire site100%
Col 285 Sector RH-B b14-0921925LLV Negotiator V1J-L0KCol 285 Sector RH-B b14-4Done
HIP 31223Spire site100%
Col 285 Sector QM-B b14-110101010INV. Wrath of Winter H2V-L3VCol 285 Sector QM-B b14-7Delivered
Col 285 Sector KW-M c7-511161120INV. Wrath of Winter H2V-L3VCol 285 Sector QM-B b14-7Delivered
Col 285 Sector QM-B b14-011301130INV. Wrath of Winter H2V-L3VCol 285 Sector QM-B b14-2Delivered
Col 285 Sector KW-M c7-1311711180LLV Negotiator V1J-L0KCol 285 Sector WN-Z b14-0Done
Inner systemsStrength
HIP 31648 **8158Done
Col 285 Sector KW-M c7-14 *985610000[TRGE] TCG Samsun H9V-6XYCol 285 Sector RM-B b14-3Delivered | Update
Col 285 Sector KW-M c7-4 *10044 → 80658893[AXI] Invicta X5Q-83NCol 285 Sector RN-T d3-78Delivered | Update
Col 285 Sector QM-B b14-31083111000[AXI] Invicta X5Q-83NCol 285 Sector QM-B b14-2Delivered | Update
Col 285 Sector QM-B b14-413964~5500[AXI] Invicta X5Q-83NCol 285 Sector QM-B b14-2Open? | Update

Titan rescues stored for week 76:
2200 from DemiserofD | Update

Resulting week 76 periphery:

SystemStrength15%With rescues
HIP 30502 **2128131932753
Omumba ** ¹2794241923752
Montioch **3020045304090
Col 285 Sector US-Z b14-2120481808
Col 285 Sector RH-B b14-3128001920
Col 285 Sector QM-B b14-4139642095
Col 285 Sector SH-B b14-1147902219
Col 285 Sector PM-B b14-0 **147932219
Col 285 Sector KW-M c7-7 **158402376
Col 285 Sector QM-B b14-5160562409
Periphery line
Col 285 Sector KW-M c7-6172322585
HIP 2922617619
Col 285 Sector US-Z b14-3 ***18380
Col 285 Sector US-Z b14-7 ***Spire site

* Projected to attack after this week 75.
** Projected to attack after next week 76.
*** Projected to attack after week 77.
1. Only versus Muruidooges, which will be attacked anyway.

Other possible and quite expensive outcomes:
  • Clearing one more will save time next week by moving Col 285 Sector KW-M c7-7 into the periphery.
  • Clearing two more will leave three Control in week 78.
  • Clearing three more will leave two Control in week 78.
  • Clearing four more will leave one Control in week 78, the Spire system HIP 30439.
  • At great expense, clearing five more will leave zero in week 78 and allow use of Col 285 Sector US-Z b14-7 to do it.
 
Last edited:

Week 75, 2nd May 3310​

Maelstrom Hadad
Spire: Both Col 285 Sector KW-M c7-15 and HIP 31223 completed.
Many Commanders will be attacking the alternative Spire site at Col 285 Sector US-Z b14-7 instead.
Peripheral Alerts and Controls are done.
These are Vogulu, Fotlandjera, Bi Dhorora and Col 285 Sectors RH-B b14-0, QM-B b14-1, KW-M c7-5, QM-B b14-0 and KW-M c7-13.
Non-peripheral Control attackers are cleared; one other open order is on the M. Hadad week 75 list.

Report
Twenty-one Alerts repelled at Vogulu, Bi Dhorora, Fotlandjera, HIP 20019, Col 285 Sectors SI-T d3-89, HF-G b11-3, JG-O c6-13, NQ-F b11-1, RW-D b12-0, KB-O c6-11, GP-H b10-2, VY-F b12-3, VY-F b12-1, AF-E b13-3, DA-E b13-1, OS-T d3-68, OS-T d3-76, PM-J b10-3, PS-T d3-152 and ZE-P c6-18, and Synuefe OU-D b45-0.
Seven Invasions defended at Chibis, Laumas, Isla, Bormuninus, Obamumbo and HIPs 20948 and 37520.
Fourteen Control evictions at Col 285 Sectors KW-M c7-4, KW-M c7-14, SH-C b13-0, QM-B b14-3, KW-M c7-5, QM-B b14-0, QM-B b14-1, KW-M c7-13, RH-B b14-0 and DA-E b13-3, HIP 31648, Pegasi Sectors JS-Q a6-2 and NY-O a7-4, and Hyades Sector MM-M b7-1.
Two Matrix systems cleared at Col 285 Sector KW-M c7-15 and HIP 31223.
The defended Invasion systems will start Recovery.

Targets updated at 06:30 9th May 3310
Hyades Sector UO-Q b5-2 Control 86% — Indra 26 Ly, 111 strength
HIP 37844 Invasion 80% — Cocijo 28 Ly, 0 ports, 1699 Ls outpost damage
HIP 20485 Invasion 70% *70.1%Indra 21 Ly, 7 ports, 677 Ls outpost + 97 Ls outpost attack
Tvasu Alert 44% *44.3%Raijin 28 Ly, 17 Ls starport, 29 Ls outpost, 17 Ls planet
Arietis Sector KM-T a4-2 Alert 30% — Indra 25 Ly
HIP 20056 Alert 20% — Indra 24 Ly, 2487 Ls outpost, 182 Ls planet
Hyades Sector TO-Q b5-2 Control 20% — Indra 23 Ly, 1336 strength
58 Tauri Control 18% — Indra 22 Ly, 1428 strength
Holvandalla Alert 14% *14.3%Raijin 21 Ly, 86 Ls starport, 19 Ls outpost
Arietis Sector KM-T a4-0 Alert 12% — Indra 25 Ly
Hyades Sector QI-S b4-2 Alert 12% — Indra 25 Ly
Arietis Sector LM-V b2-2 Control 10% *11.3%Indra 25 Ly, 760 strength
Arietis Sector DA-Z b3 Control 10% — Indra 25 Ly, 774 strength
HIP 22203 Control 10% — Indra 25 Ly, 778 strength
Hyades Sector BR-J a10-0 Control 10% — Indra 26 Ly, 765 strength
Hyades Sector JH-U b3-5 Control 10% — Indra 26 Ly, 709 strength
Hyades Sector LC-U b3-4 Control 10% — Indra 25 Ly, 771 strength
Pegasi Sector RE-N a8-2 Alert 10% — Raijin 28 Ly
Pegasi Sector NY-O a7-5 Control 6% *7.4%Raijin 24 Ly, 1142 strength
Hosan Alert 6% *7.3%Raijin 28 Ly, 539 Ls outpost
HIP 18702 Invasion 6% *6.4%Thor 35 Ly, 1 port, 2004 Ls outpost attack
Pegasi Sector XQ-J a10-1 Alert 6% — Raijin 28 Ly
Jawul Alert 4% *5.6%Raijin 27 Ly, 3045 Ls starport, 3028 Ls outpost
HIP 20491 Alert 4% *4.4%Indra 23 Ly, 1714 Ls planet
HIP 19157 Alert 4% *4.1%Indra 22 Ly, 705 Ls starport, 1277 Ls outpost
Ngolite Alert 4% — Raijin 27 Ly, 48 Ls starport, 2873 Ls planet
Aurus Alert 4% — Raijin 26 Ly, 130 Ls planet
Ixbaksha Control 4% — Raijin 23 Ly, 2520 strength
Omumba Control 2% *3.3%Hadad 14 Ly, 27k strength
HIP 18857 Alert 2% *2.8%Thor 25 Ly, 1746 Ls starport, 962 Ls outpost, 15k Ls planet
Pegasi Sector KH-V c2-25 Control 2% *2.7%Raijin 28 Ly, 615 strength
HIP 21946 Alert 2% *2.6%Indra 24 Ly, 1916 Ls outpost
Montioch Control 2% *2.5%Hadad 13 Ly, 29.4k strength
Col 285 Sector AF-E b13-5 Control 2% — Cocijo 26 Ly, 1500 strength
Desurinbin Control 2% — Cocijo 25 Ly, 1510 strength
HIP 21261 Control 2% — Indra 20 Ly, 4393 strength
HR 8536 Control 2% — Raijin 28 Ly, 608 strength
Pegasi Sector HH-U b3-7 Control 2% — Raijin 29 Ly, 504 strength
Pegasi Sector KC-U b3-1 Control 2% — Raijin 28 Ly, 1493 strength
Pegasi Sector OY-O a7-0 Control 2% — Raijin 28 Ly, 614 strength
Pegasi Sector SP-L a9-1 Control 2% — Raijin 28 Ly, 599 strength
Scythia Control 2% — Indra 20 Ly, 4402 strength
Varlawoth Control 2% — Thor 29 Ly, 1482 strength
Wanmi Alert 2% — Raijin 26 Ly, 951 Ls outpost, 957 Ls planet

Notes
The Alert report lists predicted attackers.

Week 74, 25th April 3310​

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.
 
Last edited:
Target System
DemandHeldCarrier NameCarrier LocationDistance
Col 285 Sector KW-M c7-14-10000[TRGE] TCG Samsun (H9V-6XY)Col 285 Sector RM-B b14-39.85 LY

Cleared.
 
Last edited:
Target SystemDemandHeldCarrier NameCarrier LocationDistance
Col 285 Sector KW-M c7-131180-LLV Negotiator (V1J-L0K)Col 285 Sector WN-Z b14-05.42 LY
If needed*
(I even remembered to set docking permissions to "ALL" before leaving for work this time!)
 
Last edited:
Target System
Demand
Held
Carrier Name
Carrier Location
Distance
Vogulu​
654​
-​
[VANS] Scotus (KNZ-B9L)​
Muruidooges​
5.94 LY​

Docking: ALL
Notoriety: ALLOWED
Full RnR facilities, Shipyard, Redemption Office and Universal Cartographics
 
Last edited:
Target System
Demand
Held
Carrier Name
Carrier Location
Distance
Vogulu​
4096​
-​
[VANS] Scotus (KNZ-B9L)​
Muruidooges​
5.94 LY​

Are you sure about that high a demand for Vogulu? As a peripheral system it will reach 85% just from Spire actions, after which it needs only 654—and even that delivery may be racing against Commanders completing missions!
 
Top Bottom