Thargoid invasion - Next target systems?

I‘ve also not yet seen any of them at outposts. I have been fighting at Knight Base in 70 Tauri for a few days now, and encountered zero Glaives.
Well, I guess I know where to go for a worry-free Guardian weapon playground then. It seems fair considering that the outpost CZs are more restrictive(with only one medium pad and all).

Anyone want to take bets on how much and long it will take to clear Hupang’s invasion? (… providing that it gets cleared.)
 
Well, I guess I know where to go for a worry-free Guardian weapon playground then. It seems fair considering that the outpost CZs are more restrictive(with only one medium pad and all).

Anyone want to take bets on how much and long it will take to clear Hupang’s invasion? (… providing that it gets cleared.)
It's noticeable that attacked ground ports are falling out of favour and attacked outposts are making a comeback as the go to for combat. Since the start the AX pilots in our alliance have favoured them as the least buggy option.

With Hupang it's impossible to predict. With Xmas out of the way and enough people it might only be a week, but possibly at the expense of not clearing many others.
 
It's noticeable that attacked ground ports are falling out of favour and attacked outposts are making a comeback as the go to for combat. Since the start the AX pilots in our alliance have favoured them as the least buggy option.
I never really minded the outposts and occasionally do like the added challenge that the swarms present.

… when they don’t frustrate the heck out of me because of NPCs constantly agitating them so it’s entirely unpredictable whether you’re about to eat missiles, and literally everything turns to start shooting at me the moment I do anything.

(Not having any Glaives showing up on top of them being generally the most ‘stable’ type of station CZ is also a bonus.)

That said, I do like the ground ports as occasional ‘easier’ content, while it isn’t completely trivializing the combat either. Never noticed any significant framerate issues around them either… though those fires around the port itself are quite a performance hog(as I noticed when I tried playing the game on my old PC with a 1060… I think it’s a 1060… and turning FSR on got it to a smooth 60 FPS, with it off… not so much).

The big starports? Not something I made many experiences with. Just enough to deal with interceptors rotating with the port due to someone sitting inside it for over a minute.
 
added challenge that the swarms present
Once you get into the rhythm and have a reasonably fast ship that can outrun the swarm (I alternate between 530 m/s Krait MKII and 577 m/s Phantom) you can mostly ignore them. With 3 MRP-s and 4500 hull I can eat several kamikaze attacks before needing to repair.
Never noticed any significant framerate issues around them either… though those fires around the port itself are quite a performance hog(as I noticed when I tried playing the game on my old PC with a 1060
With my RX570 I get frame drops/stutter when within ~5 klicks of a surface port. When I'm 10 klicks out it's reasonably smooth.
 
though those fires around the port itself are quite a performance hog(as I noticed when I tried playing the game on my old PC with a 1060… I think it’s a 1060… and turning FSR on got it to a smooth 60 FPS, with it off… not so much).
Heh, interesting. I have a 1060 and never had any problems with stuttering or anything, and it turns out my game already had FSR enabled (I certainly didn't do that myself bc I had no idea it existed). A buddy of mine has those problems though, I'll have to tell him to check that setting (assuming he has an AMD cpu). Thanks for the pointer! ^^

Edit, ontopic:
Hupang has a ground base under attack, 152ls, 0.5G, now if that doesn't sound inviting I don't know what. ^^
 
Last edited:

Week 57, 28th December 3309​

Report
Twenty-seven Alerts repelled at HIPs 3006, 2422 and 19600, Cephei Sectors FB-X b1-1 and DQ-Y b1, Pegasi Sectors UK-L a9-3, HH-U b3-2, MN-S b4-0, JH-U b3-8 and MN-S b4-2, Col 285 Sectors OG-E b12-0, SM-C b13-0, JG-O c6-5, VN-H b11-6, VN-H b11-5, ZT-F b12-2, OS-T d3-69, BA-P c6-16, SH-B b14-7, WN-Z b14-5 and RM-B b14-4, Hyadum II, 77 Theta-1 Tauri, 79 b Tauri, Holvandalla, Arietis Sector JR-V b2-4 and 86 Rho Tauri.
Four Invasions defended at Luggerates, HIPs 116360 and 20577, and 70 Tauri.
Three Control evictions at Pegasi Sectors KC-U b3-0, KC-U b3-3 and TK-L a9-5.
The defended Invasion systems will start Recovery.

Targets updated at 06:30 4th January 3310
Mahlina Invasion 80% *80.7%Cocijo 21 Ly, 0 ports, 224 Ls outpost damage
HIP 22524 Control 60% — Indra 20 Ly, 1830 strength
Aowicha Alert 52% *52.9%Oya 24 Ly, 4350 Ls starport, 1760 Ls planet
Lei Hsini Control 40% *41%Indra 21 Ly, 2329 strength
Scythia Invasion 26% — Indra 20 Ly, 0 ports, 270k Ls outpost damage
71 Tauri Alert 26% — Indra 15 Ly
Hyades Sector NN-S b4-3 Control 26% — Indra 19 Ly, 1816 strength
Hyades Sector PI-S b4-3 Control 24% — Indra 20 Ly, 1675 strength
Hupang Invasion 14% *15.1%Taranis 9 Ly, 3 ports, 142 Ls planet attack
Col 285 Sector VS-Z b14-0 Alert 10% *11%Hadad 19 Ly
Vocovii Alert 10% *10.8%Cocijo 24 Ly, 63k Ls outpost, 106 Ls planet
Pegasi Sector BQ-Y d71 Control 6% — Raijin 26 Ly, 1444 strength
Sugalis Control 4% *4.9%Raijin 23 Ly, 2352 strength
Pegasi Sector NN-S b4-3 Matrix 4% *4.9%Raijin 24 Ly
Col 285 Sector ZE-P c6-16 Control 4% — Cocijo 19 Ly, 2233 strength
Hyades Sector JH-V c2-13 Control 4% — Indra 19 Ly, 2468 strength
Iceniguari Control 4% — Raijin 23 Ly, 2589 strength
Pegasi Sector BQ-Y d93 Control 4% — Raijin 24 Ly, 768 strength
Pegasi Sector KC-U b3-2 Control 4% — Raijin 24 Ly, 800 strength
Pegasi Sector PE-N a8-2 Control 4% — Raijin 23 Ly, 931 strength
HIP 8525 Control 2% *3.7%Oya 18 Ly, 8809 strength
HIP 18075 Alert 2% *3%Thor 21 Ly, 1620 Ls outpost, 2930 Ls planet
Kaurukat Control 2% *2.6%Raijin 17 Ly, 11.8k strength
HIP 20916 Control 2% *2.4%Indra 17 Ly, 10.7k strength
HIP 20024 Alert 2% *2.3%Thor 19 Ly, 1959 Ls outpost, 2572 Ls planet

Notes
The Alert report lists predicted attackers.

Week 56, 21st December 3309​

Report
Fourteen Alerts repelled at Cephei Sectors AV-Y b0, AV-Y b6, AF-A c21, ZE-A c8 and WO-A b4, Pegasi Sectors RE-N a8-0, DG-X c1-6 and JH-U b3-9, Col 285 Sectors OB-E b12-4, MG-E b12-2, EA-Q c5-6 and JA-G b11-0, HIP 9709 and Vistnero.
Five Invasions defended at Chinas, Obamumbo, Iduni and HIPs 21261 and 7338.
One Control eviction at Pegasi Sector MY-O a7-5.
The defended Invasion systems will start Recovery.
 
Last edited:
Should we even attempt Hupang now, or focus on the other invasions first? My FC is currently at Taranis so for other targets I'd need to know where to move.
 
Should we even attempt Hupang now, or focus on the other invasions first? My FC is currently at Taranis so for other targets I'd need to know where to move.
Very tricky to say - it depends a bit on what the rules are for Titan attacks (we've ruled out some of the most unfavourable options, but there's still a lot of potential explanations which cover all the behaviour seen so far). But, of course, if you wait until next week when we know more, it might then be too late to save Hupang...

Under the most favourable Titan attack rules for us, saving Hupang in either one week or three weeks would be very good; saving it in two weeks, oddly, is less strong.
 
Might the most effective strategy be to stockpile "stuff" (samples/pods/etc) and dump it all in one week?

Definitely that would be true just for a short-term goal involving one occasion of taking only Hupang—the longer-term trouble is:
  • With Titans known to attack when they have no more systems, HR 1737 will be attacked immediately.
  • HR 1737 or Swahku may be attacked anyway if a new rule for Titans to attack last was added in week 53.
It is hopeless within 10 Ly if they continue attacking, which we will discover next week by watching T. Leigong. Even if they stop, we need a recovered M. Taranis to take back both a Spire site and somewhere we can use as a containment area before evicting it again, leaving behind the latter.

Some of the specifics there, affecting both points, depend on whether the invaded Hupang counts as M. Taranis having a system. By the Galaxy map numbers it does, but I am unsure whether it needs to be Control, obviously for the unknown Titan attack rules but also for the territory radius and its specific target.


Should we even attempt Hupang now, or focus on the other invasions first? My FC is currently at Taranis so for other targets I'd need to know where to move.

As above, personally I would leave it for a very long time! If we see next week that Titans stop attacking then INIV may start eyeing M. Hadad, dependent largely on the entire community to remove Spire sites, and to behave well and avoid attacking the designated containment area.

It is a shame that Titan rescues were changed only to affect Counterstrike systems; for a couple of weeks they helped the peripheral progress instead, which would have made possible something like a rescue rush followed by a defence rush.



Not so much just for the sake of Montioch:
  • If we discover that the containment area idea seems to be feasible, we will just recapture it again, this time as a peripheral system.
  • If not feasible, more so than Montioch the real loss is the entire 20 Ly sphere or more, at least until the story characters hurry a bit and give us a way to stop Alerts happening
We could actually prevent that attack this week, although it falls short of being really worth doing. Even if we spend that 7400 this week, that is already above the 5610 to recapture all of those systems with Spire support. It will also only delay Montioch, because Col 285 Sector RH-B b14-2 can reach it eventually regardless of the outcome of attacking Col 285 Sector RH-B b14-3 first.

Leaving it was a very conscious choice I mentioned at the time, although also a very easy choice!
 
Meanwhile, someone has been AFK at the planetary port of Luggerates for the entire last hour in their shard Conda, keeping a Hydra instance alive(while the bug which ‘completed’ it started a new one, so there’s a giant Scout swarm too). sigh
 
Meanwhile, someone has been AFK at the planetary port of Luggerates for the entire last hour in their shard Conda, keeping a Hydra instance alive(while the bug which ‘completed’ it started a new one, so there’s a giant Scout swarm too). sigh

If it helps, normally one can block a Commander temporarily then drop again or exit and continue to obtain a fresh zone, then unblock immediately afterwards. It is a silly workaround, but it is there for lack of a way to start a new zone which others can still join openly.
 
If someone is also working at M.Oya. SNPX plans to let Hip 2422 go into Invasion (because with that layout of stations it will be a wonderfull invasionsystem) while clearing Aowicha and the other uninhabited alerts. @Phill P I think it was you who said that pdes doesn´t want to have invasions. However it would mean you can focus on the other 5 inhabited alert systems. And with the invasions already there they should be the first priority. Also if we repell it in the status invasion, we wouldn´t have to worry about it for 2 weeks or more.
We hope we also get Luggerates this cycle with an ground station under attack.

o7 Cmdr
 
Last edited:
So this happened. I noticed one Hydra's health bar disappear at around 70%, and then when I went looking for the second as it was nearly killed, I saw it on my contacts and decided to instead investigate. I would say it was worth it.

 
Well, I guess I know where to go for a worry-free Guardian weapon playground then. It seems fair considering that the outpost CZs are more restrictive(with only one medium pad and all).
Thing is, you are able to finish off an outpost CZ solo with a 5 AXMC or a 4 Modshard Krait Mk2 quite easily in 30 min or so (98% Cyclops and Scouts only). And then bang, the two Hydras arrive & you have to relog, which is kind of crazy and removes a little bit of satisfaction.. (at least for me). Of course there is still open play, but I observed that more CMDRs do the brave Sir Robin (which I try to avoid in open) when the Hydras drop in than at planet sides.
 
Thing is, you are able to finish off an outpost CZ solo with a 5 AXMC or a 4 Modshard Krait Mk2 quite easily in 30 min or so (98% Cyclops and Scouts only). And then bang, the two Hydras arrive & you have to relog, which is kind of crazy and removes a little bit of satisfaction.. (at least for me). Of course there is still open play, but I observed that more CMDRs do the brave Sir Robin (which I try to avoid in open) when the Hydras drop in than at planet sides.
I would prefer to fight the Hydras of course, but as is I’m not very confident I’d like to take a Guardian-only weapon build to a surface port(do the Glaives spawn at the big orbitals?), where people do fight them, although I’ve also only seen one trio of Glaives in a few of the CZs that I did(all but one of which were already well underway).

… and if you’re that unfortunate person to only have AXMCs during that Hydra phase, well, you’re not gonna be doing a whole lot about them anyway.
 
Thing is, you are able to finish off an outpost CZ solo with a 5 AXMC or a 4 Modshard Krait Mk2 quite easily in 30 min or so (98% Cyclops and Scouts only).
30 minutes! Last time I soloed an instance, it kept me busy a full 90 minutes. Sure, a better pilot might get through somewhat faster, but not by that much. Maybe with a 6-shard Instagib Conda; haven't tried that. If I tallied the score halfway correctly, there were about 22-24 Cyclopes, or over 90 hearts. You really saying you can wreck the shields, exert a heart and destroy it, all in 20 seconds total, 90 times in a row, without fail, and after every 4th heart the next Clops is lined right up without ever having to cover distance? If so, then chapeau. Sorry if I'm sounding a bit incredulous, but yeah, I am.
 
Back
Top Bottom