Thargoid invasion - Next target systems?

With a day to spare—that is absolutely brilliant dedication, and it comes at a such critical time where we need as few distractions from M. Taranis as possible next week, least of all anything proceeding to Invasion. Reducing your Alert list permanently is something I have wanted for a while, and I think we have everything coming together now to do exactly that!
It certainly has been very productive to starve the Thargoids of territory from both direction, with us clearing Alerts while others cleared Controls, and now the respective operations are starting to feed into each other which was my hope as well.
If next week yields a Community Goal to unlock all the classes of double-engineered Frame Shift Drive, somebody is watching and meddling with the plans purposefully.
Or if they give us class 5 and class 6 corrosive resistant cargo racks.
 
If next week yields a Community Goal to unlock all the classes of double-engineered Frame Shift Drive, somebody is watching and meddling with the plans purposefully.
Or a distraction relating to the Titan survivors, whichever form that might take. But as it seems there’s a two week buffer to get this plan done, I think even with a CG(and providing no further unannounced/behind-the-scenes difficulty adjustments), it should be fine to complete. As long as it gets to a 66% completion or so for that first week, at least, if just to be sure.

(I’m sure I’ll see maths about the required numbers or projected progress thrown around. Consider that an invitation… or not.)
 
Sure, here's the possible cases, assuming symmetric progress each week.

>100%: simply done in one week
>85%: first week possibly takes out everything but the spires, second week finishes it regardless
>66%: first week softens things up, second week finishes it off
>60%: first week softens things up, second week does enough to allow some non-spire systems to be finished with the existing planned sampling runs, that cuts Alerts down to the point where a third week can finish things off
>55%: first two weeks soften things up, but the second week needs some additional samples delivering to deal with selected non-spire systems in time to stop there being too many Alerts in week three. Then things can be finished off. Alternatively, the plan adapts to take out everything but Swahku, its spire, and its neighbouring uninhabited, and then the spire is allowed to cool off slightly to get it back into sync with Swahku for another attempt later.
>50%: The plan starts to fall apart - the aim probably has to change to grabbing additional samples to finish off the Hupang cluster at the end of week 2, and just settling for Taranis' remaining systems being somewhat contained but needing a longer approach.
<50%: The plan is unviable as-is, but it might be possible to salvage the Hupang cluster attack if this is recognised quickly enough, and either consider a longer siege on the other side or leave it be and look for easier victories elsewhere.
<33%: The plan cannot work even with modifications. Salvaging the Hupang cluster at this stage will be very costly, though possibly still worth the price.

The 50-66% range is the one where even relatively small changes in progress can have really big implications.
 
I know Aleksandra's version is literally......
100%: Dead titan makes great promotion in all the 1 year news
<100%: See you in HIP 8033

Great stuff all round this week though!
I'll send the Truckers another update to hype the Taranis last stand on their show tomorrow :D
 
I would like to think that discovering what becomes of an isolated Titan is worth very much a steady approach if that is what it requires! I promise I will repeat that to myself as often as needed to manage any dangerously high levels of excitement and intense curiosity which may compromise the operation.

As a related memory for @Kira Goto, a little chart brought forward in time from February!

progress-png.344941

It was for individual systems just after the weekly reinforcements were introduced in place of losing all progress, so it lacks those newer details which take into account the new 85% non-Matrix limit, provided above quite kindly. It shows how much activity occurs in total for different rates per week, both for Commanders who continue regardless of completion ("exclusive") and for those who stop and move elsewhere ("adaptive").

Right-to-left, one can see the original boundaries there; 100%, 66%, 55%, 50%, 46% and such. The weekly activity needed to capture a system over n weeks is (2 + n)/3n, and those additional cases of reaching 85% ought to match (31 + 20n)/60n.
 
So… if my brain is reading that chart right, there seemed to be more progress spent on the systems at lower percentages?

I’m not sure if that’s the correct interpretation. Annoys me a bit, because I’d like to get it right.
 
So… if my brain is reading that chart right, there seemed to be more progress spent on the systems at lower percentages?
I’m not sure if that’s the correct interpretation. Annoys me a bit, because I’d like to get it right.

Exactly right! Lower weekly activity incurs the 33% Thursday reinforcements, potentially multiple times, such that more total activity is needed for one victory. The activity totals are simply 100% plus one-third per extra week required, although the weekly activity amounts where those increases occur are not so linear, and follow instead those equations earlier.

As an example, consider a 3-week victory; setting n = 3 and using weekly activity (2 + n)/3n, we get 5/9 (~55%). One can verify this with the one-third reinforcement written as 3/9; the first week yields 5/9 reduced to 2/9, then 7/9 reduced to 4/9, then finally 9/9 for a victory.

The way to arrive at such an expression is to give a meaningful name to the number we are trying to find, write a little model for how we know it works, then solve it! Let x be the mystery weekly progress rate and let n be the number of weeks involved, such that the total activity is nx. We need to reach 100% progress of course, but each additional week costs an extra third, so we can write:

nx = 1 + (n − 1)/3

Solving for the weekly progress x is then just a case of dividing it all by n, although we can tidy it up a bit first; write the 1 as 3/3 and combine it with the fraction:

nx = (n − 1 + 3)/3 = (n + 2)/3​

Now divide by n:

x = (n + 2)/3n

Other targets such as 85% can be obtained by changing that original 1 to be 0.85. If it turns out that the reinforcements are actually 33.0% rather than a third, something I admit I never checked, use 0.33 (n − 1). Hopefully those colours help to associate each part of that first expression with each concept at hand, and again at the end for making adjustments!
 
Hm. Well, my incompetent-at-maths brain is only comprehending some of that, but I get the main takeaway from the chart(or at least I think I do). Those who adapt to systems once they see a certain amount of progress or are complete tend to put in less effort per system than those who remain despite said completion, starting at around the 43-46% mark(or at least it becomes a noticeable divergence at that point).

What’s the 100/100 point/marker for though? As in, why’s it there.

… this also reminds me why I usually leave some of the deeper planning to other people and rather chime in with feedback if I believe I can add to it or point out a possible flaw.
 
Just ahead of the end of week 50, that looks to be fifty-three systems—in a sense with HIP 23816 becoming the new strongest eviction with 39318 compared to Montioch with 29892, albeit not quite in the same league of only direct activity being involved.

Speaking of strengths, we had an outlier earlier in the week; Hyades Sector KN-K b8-2 predicted 8476 but measured 8491, a small fraction of a percent short. I have already a little note which suggests that the present 10 Ly junction needs to be around 300 higher based on a much earlier measurement at Pegasi Sector JH-U b3-6 by the good CMDR Carpets, presently at 11851 but may need to be somewhere up to 12136, but either way I will state any changes made!

This does affect a few of the weaker systems remaining for Operation Deleted, where we will not be taking any chances with being short a few units. In that sense, a more general note is that the likes of Hupang, HR 1737 and Swahku lie in regions which are completely untested and could also fall very slightly short, for which the extra time to fix such errors makes it all the more important to get a nice swift M. Taranis periphery completion! HIP 25654 will be its final Matrix system, and please remember that we are not clearing Hyades Sector BV-O b6-2 until the former is at 100%, unlike the others which are clear to deliver at 85%.

Rescue those bio-storage at Hyades Sector FB-N b7-6, and strike well the Spire at HIP 25654 with missions available at Telin!


What’s the 100/100 point/marker for though? As in, why’s it there.

Completeness, of course!
 

Week 51, 16th November 3309​

Report
Thirty-two Alerts repelled at HIPs 21125, 9137 and 7338, Col 285 Sectors EA-Q c5-8, SS-H b11-5, JA-G b11-3, SM-C b13-0, NG-E b12-4, ZE-P c6-15, UN-H b11-3, RM-B b14-2, VS-Z b14-0, WN-Z b14-5, PM-B b14-0, ZE-P c6-16 and KW-M c7-12, Hyadum II, Pegasi Sectors MN-S b4-2, MN-S b4-0, HH-U b3-2 and JH-U b3-8, 71 Tauri, Trianguli Sector CA-A c22, Cephei Sector DQ-Y b1, Aowicha, Arietis Sectors JR-V b2-4 and MX-U c2-18, 79 b Tauri, 86 Rho Tauri, Kurumanit, Luggerates and Chinas!
Nine Control evictions at HR 1737, Hupang, Col 285 Sector SH-B b14-1, Swahku, Hyades Sectors GB-N b7-2, FB-N b7-4, BV-O b6-2 and KN-K b8-0, and Arietis Sector NX-U c2-20.
One Matrix system cleared at HIP 25654.
Three recaptured systems starting Recovery are HR 1737, Hupang and Swahku.
Maelstrom Taranis is depleted!

Targets updated at 06:30 23rd November 3309
97 i Tauri Control 90% *90.1%Indra 21 Ly, 387 strength
Chinas Alert 88% *88.4%Raijin 17 Ly, 1760 Ls outpost, 1208 Ls planet
Lei Hsini Control 84% *85.1%Indra 21 Ly, 587 strength
HIP 22524 Control 72% — Indra 20 Ly, 1281 strength, Peripheral system
Hyades Sector JH-V c2-13 Control 50% — Indra 19 Ly, empty, 826 strength, Peripheral system
Hyades Sector NN-S b4-3 Control 50% — Indra 19 Ly, empty, 767 strength, Peripheral system
Hyades Sector PI-S b4-3 Control 50% — Indra 20 Ly, empty, 640 strength, Peripheral system
Dhang Tzela Control 32% — Thor 19 Ly, 4783 strength, Peripheral system
Col 285 Sector JA-G b11-1 Control 30% — Thor 19 Ly, empty, 1046 strength, Peripheral system
Col 285 Sector QB-E b12-2 Control 30% — Thor 19 Ly, empty, 1045 strength, Peripheral system
Col 285 Sector RW-D b12-3 Control 30% — Thor 18 Ly, empty, 1301 strength, Peripheral system
HIP 19046 Control 30% — Thor 18 Ly, empty, 1260 strength, Peripheral system
Akbakara Control 28% — Oya 18 Ly, 6199 strength, Peripheral system
HIP 8525 Control 26% *26.6%Oya 18 Ly, 6713 strength, Peripheral system
Pegasi Sector NN-S b4-3 Matrix 22% *23.2%Raijin 24 Ly, empty
Iceniguari Control 22% — Raijin 23 Ly, 2103 strength, Peripheral system
Pegasi Sector BQ-Y d71 Control 22% — Raijin 26 Ly, 1199 strength, Peripheral system
Pegasi Sector BQ-Y d93 Control 22% — Raijin 24 Ly, empty, 459 strength, Peripheral system
Pegasi Sector KC-U b3-0 Control 22% — Raijin 27 Ly, empty, 312 strength, Peripheral system
Pegasi Sector KC-U b3-2 Control 22% — Raijin 24 Ly, empty, 470 strength, Peripheral system
Pegasi Sector KC-U b3-3 Control 22% — Raijin 27 Ly, empty, 323 strength, Peripheral system
Pegasi Sector PE-N a8-2 Control 22% — Raijin 23 Ly, empty, 514 strength, Peripheral system
Pegasi Sector TK-L a9-5 Control 22% — Raijin 25 Ly, empty, 398 strength, Peripheral system
Sugalis Control 22% — Raijin 23 Ly, 1929 strength, Peripheral system
Col 285 Sector KM-V d2-109 Control 12% — Cocijo 22 Ly, empty, 736 strength, Peripheral system
HIP 13179 Control 10% *11%Oya 15 Ly, 13.4k strength, Peripheral system
Cephei Sector AF-A c9 Control 10% *10.2%Oya 16 Ly, empty, 2538 strength, Peripheral system
Sambaho Control 8% *8.9%Oya 15 Ly, 16.4k strength, Peripheral system
Daruwach Control 8% — Oya 16 Ly, 12.8k strength, Peripheral system
Col 285 Sector WY-F b12-1 Control 8% — Cocijo 21 Ly, 3776 strength, Peripheral system
Pegasi Sector GW-W d1-115 Control 6% — Raijin 23 Ly, 2774 strength
Col 285 Sector XY-F b12-5 Control 6% — Cocijo 21 Ly, empty, 914 strength, Peripheral system
Col 285 Sector PM-B b14-2 Control 4% — Hadad 19 Ly, empty, 1529 strength, Peripheral system
Col 285 Sector US-Z b14-0 Control 4% — Hadad 18 Ly, empty, 1732 strength, Peripheral system
HIP 38235 Control 4% — Cocijo 21 Ly, 4005 strength, Peripheral system
Col 285 Sector PM-B b14-1 Control 4% — Hadad 19 Ly, empty, 1321 strength, Peripheral system
Col 285 Sector TS-H b11-4 Control 4% — Cocijo 21 Ly, empty, 887 strength, Peripheral system
Col 285 Sector TS-H b11-6 Control 4% — Cocijo 21 Ly, empty, 949 strength, Peripheral system
Col 285 Sector US-H b11-3 Control 4% — Cocijo 21 Ly, empty, 868 strength, Peripheral system
Col 285 Sector XT-Q c5-5 Control 4% — Cocijo 21 Ly, empty, 896 strength, Peripheral system
Vasupari Control 2% *3.6%Hadad 18 Ly, 8576 strength
Col 285 Sector SX-Z b14-0 Matrix 2% *2.8%Hadad 19 Ly, empty
Col 285 Sector VS-Z b14-3 Matrix 2% *2.7%Hadad 24 Ly, empty
HIP 113535 Control 2% *2.6%Raijin 20 Ly, 4248 strength
Col 285 Sector SH-B b14-6 Control 2% — Hadad 20 Ly, empty, 1225 strength, Peripheral system
Col 285 Sector WN-Z b14-1 Control 2% — Hadad 19 Ly, empty, 1510 strength, Peripheral system
HIP 32764 Control 2% — Hadad 20 Ly, empty, 1040 strength, Peripheral system

Notes
Maelstrom Taranis has reached a Final Ten scenario.
Maelstrom Leigong has reached a Final Twenty scenario.
Operation Deleted has been delivered.
The Alert report lists predicted attackers, and the Maelstrom maps show Control system connectivity.

Week 50, 9th November 3309​

Report
Thirty-seven Alerts repelled at Hyades Sector HW-M b7-5, HIPs 4041, 23716, 21475, 20712, 19600, 20397, 22265 and 25679, Col 285 Sectors VN-H b11-0, XT-Q c5-1, XT-Q c5-2, KW-M c7-16, WY-F b12-5, RM-B b14-0, OR-B b14-4, KW-M c7-29, JW-M c7-10, MG-E b12-0, JG-O c6-5, OB-E b12-4 and KM-V d2-69, Pegasi Sectors JH-U b3-9, RE-N a8-0, IH-U b3-8 and LC-U b3-2, Cephei Sectors WO-A b4, AV-Y b2 and BV-Y b2, Arietis Sectors KM-W c1-15, WJ-R b4-3, FG-Y d66, NX-U c2-19 and MM-V b2-1, Njorog, Nibelaako and Gliese 9035.
Ten Control evictions at Hyades Sectors KN-K b8-1, BV-O b6-4, GB-N b7-1, FB-N b7-0, KN-K b8-2 and FX-H a11-0, HIPs 23816 and 22496, and Arietis Sectors FL-X b1-0 and HG-X b1-3.
Six Matrix systems cleared at Hyades Sectors DQ-O b6-0 and ST-Q b5-5, Trianguli Sector BA-A d85, HR 1358, HIP 22350 and Arietis Sector HG-X b1-0.
Two recaptured systems starting Recovery are HIPs 23816 and 22496.
Maelstrom Leigong loses three attacks, and Taranis loses four attacks.
 
Last edited:
The speed of the attack leaves Taranis without much room to place new Alerts for now - but as previously discussed, time is limited before the recaptured systems surrounding Hupang come off cooldown/recovery. Good luck!
Taranis-edges.png
 
Well, first hurdle overcome, and another bit of scientific discovery: periphery effects still work even when a Maelstrom doesn't have enough systems left to have a periphery per se. That was always a risk... Current progress is a bit slower than needed, but Thursday mornings often are quiet.
 
One week completion would be ideal, of course, but mostly relevant to personal accomplishment and to have the feat appear in the monthly war summary. I’m not sure it’d quite make it in if it only occurred by the 30th, but having it done only by then(and visible in the game following the weekly tick) isn’t an issue per se.
 
On the numbers from Dark Session's tests after the last rebalance, those sales alone should shift things about 2-3%.
So if it doesn't ... they clearly don't want this to be too easy.
 
8% for that first day doesn’t look… too terrible, if the weekend provides better progress. It also looks like someone’s doing stuff in Hupang and HR 1737 again, as they’re both ahead by about 2%.
 
I think we can do it this cycle. SNPX will support as good as we can. Our "AX-Friday" will take place in HIP 25654 and I think, at least some commanders will intensify the Titan rescues over the weekend.

On the other hand we would apreciate any assistance to clear our alerts at Oya. If there are not enough forces to clear all alerts, we request an invasion for HIP 7338.
 
Top Bottom