Thargoid invasion - Next target systems?

I just have a question; why in Fargod's name do you get a f... fine in an active AX CZ area and get an anonymous access to the base while fighting in a CZ? How does that work? What's the logic behind this stupid interaction? Like i needed more reasons to never interact with this...
If you mean the station itself is fining you for firing inside the no-fire zone, it's because those CZs are not meant to exist. For whatever reason, systems retaken from the thargoids are not losing their CZs when they go back to being human controlled and the stations don't recognize they are under attack.
 
That is a very good-looking start—victories in HIPs 20485 and 7143, Arietis Sector FG-Y d66 and Col 285 Sectors NG-E b12-3 and NG-E b12-4, with more well underway!

Evictions at 07:10 28th July 3309:
Ixbaksha Control 64% — Raijin 23 Ly, 945 strength
HIP 9764 Control 40% — Leigong 24 Ly, 1156 strength

Alerts:
Vogulu Alert 56% *56.7%Hadad 21 Ly, 336 Ls starport, 471 Ls outpost
Namayu Alert 26% — Taranis 27 Ly, 374 Ls outpost, 255 Ls planet
Balak Alert 22% — Raijin 23 Ly, 9 Ls outpost, 16 Ls planet
Hez Ur Alert 18% — Cocijo 22 Ly, 446 Ls starport
HR 1403 Alert 14% *15.6%Indra 25 Ly, 194 Ls starport, 62k Ls outpost, 194 Ls planet

Clean-up:
Pegasi Sector OI-S b4-1 Alert 38% — Raijin 26 Ly, empty
Cephei Sector WO-A b4 Alert 36% — Oya 15 Ly, empty


This week will be a bit lighter on the part of INIV with strictly no plans which would rely on continuing after update 16, although we will do a bit of trimming here and there; at minimum bring M. Thor down to two attacks, and guard Kagutsuchi and Isla. Ordinarily the next steps would be to guard Laumas first then evict Mahlina ahead of guarding Col 285 Sector ZE-P c6-11, but I imagine the latter could approach or fall after update 16, so I would prefer not to promise that.

As a note regarding a system not to trim, and unless anything has changed on the part of @Starsong, I am quite sure that the plan is to leave Hyades Sector GW-W d1-87 around. It can attack Senocidi, but I believe the longer-term plan is that it attacks Gandje later.


I just have a question; why in Fargod's name do you get a f... fine in an active AX CZ area and get an anonymous access to the base while fighting in a CZ? How does that work? What's the logic behind this stupid interaction? Like i needed more reasons to never interact with this...

To expand a bit on the more direct answer you have from Ned, those port conflicts are an error of which many Commanders are making use to counter the other error of having none around if we are winning. Indeed it is far from ideal, but at least one can dock and clear the minor fines immediately, and the conflict and missions help a lot when they appear in an Alert system!
 
As a note regarding a system not to trim, and unless anything has changed on the part of @Starsong, I am quite sure that the plan is to leave Hyades Sector GW-W d1-87 around. It can attack Senocidi, but I believe the longer-term plan is that it attacks Gandje later.
That would depend on how useful it is to clear GW-W d1-87 - there is a second candidate (Trianguli Sector EQ-Y b3) to attack Gandje. It's a case of whether it's better to protect Senocidi (starport for evacs, but planetaries are unfeasibly far away for invasion defence) or 29 e Orionis (no starport, but two low-grav planetaries).
 
Victories in Col 285 Sector YT-Q c5-12 and HIP 22203!

Evictions at 18:30 28th July 3309:
Ixbaksha Control 66% — Raijin 23 Ly, 893 strength
HIP 9764 Control 40% — Leigong 24 Ly, 1156 strength

Alerts:
Vogulu Alert 96% *96.7%Hadad 21 Ly, 336 Ls starport, 471 Ls outpost
HR 1403 Alert 38% — Indra 25 Ly, 194 Ls starport, 62k Ls outpost, 194 Ls planet
Namayu Alert 30% *30.5%Taranis 27 Ly, 374 Ls outpost, 255 Ls planet
Balak Alert 28% — Raijin 23 Ly, 9 Ls outpost, 16 Ls planet
Hez Ur Alert 22% *23.9%Cocijo 22 Ly, 446 Ls starport, 236 Ls outpost

Clean-up:
Pegasi Sector OI-S b4-1 Alert 40% *41.4%Raijin 26 Ly, empty
Cephei Sector WO-A b4 Alert 36% *36.1%Oya 15 Ly, empty
Pegasi Sector FW-W d1-110 Alert 34% — Raijin 25 Ly, empty


That would depend on how useful it is to clear GW-W d1-87 - there is a second candidate (Trianguli Sector EQ-Y b3) to attack Gandje. It's a case of whether it's better to protect Senocidi (starport for evacs, but planetaries are unfeasibly far away for invasion defence) or 29 e Orionis (no starport, but two low-grav planetaries).

Regarding those two options, and assuming Invasions at Gandje are completed immediately and therefore have a four-week cycle, my comments are:
  • Hyades Sector GW-W d1-87 will alternate between Gandje and one of Senocidi, Cao Tzu and Hyades Sector AV-O b6-5 in that order, all of which are inhabited.
  • If cleared to allow the room for it, Trianguli Sector EQ-Y b3 will alternate between Gandje and one of many other empty options before reaching 29 e Orionis.
I think the Trianguli option is better; at present it will be Gandje first, 29 e Orionis, Gandje, then only 29 e Orionis again if those other EQ-Y systems did not get cleared before or during the previous attack there. Meanwhile and setting aside that idea, clearing the Hyades option to guard Senocidi is actually quite favourable!

I would feel terrible for messing up your plan though, so I am thinking to focus on easing the inhabited attacks elsewhere for the moment and only consider M. Taranis if you are sure it will work well in the end, time permitting of course!
 
Plan wise, at this point it's clear that if things do not change the systems will be consistently repelled as alerts, and if they Do change then we could equally end up mired in a dozen invasions and forced to pick/choose again, at which point deliberately leaving a system because it attacks one we like would become comically silly in hindsight...

So, no restrictions on recapture from me at least, I'll accept the angry letters later if 16 changes little and we're in the 'congratulations, you won, that means you have nothing to do' era.
 
Plan wise, at this point it's clear that if things do not change the systems will be consistently repelled as alerts, and if they Do change then we could equally end up mired in a dozen invasions and forced to pick/choose again, at which point deliberately leaving a system because it attacks one we like would become comically silly in hindsight...

So, no restrictions on recapture from me at least, I'll accept the angry letters later if 16 changes little and we're in the 'congratulations, you won, that means you have nothing to do' era.
Yeah. Let’s snap the link, it’ll probably be repelled anyway if it get Alerted under these conditions, as much as I hate to admit it - and we don’t know if we’ll still be able to reliably clear Controls after U16.
 
Victories in Col 285 Sectors IA-G b11-3, SM-C b13-1, SM-C b13-2 and OB-E b12-4, HIPs 116542, 8078 and 9764, Vogulu, Ixbaksha and Hyades Sector MT-I b9-1! M. Leigong loses one attack, M. Thor loses two and Isla is guarded.

Following those two excellent recaptures HIP 20741 is doing well. Tougeir is a steep target which would need a bit of help, although it is also an excellent tactical choice, and having enough of a head-start there could be worth INIV joining and seeing it to completion.

Alerts at 08:50 29th July 3309:
HR 1403 Alert 74% *75%Indra 25 Ly, 194 Ls starport, 62k Ls outpost, 194 Ls planet
Namayu Alert 70% — Taranis 27 Ly, 374 Ls outpost, 255 Ls planet
Hez Ur Alert 52% — Cocijo 22 Ly, 446 Ls starport, 236 Ls outpost
Balak Alert 40% *41%Raijin 23 Ly, 9 Ls outpost, 16 Ls planet
HIP 20948 Alert 22% *22.9%Indra 24 Ly, 56k Ls planet
Bi Dhorora Alert 20% — Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet

Evictions:
HIP 20741 Control 20% *20.5%Indra 24 Ly, 1481 strength
Tougeir Control 12% *13.3%Oya 16 Ly, ~11.1k strength

Clean-up:
Pegasi Sector OI-S b4-1 Alert 48% *49.7%Raijin 26 Ly, empty
Cephei Sector WO-A b4 Alert 42% — Oya 15 Ly, empty
Pegasi Sector FW-W d1-110 Alert 40% — Raijin 25 Ly, empty
Cephei Sector FB-X b1-1 Alert 30% — Oya 20 Ly, empty
Pegasi Sector QE-N a8-2 Control 24% — Raijin 26 Ly, empty, 327 strength


Yeah. Let’s snap the link, it’ll probably be repelled anyway if it get Alerted under these conditions, as much as I hate to admit it - and we don’t know if we’ll still be able to reliably clear Controls after U16.

Understood; I will place guarding Senocidi just behind guarding Kagutsuchi, if Hyades Sector GW-W d1-87 is still incomplete by then. Indeed I am quite happy to leave a Control system around if you want such, while it is entirely the call of Commanders repelling Alerts whether to allow one to proceed!


Additional:
Plan wise, at this point it's clear that if things do not change the systems will be consistently repelled as alerts, and if they Do change then we could equally end up mired in a dozen invasions and forced to pick/choose again, at which point deliberately leaving a system because it attacks one we like would become comically silly in hindsight...

At least we will have plenty of time to decide, though! The first attack on Gandje is not for another two weeks yet, so if we still have the means to remove Trianguli Sector EQ-Y b3 then you still have an exit-strategy.
 
Last edited:
Victories in HR 1403, Col 285 Sector BF-E b13-1 and Arietis Sectors LM-V b2-3 and NH-V b2-0Kagutsuchi is guarded!

Alerts at 18:30 29th July 3309:
Namayu Alert 80% *81.4%Taranis 27 Ly, 374 Ls outpost, 255 Ls planet
Hez Ur Alert 56% *57%Cocijo 22 Ly, 446 Ls starport, 236 Ls outpost
Balak Alert 52% — Raijin 23 Ly, 9 Ls outpost, 16 Ls planet
Gliese 9035 Alert 38% — Oya 20 Ly, 556 Ls planet
HIP 20948 Alert 32% *32.4%Indra 24 Ly, 56k Ls planet
Bi Dhorora Alert 26% *26.3%Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet

Evictions:
HIP 20741 Control 20% *21%Indra 24 Ly, 1472 strength
Tougeir Control 14% *14.4%Oya 16 Ly, ~11.0k strength

Clean-up:
Cephei Sector WO-A b4 Alert 72% *72.3%Oya 15 Ly, empty
Pegasi Sector OI-S b4-1 Alert 50% — Raijin 26 Ly, empty
Pegasi Sector FW-W d1-110 Alert 44% — Raijin 25 Ly, empty
Cephei Sector FB-X b1-1 Alert 30% *30.1%Oya 20 Ly, empty
Cephei Sector ZE-A c8 Alert 28% — Oya 20 Ly, empty
Pegasi Sector QE-N a8-2 Control 24% — Raijin 26 Ly, empty, 327 strength
 
Victories in Hyades Sectors GW-W d1-87 and LY-I b9-0, Cephei Sector WO-A b4, HIP 6251, Arietis Sectors VJ-R b4-2 and VJ-R b4-3, Col 285 Sectors KW-M c7-16, RM-B b14-4 and YT-Q c5-14, and Mesarthim! Senocidi is guarded, Namayu needs probably one exploded Orthrus for completion, and the eviction at HIP 6442 is very much on-course for taking away the last attack from M. Leigong.

Alerts at 08:40 30th July 3309:
Namayu Alert 98% *99.3%Taranis 27 Ly, 374 Ls outpost, 255 Ls planet
Balak Alert 80% — Raijin 23 Ly, 9 Ls outpost, 16 Ls planet
Hez Ur Alert 70% — Cocijo 22 Ly, 446 Ls starport, 236 Ls outpost
Bi Dhorora Alert 54% — Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet
Gliese 9035 Alert 50% — Oya 20 Ly, 556 Ls planet
HIP 20948 Alert 44% *44.3%Indra 24 Ly, 56k Ls planet

Evictions:
HIP 6442 Control 54% *54.2%Leigong 28 Ly, 698 strength, −1 attack
HIP 20741 Control 20% *21.8%Indra 24 Ly, 1457 strength
Tougeir Control 18% — Oya 16 Ly, ~10.5k strength

Clean-up:
Col 285 Sector JW-M c7-10 Alert 60% — Hadad 17 Ly, empty
Cephei Sector FB-X b1-1 Alert 54% *54.2%Oya 20 Ly, empty
Pegasi Sector OI-S b4-1 Alert 50% — Raijin 26 Ly, empty
Pegasi Sector FW-W d1-110 Alert 44% — Raijin 25 Ly, empty
Cephei Sector ZE-A c8 Alert 38% — Oya 20 Ly, empty
Pegasi Sector QE-N a8-2 Control 24% *24.3%Raijin 26 Ly, empty, 326 strength


Unfortunately Tougeir is a bit too steep for INIV to commit time this week, at least not with update 16 approaching and without a larger joint effort over the next two days. It is still a great choice if cleared, for it has no supporting systems and all it does is attack Lahua and Muchihiks.

Hopefully it is well enough to guard several other inhabited systems, insofar as it should help the very many Commanders who are stopping all of those Alerts. Of course, over the last month all of the empty system Alerts have also been stopped; unfortunately those can be reduced only if a Maelstrom is being collapsed, although ahead of some tougher cases approaching I would note that it should be quite fine to leave a few if needed.
 
Victories in Namayu, Pegasi Sectors UK-L a9-0, OI-S b4-1 and FW-W d1-110, Cephei Sectors FB-X b1-1, ZE-A c8 and DQ-Y b1, Balak, Gliese 9035, HIPs 6442 and 37520, and Col 285 Sectors RS-H b11-6 and VY-Q c5-19! M. Leigong loses its last attack, and Laumas is guarded in advance—either of being brought into attack focus this week or attacked directly next week, depending on how the update fares tomorrow.

Speaking of which, remember that anything could change tomorrow in a way which disrupts how things work at the moment! The Alerts below are projected to finish ordinarily, but one may consider focus on the top few just in case of any problems afterwards. Remember also to keep a copy of your controls!

Alerts at 07:40 31st July 3309:
Hez Ur Alert 92% *92.7%Cocijo 22 Ly, 446 Ls starport, 236 Ls outpost
Bi Dhorora Alert 72% *72.9%Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet
HIP 19757 Alert 66% *67.4%Indra 25 Ly, 2255 Ls planet
HIP 20948 Alert 60% *61.3%Indra 24 Ly, 56k Ls planet
Jawul Alert 42% *43.3%Raijin 27 Ly, 3045 Ls starport, 3028 Ls outpost
65 Kappa Tauri Alert 32% *32.2%Indra 25 Ly, 71k Ls starport, 72k Ls planet

Evictions:
HIP 20741 Control 24% *24.1%Indra 24 Ly, 1414 strength
Tougeir Control 20% — Oya 16 Ly, ~10.2k strength

Clean-up:
Col 285 Sector JW-M c7-10 Alert 98% *98.4%Hadad 17 Ly, empty
HIP 5629 Control 58% — Leigong 41 Ly, empty, 129 strength
Pegasi Sector QE-N a8-2 Control 44% — Raijin 26 Ly, empty, 241 strength
Pegasi Sector NY-O a7-1 Control 22% — Raijin 22 Ly, empty, 650 strength
 
Victories in Hez Ur, Pegasi Sectors NY-O a7-1, NY-O a7-2 and QE-N a8-2, and Hyades Sector GB-N b7-4! Well done to those keeping M. Raijin on the decline; those evictions also contribute in advance for guarding some systems such as Kissi and Koko Oh, which very much is what I would do before collapsing it.

The plan here is to shrink M. Cocijo a little more, then visit M. Indra again to adopt HIP 20741 and perhaps cause a few more future targeting problems if we can! An extra harvest delivery withheld for update 16 is also possible, although it will be "late" by a few hours, minding also that the means may also change.

Alerts at 18:30 31st July 3309, update 16 caution:
Bi Dhorora Alert 80% *80.8%Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet
HIP 20948 Alert 72% *73.5%Indra 24 Ly, 56k Ls planet
HIP 19757 Alert 70% *71.6%Indra 25 Ly, 2256 Ls planet
Wanmi Alert 64% *64.8%Raijin 26 Ly, 951 Ls outpost, 957 Ls planet
Jawul Alert 56% — Raijin 27 Ly, 3045 Ls starport, 3028 Ls outpost, 3063 Ls planet
65 Kappa Tauri Alert 36% *36.4%Indra 25 Ly, 71k Ls starport, 72k Ls planet

Evictions:
HIP 20741 Control 26% *27.5%Indra 24 Ly, 1351 strength, warranted by INIV
Tougeir Control 20% *21.5%Oya 16 Ly, ~10.0k strength

Clean-up:
Col 285 Sector JW-M c7-10 Alert 98% *98.5%Hadad 17 Ly, empty
HIP 5629 Control 58% *59.8%Leigong 41 Ly, empty, 123 strength
 
Victories in HIPs 20741, 19757 and 5629, 57 h Tauri, Col 285 Sectors ZE-P c6-6, US-H b11-4, YY-F b12-3 and JW-M c7-10, Trianguli Sector EQ-Y b3 and Hyades Sectors PN-T c3-23 and QN-T c3-4! That guards Gandje, intentionally or otherwise, although I imagine it well enough for BLOP either way.

Normally all of the Alerts below (also all which remain) would project completion, but using a reduced length of Tuesday to account for a smooth update 16 leaves Col 285 Sector UD-G b12-2 around 30% short. 65 Kappa Tauri ought to be fine if everything remains intact this evening, otherwise it becomes a risky borderline case.

Alerts at 06:50 1st August 3309:
Jawul Alert 96% *96.7%Raijin 27 Ly, 3045 Ls starport, 3028 Ls outpost, 3063 Ls planet
HIP 20948 Alert 90% *90.2%Indra 24 Ly, 56k Ls planet
Bi Dhorora Alert 88% *89%Hadad 18 Ly, 2734 Ls outpost, 1857 Ls planet
Wanmi Alert 80% *81.4%Raijin 26 Ly, 951 Ls outpost, 957 Ls planet
65 Kappa Tauri Alert 54% *55.5%Indra 25 Ly, 71k Ls starport, 72k Ls planet
Trailing:

Col 285 Sector UD-G b12-2 Alert 10% *11.1%Cocijo 26 Ly, 2174 Ls planet

Evictions:
Tougeir Control 28% — Oya 16 Ly
Omumba Control 12% *13.3%Hadad 14 Ly
 
Do you have a reasonably accurate estimate for Cephei Sector BV-Y b2, unpopulated control at 15.98888774 ly from Oya? The most recent graph that I've seen puts it at around 2720 samples. I'm going to clear it and then see if U16 has made any changes.
 
Do you have a reasonably accurate estimate for Cephei Sector BV-Y b2, unpopulated control at 15.98888774 ly from Oya? The most recent graph that I've seen puts it at around 2720 samples. I'm going to clear it and then see if U16 has made any changes.
2720 seems about right for an unpopulated system at that distance. I'd advise making a measurement delivery first though, lest you do all the work to clear it and only then find out something has changed!
 
That guards Gandje, intentionally or otherwise, although I imagine it well enough for BLOP either way.
Intentional, just in case.
If nothing changed, we can push to further systems.
If something did, it's one less to worry about in the short term, and an uninhabited obstruction in the longer term.

Partly curious to see if we can reserve more than 2b for a buy order now, given the 10,000% thing - would be nice to pay people a decent amount for the effort... though i might need to top up my carrier balance before that.
 
Yep. Thought that i'd drop off 272 after the tick and see how much progress that brings.

Thank you most kindly if you do make a measurement! If it helps to know, we have also 404 units hidden somewhere on V's carrier for a system which needed 308, with a plan to deliver 309 initially. That will not be until a few hours after update 16, though!

Both measurements will be lovely for a quick indication across two very different distance segments.


Partly curious to see if we can reserve more than 2b for a buy order now, given the 10,000% thing - would be nice to pay people a decent amount for the effort... though i might need to top up my carrier balance before that.

It was already quite generous with over 200k per unit! Then again, with wording from update 16:
The decision was made to do this in consideration that some things are rare but have a relatively low price; this means that Commanders will now be able to sell them at a price that is worthwhile for the effort they went to, to acquire them.
I wonder curiously which items were the consideration, if not Research samples...
 
Back
Top Bottom