Thargoid invasion - Next target systems?

The re-controlled spire sites around Indra are active, but the progress bar on the systems doesn't have the "spire site present" status, but instead uses the regular control status.

Back to 8 alerts. If it's based on the previous week's alerts, the threshold is somewhere between 41 and 44 alerts.
 
So 8 alerts, but Taranis also went for one of the uninhabited systems near it? scratches head in confusion

(At least overwatch says so and I have little reason to doubt the accuracy of its data.)
 
I suppose that opens a few questions! Relevant more for others than for me, and without any particular rush to discover it:
  • Whether actions at such a site give peripheral progress, system progress, both or neither.
  • Whether non-Spire actions give system progress.
  • Whether Rescue megaship missions are present.
Meanwhile, T. Taranis continues misbehaving while it has only one Control system, and indeed T. Leigong continues sleeping.


So 8 alerts, but Taranis also went for one of the uninhabited systems near it? scratches head in confusion

It can reach no other inhabited systems! With Invasions at Swahku and HR 1737, its options were only Hyades Sectors GB-N b7-2 and FB-N b7-4, whereas Hupang chose the sole inhabited system HIP 23816 from nine others including some closer and some farther.
 

Week 62, 1st February 3310​

Report
Two Invasions defended at Nu Guang and HIP 22496.
The defended Invasion systems will start Recovery.

Targets updated at 06:30 8th February 3310
HIP 21918 Invasion 74% — Indra 22 Ly, 1 port, 769 Ls outpost attack, 293 Ls outpost damage
Aowicha Invasion 72% *73.1%Oya 24 Ly, 3 ports, 1765 Ls 0.19g planet attack
Vistnero Invasion 56% *56.1%Raijin 21 Ly, 2 ports, 147 Ls 0.12g planet attack, 521 Ls outpost damage
Nibelaako Alert 42% *42.8%Raijin 22 Ly, 519 Ls starport, 519 Ls planet
HR 1358 Alert 40% *40.6%Indra 22 Ly, matrix
HIP 20616 Alert 34% — Indra 22 Ly, 176k Ls planet
HIP 20890 Alert 34% — Indra 22 Ly, 1609 Ls outpost, 6876 Ls planet
Hez Ur Invasion 30% *31%Cocijo 22 Ly, 1 port, 446 Ls starport attack, 236 Ls outpost damage
Hyades Sector ST-Q b5-5 Matrix 30% *30.2%Indra 22 Ly
HIP 22350 Alert 28% *29.5%Indra 22 Ly, matrix
Arietis Sector JR-V b2-1 Alert 28% *29.4%Indra 22 Ly
Arietis Sector LM-V b2-5 Control 28% *29.2%Indra 22 Ly, 965 strength
92 Sigma-2 Tauri Control 28% — Indra 22 Ly, 1044 strength
97 i Tauri Invasion 22% *23.4%Indra 21 Ly, 2 ports, 1485 Ls planet attack
HIP 116360 Invasion 16% *17.4%Raijin 21 Ly, 3 ports, 462 Ls 0.2g planet attack, 861 Ls 0.3g planet damage
Chinas Invasion 16% *17.3%Raijin 17 Ly, 4 ports, 1199 Ls 0.13g planet attack
Khwal Invasion 16% *17%Cocijo 22 Ly, 2 ports, 3228 Ls 0.2g planet attack, 89 Ls 0.15g planet damage
Yan Zangata Invasion 16% *16.3%Hadad 22 Ly, 1 port, 70 Ls outpost attack, 98 Ls outpost damage
HIP 7338 Invasion 16% — Oya 19 Ly, 2 ports, 1660 Ls 0.2g planet attack, 986 Ls 0.15g planet damage
Arietis Sector KM-W d1-94 Invasion 10% *11.3%Leigong 17 Ly, 1 port, 898 Ls planet attack, 620 Ls planet damage
HIP 18075 Invasion 8% *9.3%Thor 21 Ly, 3 ports, 2826 Ls planet attack
Pegasi Sector UK-L a9-0 Alert 8% *8.3%Raijin 23 Ly
HIP 29596 Alert 8% — Hadad 18 Ly, 2098 Ls starport
Tagin Alert 8% — Raijin 23 Ly, 636 Ls outpost
HIP 21261 Invasion 6% *6.8%Indra 20 Ly, 1 port, 18 Ls outpost attack, 285 Ls outpost damage
HIP 112595 Alert 6% *6.6%Raijin 24 Ly
HIP 20577 Alert 4% *5.1%Indra 18 Ly, 123 Ls outpost, 169 Ls planet
Pegasi Sector KC-U b3-2 Control 4% *4.8%Raijin 24 Ly, 793 strength
Pegasi Sector BQ-Y d93 Control 4% *4.7%Raijin 24 Ly, 762 strength
Ixbaksha Alert 4% *4.5%Raijin 23 Ly
Col 285 Sector JW-M c7-11 Alert 4% *4.5%Hadad 23 Ly
Canaharvas Alert 4% *4.4%Cocijo 24 Ly, 964 Ls outpost
HR 2204 Invasion 4% *4.4%Hadad 15 Ly, 2 ports, 4277 Ls planet attack
Pegasi Sector PI-S b4-6 Alert 4% *4.2%Raijin 24 Ly
HIP 20679 Control 4% — Indra 18 Ly, 8890 strength
Pegasi Sector NN-S b4-3 Matrix 4% — Raijin 24 Ly
Col 285 Sector EA-Q c5-8 Alert 4% — Thor 23 Ly
Pegasi Sector BQ-Y d71 Control 4% — Raijin 26 Ly, 1475 strength
Pegasi Sector GW-W d1-115 Control 4% — Raijin 23 Ly, 2833 strength
Pegasi Sector PE-N a8-2 Control 4% — Raijin 23 Ly, 931 strength
Sugalis Control 4% — Raijin 23 Ly, 2375 strength
Col 285 Sector VS-Z b14-3 Matrix 2% *3.7%Hadad 24 Ly
HIP 19198 Alert 2% *3.6%Thor 17 Ly, 1454 Ls starport
Balak Invasion 2% *3.1%Raijin 23 Ly, 3 ports, pending attack report
Col 285 Sector VS-Z b14-6 Alert 2% *2.9%Hadad 24 Ly
HIP 113535 Control 2% *2.7%Raijin 20 Ly, 4245 strength
70 Tauri Alert 2% *2.4%Indra 21 Ly, 2003 Ls outpost
Vucumatha Invasion 2% *2.3%Cocijo 23 Ly, 2 ports, 13k Ls outpost attack
Iduni Invasion 2% *2.3%Raijin 22 Ly, 0 ports, 423 Ls outpost damage
Omumba Invasion 2% *2.2%Hadad 14 Ly, 2 ports, 1232 Ls planet attack, 41 Ls outpost damage
Scythia Control 2% — Indra 20 Ly, 4400 strength
HIP 22524 Control 2% — Indra 20 Ly, 4483 strength
HIP 11111 Alert 2% — Oya 24 Ly, 2567 Ls outpost
Col 285 Sector OG-E b12-1 Alert 2% — Thor 23 Ly, matrix
Col 285 Sector JG-O c6-5 Control 2% — Thor 25 Ly, 538 strength
Col 285 Sector KB-O c6-3 Control 2% — Thor 23 Ly, 1188 strength
Col 285 Sector KM-V d2-69 Alert 2% — Cocijo 24 Ly
Col 285 Sector KW-M c7-17 Alert 2% — Hadad 24 Ly
Col 285 Sector NG-E b12-1 Alert 2% — Thor 23 Ly
Col 285 Sector NG-E b12-4 Control 2% — Thor 22 Ly, 1314 strength
Col 285 Sector NR-B b14-1 Alert 2% — Hadad 24 Ly
Col 285 Sector OC-V d2-79 Alert 2% — Thor 21 Ly
Col 285 Sector OC-V d2-96 Control 2% — Thor 22 Ly, 1377 strength
Col 285 Sector OR-B b14-9 Alert 2% — Hadad 25 Ly
Col 285 Sector RM-B b14-1 Alert 2% — Hadad 24 Ly
Col 285 Sector RM-B b14-7 Alert 2% — Hadad 26 Ly
Col 285 Sector SM-C b13-0 Control 2% — Thor 22 Ly, 1444 strength
Col 285 Sector SS-H b11-3 Control 2% — Cocijo 23 Ly, 1027 strength
Col 285 Sector SX-Z b14-1 Control 2% — Hadad 23 Ly, 948 strength
Col 285 Sector TS-H b11-2 Alert 2% — Cocijo 23 Ly
Col 285 Sector UH-C b13-1 Alert 2% — Thor 22 Ly
Col 285 Sector US-H b11-2 Alert 2% — Cocijo 24 Ly
Col 285 Sector VN-H b11-0 Control 2% — Cocijo 25 Ly
Col 285 Sector WN-Z b14-3 Control 2% — Hadad 23 Ly, 1104 strength
Col 285 Sector XY-F b12-6 Alert 2% — Cocijo 23 Ly
Col 285 Sector ZE-P c6-13 Alert 2% — Cocijo 23 Ly
HIP 36901 Alert 2% — Cocijo 23 Ly
Pegasi Sector QE-N a8-5 Alert 2% — Raijin 23 Ly
Vocovii Alert 2% — Cocijo 24 Ly, 106 Ls planet

Notes
The Alert report lists predicted attackers.

Week 61, 25th January 3310​

Report
Two Alerts repelled at Gliese 9035 and HIP 2422.
Four Invasions defended at HIPs 20899, 20492 and 20491, and Holvandalla.
The defended Invasion systems will start Recovery.
 
Last edited:
It can reach no other inhabited systems! With Invasions at Swahku and HR 1737, its options were only Hyades Sectors GB-N b7-2 and FB-N b7-4, whereas Hupang chose the sole inhabited system HIP 23816 from nine others including some closer and some farther.
Not so confused about its chosen attack, as much as that it kind of throws off my idea that a Titan not attacking gives an additional alert to the others.

That, clearly, doesn’t seem to be the case here unless the new default is now seven alerts per Titan.
 
Whether a Titan attempts to attack seems to be unrelated to the number of Alerts, and instead depend very much only on its number of Control systems being below three!

If there is an actual connection to be discovered rather than Frontier simply is changing it weekly, I imagine it would use the number of Alerts placed earlier. At present it would be just as well to suppose it is chosen randomly, although with 51 now it could begin forming a pattern if it were to lower next week, given that we have had a six-per-Titan week from 44 earlier.

Additional: Ultimately Frontier wants some intended number of Alerts weekly, so it would make little sense that an automatic adjustment is beholden to the Titan ability to find a target—instead it would be a more general measure against containment attempts, short of achieving eight containments simultaneously of course!

Additional additional: Unfortunately the latter seems like an expensive way to make Frontier increase the attack range.
 
Last edited:
Leigong was able to place alerts too, so that suggests anything around a two-pass structure for deciding alert counts is probably wrong.

If it's based it on the previous week's Alert count to decide whether to increase, decrease or hold the Alert budget then its "hold" region seems to have a maximum envelope 39-43, which is narrow enough to likely lead to oscillations.

Or it could still be under manual control, of course.
 
Only thing I am at this point certain on is that Frontier clearly wants things to ramp back up before they introduce the ability to attack Titans directly.

And while it might/likely will have a strong effect on the control sphere(and other affected systems), I’m not sure how relevant those controls would be whenever Salvation inside his Guardian AI doohickey shows up. Unless that weapon is not as effective as hoped for. The war would likely take a different form if it did continue.
 
Only thing I am at this point certain on is that Frontier clearly wants things to ramp back up before they introduce the ability to attack Titans directly.

And while it might/likely will have a strong effect on the control sphere(and other affected systems), I’m not sure how relevant those controls would be whenever Salvation inside his Guardian AI doohickey shows up. Unless that weapon is not as effective as hoped for. The war would likely take a different form if it did continue.
Surely they do, in as otherwise they would not call U18 "end of thargoid war" or "kill the titans".

Its safe to assume that once titans are gone, it certainly means no new invasions/alerts for each of sphere of influence, so what would be next is just taking back systems out thier control (to get rid of any remain thargoids craft) but also long as any remain spire systems are not shut down... in end there are "portals" there as well, so lore-wise any remain thargoids are kind of be able to hold out a bit (with titans gone), until these are offline, thats it.

Because, it would be wierd, if by means of titans gone, suddenly all neighbouring thargoids would be gone by space magic... its more likely to we would be needed to still clean up any "remains".
 
Last edited:
Definitely I can imagine remaining systems dropping to minimum Strength if the corresponding Titan were to cease functioning; I can imagine also new Titans arriving occasionally after the era of the original eight, perhaps to coincide with moments when the Thargoids produce a new vessel or attack method. It would be sensible that these eight are everything they had at the time, yet the Titan arrival sequence was quite nice and surely is something new Commanders may enjoy seeing!

I presume speculation remains regarding Cols 70 and 121, where it could be quite interesting if some of those were indeed Thargoid systems.
 
I suppose that opens a few questions! Relevant more for others than for me, and without any particular rush to discover it:
  • Whether actions at such a site give peripheral progress, system progress, both or neither.
  • Whether non-Spire actions give system progress.
  • Whether Rescue megaship missions are present.
I stopped by Arietis Sector HG-X b1-0. It does have a tiny bit of progress, but I went and blew up an Orthrus at the spire site and the progress didn't change.
 
in as otherwise they would not call U18 "end of thargoid war" or "kill the titans".
Did they? I heard it differently
https://youtube.com/clip/UgkxWomMn2Y-GgZGlvBLTqi-Q0HyJxqghusq?si=AEktvcWnRHoI0c6T
Update 18 will allow commanders to finally take the fight to the beheomeths that are the Titans

This could mean any of
  • We can damage the Titan and reduce its attacks for that week, but with no other effect.
  • We can damage them and disable their attacks, enabling us to hold ground we wouldn't otherwise.
  • We can damage them and gain significant ground, akin to cutting supply routes.
  • We can damage them, requiring them to divert resources from expansion for repair, without which they stay damaged
  • We can damage them and get them into a state / use their resources for .... something new (Update 20?)
  • We can "kill the titans"
Take your pick...we are alll just speculating.
... I can't see us "winning" until we've traced them back to where they came from, who knows... maybe a damaged Titan unlocks a yellow goo jump portal that leads to the middle of the permit locked Cone Sector. Nah... surely not

1706830865923.png
 

Week 63, 8th February 3310​

Report
Three Alerts repelled at Obamumbo, HIP 20485 and Yemaki.
Five Invasions defended at Aowicha, Vistnero, HIPs 21918 and 20890, and Balak.
The defended Invasion systems will start Recovery.

Targets updated at 06:30 15th February 3310
HIP 20527 Alert 78% *78.6%Indra 23 Ly, 595 Ls starport, 834 Ls outpost, 4805 Ls planet
HIP 20616 Invasion 58% *58.2%Indra 22 Ly, 4 ports, 176k Ls 0.5g planet attack
78 Theta-2 Tauri Alert 58% — Indra 25 Ly
Arietis Sector LM-V b2-5 Control 52% — Indra 22 Ly, 654 strength
Isla Alert 50% *51.9%Raijin 24 Ly, 888 Ls starport, 1649 Ls outpost, 888 Ls planet
HIP 11111 Invasion 44% *44.5%Oya 24 Ly, 2 ports, 2474 Ls 0.11g planet attack
Hyades Sector TO-Q b5-2 Alert 44% — Indra 23 Ly
HIP 29596 Invasion 42% *42.3%Hadad 18 Ly, 7 ports, 1548 Ls 0.14g planet + 3015 Ls outpost attack
Hyades Sector QI-S b4-2 Alert 42% — Indra 25 Ly
Arietis Sector JR-V b2-1 Control 42% — Indra 22 Ly, 796 strength
Arietis Sector HG-X b1-3 Alert 42% — Indra 22 Ly
Hyades Sector PI-S b4-2 Alert 42% — Indra 22 Ly
97 i Tauri Invasion 36% *36.6%Indra 21 Ly, 1 port, 1485 Ls starport attack, 1485 Ls planet damage
Chinas Invasion 24% *25.7%Raijin 17 Ly, 3 ports, 1208 Ls 0.12g planet attack, 1199 Ls 0.13g planet damage
Pegasi Sector NY-O a7-5 Alert 12% — Raijin 24 Ly
Col 285 Sector OB-E b12-4 Control 12% — Thor 21 Ly, 1492 strength
Minawara Alert 8% *8.7%Oya 23 Ly, 412 Ls outpost, 412 Ls planet
Ixbaksha Invasion 8% *8.5%Raijin 23 Ly, 2 ports, 196 Ls 0.18g planet attack
Arietis Sector KM-W d1-94 Invasion 8% *8.2%Leigong 17 Ly, 0 ports, 898 Ls planet damage
HIP 18075 Invasion 8% *8.2%Thor 21 Ly, 2 ports, 2930 Ls planet attack, 2826 Ls planet damage
Pegasi Sector MN-S b4-5 Control 8% — Raijin 21 Ly, 3581 strength
HIP 20577 Invasion 6% *7.5%Indra 18 Ly, 3 ports, 169 Ls 1.4g planet attack
Nibelaako Invasion 6% *7.1%Raijin 22 Ly, 6 ports, 16k Ls outpost attack
Vogulu Alert 6% *6.6%Hadad 21 Ly, 336 Ls starport
Col 285 Sector KM-V d2-69 Invasion 6% *6.5%Cocijo 24 Ly, 1 port, 451 Ls planet attack
Canaharvas Invasion 6% *6.5%Cocijo 24 Ly, 1 port, 964 Ls outpost attack
Tagin Invasion 6% *6.2%Raijin 23 Ly, 1 port, 636 Ls outpost attack
HIP 7338 Invasion 6% — Oya 19 Ly, 1 port, 674 Ls outpost attack, 1660 Ls 0.2g planet damage
Hez Ur Invasion 6% — Cocijo 22 Ly, 0 ports, 446 Ls starport damage
Pegasi Sector YQ-J a10-0 Alert 6% — Raijin 24 Ly
HIP 112219 Alert 4% *4.8%Raijin 24 Ly
HIP 113535 Control 4% *4.7%Raijin 20 Ly, 4159 strength
Bormuninus Alert 4% *4.1%Raijin 24 Ly, 45 Ls outpost
HIP 116542 Alert 4% — Raijin 24 Ly
Vocovii Invasion 4% — Cocijo 24 Ly, 3 ports, 106 Ls planet attack
Pegasi Sector NN-S b4-3 Matrix 4% — Raijin 24 Ly
HIP 116360 Invasion 4% — Raijin 21 Ly, 2 ports, 1211 Ls outpost attack, 462 Ls 0.2g planet damage
Muruidooges Alert 4% — Hadad 18 Ly, 1018 Ls starport
Pegasi Sector BQ-Y d71 Control 4% — Raijin 26 Ly, 1475 strength
Pegasi Sector BQ-Y d93 Control 4% — Raijin 24 Ly, 768 strength
Pegasi Sector GW-W d1-115 Control 4% — Raijin 23 Ly, 2833 strength
Pegasi Sector KC-U b3-2 Control 4% — Raijin 24 Ly, 800 strength
70 Tauri Invasion 2% *3.6%Indra 21 Ly, 2 ports, 3010 Ls outpost attack
Pegasi Sector EB-W b2-2 Alert 2% *3.2%Raijin 24 Ly
HIP 19198 Invasion 2% *3.2%Thor 17 Ly, 2 ports, 1004 Ls 0.11g planet attack
Picenile Alert 2% *3%Cocijo 25 Ly, 395k Ls planet
Col 285 Sector YT-F b12-1 Alert 2% *2.8%Cocijo 24 Ly
Khwal Invasion 2% *2.7%Cocijo 22 Ly, 1 port, 67 Ls outpost attack, 3228 Ls 0.2g planet damage
Yan Zangata Invasion 2% *2.6%Hadad 22 Ly, 0 ports, 70 Ls outpost damage
Kurumanit Control 2% *2.4%Cocijo 20 Ly, 4376 strength
HIP 23816 Invasion 2% *2.4%Taranis 12 Ly, 5 ports, 475 Ls outpost + 3570 Ls planet attack
Col 285 Sector SS-H b11-2 Alert 2% — Cocijo 24 Ly
HIP 21261 Invasion 2% — Indra 20 Ly, 0 ports, 18 Ls outpost damage
Col 285 Sector VN-H b11-0 Control 2% — Cocijo 25 Ly
Col 285 Sector AU-F b12-2 Alert 2% — Cocijo 24 Ly
Col 285 Sector OB-D b13-1 Alert 2% — Hadad 24 Ly
Col 285 Sector TS-H b11-1 Alert 2% — Cocijo 24 Ly
Col 285 Sector UN-H b11-6 Alert 2% — Cocijo 24 Ly
Col 285 Sector US-H b11-2 Control 2% — Cocijo 24 Ly, 757 strength
Col 285 Sector VN-H b11-5 Alert 2% — Cocijo 24 Ly
Col 285 Sector XT-Q c5-2 Alert 2% — Cocijo 25 Ly

Notes
The Alert report lists predicted attackers.

Week 62, 1st February 3310​

Report
Two Invasions defended at Nu Guang and HIP 22496.
The defended Invasion systems will start Recovery.
 
Last edited:
Just 2 invasions defended. Well, Nu Guang was a <20ly system, but still, just 2 systems is really late-2022 vibes.
Wonder if that is because the majority of players are really fed up at the moment and are holding out for the next step by FDev?
 
Just 2 invasions defended. Well, Nu Guang was a <20ly system, but still, just 2 systems is really late-2022 vibes.
Wonder if that is because the majority of players are really fed up at the moment and are holding out for the next step by FDev?
A lot of effort is also split between the very numerous invasions. Even discounting peripheral progress at Indra from spire activities(more on that in a moment), people are just scattered a little all over the different Titans. Less toward Cocijo, Thor and Hadad that last week though, it seems.

(PDES was also busy with HIP 21918 for the entire week, or so it looked, which probably didn’t help matters.)

And I have a bit of a thought regarding spires (that may be difficult to prove), for some time now… what’s the possibility of their difficulty increasing as more of them are cleared out in a ‘Consolidation of defenses’ style move?
 
A lot of effort is also split between the very numerous invasions.
Light addendum to that idea - I am partly suspecting or thinking about a difficulty increase for invasions as well after the last few changes to alerts and controls. But that’s hardly something I could verify very easily… especially since I’ve not been gathering any data and only occasionally looked at inara and the overwatch statistics(which are undoubtedly not 100% accurate as not every player uploads data to either site) for relative differences from one system to another.
 
Wonder if that is because the majority of players are really fed up at the moment and are holding out for the next step by FDev?

Unconcerned would be a good description here—otherwise indeed, very much so awaiting the fixed conclusion schedule! Short of a definitely neutralised Titan with ideally Tanner declaring it stopped this time, there is not the support for clean-up.

Despite lacking various information at present, I imagine the which-Titan-first question will be upcoming! If there turns out to be no worthwhile strategic consideration then I imagine T. Taranis, Oya or Indra will be appropriate for being the focus. If a peripheral progress mechanism is needed and nothing new is introduced then that gives T. Hadad an immediate promotion, albeit with a steep Alert wall—unless disabling a Titan also stops Alerts or changes the definition of peripheral. If a disabled Titan lowers the strengths or if an alternative percentage progress becomes available, that puts the popular choices back to the top of course!

I am interested also to see the mass-lock factor of the upcoming Python 2; the normal Python already is borderline heavy, so I wonder whether one of its tricks will be to beat a Glaive for mass.
 
Despite lacking various information at present, I imagine the which-Titan-first question will be upcoming! If there turns out to be no worthwhile strategic consideration then I imagine T. Taranis, Oya or Indra will be appropriate for being the focus. If a peripheral progress mechanism is needed and nothing new is introduced then that gives T. Hadad an immediate promotion, albeit with a steep Alert wall—unless disabling a Titan also stops Alerts or changes the definition of peripheral. If a disabled Titan lowers the strengths or if an alternative percentage progress becomes available, that puts the popular choices back to the top of course!
And if it turns out you need to take out the Spires first - either as an absolute thing, or to decrease the difficulty level - then Taranis and Leigong remain the obvious choices for now.
 
Fighting in Vistnera or what it's called this week. And daaaaayum is that a difficult instance! (It's an orbital city)
Yesterday I fought basically an entire instance on my own; only for a short time did another CMDR help, guess he bailed when he saw how long it would take. The instance consisted of something like 1-2 Medusas, 3-4 Basilisks, and of course a bunch of Cyclopes. All in all I was busy for almost 3 hours, it was draining. And then in the end a full 3 Hydras (which ofc I didn't take on by myself).
Nevertheless I returned today and arrived during a Hydra stage -- 3 again. It was pretty buggy; sometimes the Hydra just teleported like 7km in one second, sometimes it just warped all over the screen. We killed two of them and then the stage counted as completed, while the third was still happily shooting at the station.

Yeah well, long story short... orbital city CZs are no joke. I hope we'll manage to complete the system this week.
 
Meanwhile, in Aowicha on Thursday, I’d taken it upon myself to solo a planetary port instance all the way including the Hydras with a four modshard Krait.

While I am happy to report that I did, in fact, do it, I’m also probably not going to do it again. It was also a bit of an impromptu thing because I ran it in open and due to both time of day and the early stage of the cycle, nobody came to join me around there.

(I also haven’t frequented any open instances after that because they’ve just been horribly unstable for me ever since this Thursday if there was another player - still trying to determine if it was my internet or not… sure has been acting up a lot the last two days, for no visible reason, so I am inclined to put that down as the cause.)
 
Back
Top Bottom