Maelstrom Maps

Here are the current (well, aside from this afternoon's recaptures...) Control maps of each Maelstrom.
- Matrix/Spire systems are shown in red, formerly-inhabited systems dark green, other uninhabited Controls light green
- systems within 15 LY of the Titan get a thicker border, systems within 10 LY a very thick border
- arrows point away from the Titan and connect systems based on the Thargoid's 10 LY attack range.
- position on the map doesn't correspond at all to position in 3-D space, and distances between systems are likewise arbitrary, to focus on the connectivity aspect
- to save a little space, the word "Sector" has been omitted from system names

The 10 LY range of the Thargoid advance means that despite the same rules applying at each Maelstrom, the consequences are very distinct - a use of the geography of space in a way that hasn't really been seen in the series since the original Elite.

The maps themselves can be quite substantial, so I've put them inside the spoiler cuts below.

Previous fights around Taranis have left it quite loosely connected, with lots of disconnected systems, and a very weak bridge via Ixbalan. Its remaining dense cluster on the left has a balance between the relatively weak spire at HW-M b7-4 and the very strong Hupang which would require an extremely coordinated attack to overcome.
Taranis.png

Previous activity has already split Leigong into a couple of disjoint clusters, as well as a few extra loose systems around their own spires. The weakest Maelstrom to begin with, it's now critically dependent on the KN-K b8-3 spire to hold most of it together. At the moment, that one is too close-in to threaten.
Leigong.png

Despite the high system density at Indra, recent recapture work has split it into two separate clusters, with very different characters - the cluster shown on the right is anchored solely by the HG-X b1-0 spire and has no other strong sytsems, whereas the left side would likely be near-invincible even without its multiple spires. There is longer-term potential for a sufficiently large clearance of the right cluster to weaken the outer spires on the left cluster, however.
Indra.png

Oya's two Spire sites are tucked away behind the Titan, but the connectivity of the remaining groups, using other near-Titan controls, will make further progress costly beyond the few remaining outliers.
Oya.png

A large and well-connected single cluster at Cocijo will make significant progress difficult from most directions. Trimming further uninhabited controls uniformly off the fringes is possible, and the isolated WY-F b12-1 is an obvious option for recapture, but the dense inner core around Nyani is one of the strongest of any Maelstrom.
Cocijo.png

Considerable disconnection work has taken place at Thor already, with the most interesting feature being the entirely disconnected Rajuarpai pentagram - a major project to recapture, nevertheless. Outside of that, some well-distributed spires and the extremely strong Leunii-Gluschen pairing will make further shrinking of Thargoid territory very difficult.
Thor.png

Raijin currently combines a large size with strong connectivity and well-distributed anchors in terms of both Spires and Titan-adjacent Controls of other sorts. There is some weakness on the top-left side, with the clusters around Iceniguari, Chakma and Sugalis not having any particularly strong systems, but this is very limited.
Raijin.png

Hadad has already been the target of many recapture attempts, which have left it in the interesting situation of having no inhabited systems on its perimeter, and only two remaining inside it. The spire system at HIP 30439 forms the only bridge between the two halves of Hadad - though not one the Thargoids need to be concerned about losing! - which have quite different characters - the top half is more loosely connected, but has a very strong set of individual systems at its core, whereas the bottom half is much weaker in its individual systems but much more strongly connected.
Hadad.png

I've also made versions which also show the attackable systems from each Control, as that's sometimes interesting but does add a lot of clutter as well. Those bonus images are in this zip file - inhabited targets are shown in a darker grey.
 
I suspect this is answered elsewhere, but what's the skinny with clusters being harder? Is more effort required based on systems in range? Or do clusters act like one larger pool of effort, with the effect spreading over other systems, and so you can't simply target one system, without that effect being somewhat distributed over a large amount of systems?
 
Indeed; just having noticed them lurking here, thank you for these! I have a lot of interest in seeing the more vulnerable sections, even if update 17 has changed priorities a bit and placed periphery completion ahead of targeted campaigns—although that also will be creating many new vulnerabilities. Ahead of either of those always will be threat cancellation via target lists, of course!


I suspect this is answered elsewhere, but what's the skinny with clusters being harder? Is more effort required based on systems in range? Or do clusters act like one larger pool of effort, with the effect spreading over other systems, and so you can't simply target one system, without that effect being somewhat distributed over a large amount of systems?

The strength is still based only on inhabitation and Maelstrom distance, and nothing is distributed that way; it is simply that systems close enough to form a complete graph need clearing all together¹ to avoid them restoring each other. The M. Thor case has some good examples:

Rajuarpai.png
Leunii.png

Those are two cases of the complete* graph K₅, the former being interestingly disconnected from other systems. Rajuarpai (46194) is over 50% stronger than the strongest Control system cleared thus far, Montioch (29892) at M. Hadad; without any help that would require quite some stockpiling, followed with weekly attention dedicated to clearing the others one by one.

The latter simply is unassailable without reaching it eventually via shrinking the M. Thor periphery so that Titan rescues² can contribute by percentage³, and again it all has to clear together to avoid a resurgence. On the same strength scale Gluschen is 81733, Leunii is 106584, and even the empty Col 285 Sector IG-O c6-15 is 103096 given that the strengths converge as they approach 5 Ly.

1. Within their one-month respite interval, of course!
2. Also Spire activity, if Commanders are able to leave one around...
3. Up to an 85% limit that way.


*Additional: Or "almost-complete", something I discussed here earlier, and where I just noticed that Gluschen lacks one link.
 
Last edited:
Indeed; just having noticed them lurking here, thank you for these! I have a lot of interest in seeing the more vulnerable sections, even if update 17 has changed priorities a bit and placed periphery completion ahead of targeted campaigns—although that also will be creating many new vulnerabilities. Ahead of either of those always will be threat cancellation via target lists, of course!




The strength is still based only on inhabitation and Maelstrom distance, and nothing is distributed that way; it is simply that systems close enough to form a complete graph need clearing all together¹ to avoid them restoring each other. The M. Thor case has some good examples:


Those are two cases of the complete* graph K₅, the former being interestingly disconnected from other systems. Rajuarpai (46194) is over 50% stronger than the strongest Control system cleared thus far, Montioch (29892) at M. Hadad; without any help that would require quite some stockpiling, followed with weekly attention dedicated to clearing the others one by one.

The latter simply is unassailable without reaching it eventually via shrinking the M. Thor periphery so that Titan rescues² can contribute by percentage³, and again it all has to clear together to avoid a resurgence. On the same strength scale Gluschen is 81733, Leunii is 106584, and even the empty Col 285 Sector IG-O c6-15 is 103096 given that the strengths converge as they approach 5 Ly.

1. Within their one-month respite interval, of course!
2. Also Spire activity, if Commanders are able to leave one around...
3. Up to an 85% limit that way.


*Additional: Or "almost-complete", something I discussed here earlier, and where I just noticed that Gluschen lacks one link.
Ok... so the issue is really as soon as you poke a hole... the "connected" systems have no real choice but to go for that again, and so you're left with perpetually preventing it from being retaken... and they're high population systems meaning they take lots of effort.
 
It is more simply inhabited versus empty without involving the population number, but yes! For the completely opposite example, consider M. Leigong:

Leigong.png

Not more than a week or so prior to the Matrix systems becoming immovable, the INIV plan was to test whether a Maelstrom system can attack (see Operation Redacted), then simply clear all of that if not. The test was very successful when HIP 8887 failed to attack HIP 9016, and we did clear out an entire group of systems similar to the upper group above, then stopped entirely due to Hyades Sector KN-K b8-3.

If Commanders are able to give us Matrix completions there then we can still clear it all eventually, even if some of those inner systems miss the extra progress for being among the outer ten when it happens. Most systems which form groups of four or more are empty, as are both remaining systems which are within 10 Ly, and no system at all is within 9 Ly!
 
This week's maps are ready.

Biggest changes in terms of connections are at Leigong and Taranis
One of Leigong's clusters now has no spires attached (and the loose ones are all gone too)
Leigong.png

At Taranis, the breakup continues, with a few isolated systems, and a large cluster lacking a Spire - while the map as a whole now fits into a very small image.
Taranis.png
 
This week's maps are ready.

Some noticeable changes at
where the HIP 8033 side is now a single line
Leigong.png
and at
where the cluster around 75 Tauri and HIP 21179 is now disconnected entirely, and HIP 21912 forms the only bridge to another region.
Indra.png
 
Maps for 14 December - some interesting changes at Hadad as its recent recaptures give it a backup route between the two halves which doesn't go through the central spire.

And something slightly different for scale: Meene is the closest system to any Titan that has more than purely local importance, so here are the recaptures that Taranis would need to make to get there:
(Meene's the blue one in the bottom left)
Meene-full.png
At just short of 500 systems this would take about 90 weeks to threaten Meene if all attacks were allowed to go through uncontested. (Despite Taranis' rather diminished current state, this is still considerably closer than any other Maelstrom is to threatening anywhere else of "you'd care about this even if it wasn't your home system" importance)

In theory it's possible to reduce the number of systems they need to capture - if you really hated Ram Tah, for example - by cutting off some of the side branches in the wrong direction ... but in practice the Thargoids will then attempt to repeatedly retake those bottleneck systems, so while it would be possible to get Taranis to Meene in only about 340 systems held, the reduction in number of fresh Alerts Taranis gets to place means that it doesn't really save any time.

So, no need to worry about a few failed defences here or there.
 
May I request a present map for M. Hadad? While I imagine it may not discover any vulnerable districts necessarily, it could be quite nice to compare that possible spatial value against our target list at the moment!

Said list is drawn from those which both can attack at the end of next week and are placed between the first two Spire sites radially, with the extra goal of leaving behind a first periphery which removes both sites together, but I think that ought not come before protruding systems which can be removed feasibly without leaving a cavity to defend.
 
Interesting; thank you! I had Col 285 Sectors KW-M c7-28 and KW-M c7-29 queued next on the east edge there, but indeed some of the north-west Col 285 Sector WN-Z systems also will be soon to misbehave, so some of those can join the list this week.

We will not be preventing the attack against Col 285 Sector GQ-O c6-22 this week, although we will stop it as Alert if needed, which should at least cause quite crippled outward targeting due to those KW-M losses if we do not get around to depleting the list more fully.
 
Top Bottom