They needed to source enough mulched human fertilizer first.
Thargoid invasion - Next target systems?
- Thread starter Aleks Zuno
- Start date
That's pretty bad if we've all only just noticed. Are we sure it's not just been put in by U16? Or perhaps it was set to happen by U16 if those systems were not cleared first.
Oh, I'm sure that they only "matured" in U16 so that we can start detecting them.
Another interesting question is why those specific systems: there's no pattern obvious so far beyond "uninhabited control system with a landable atmosphere world" ... but plenty of other systems which also meet that definition don't seem to have them (or not found yet, anyway)
No pattern has been found at all to them? That's frustrating.
If they are meant to stop war progress they should remove the progress bar so we know they are lost. If it's a bug that the bar isn't moving, they should say so and fix it really.
Last edited:
I think Oya only has 3 systems within 25ly that could be potential barnacle sites and 2 of them are confirmed sites.
Another Leigong - Hyades Sector NT-I b9-4 > 31 ly
Well, it's only been three days and not everywhere that does have them has been found, so that's not entirely surprising.
26 January so another early capture. Leigong (and Thor) you'd expect to see them further out as they need to have a higher radius for the same index. Though at ~160th that one might also be the highest index found so far.
I did a spot of scanning planets ahead of attempting to guard Wangakwan, and I think I found a novel site myself; is the following of interest to @Ian Doncaster, @Disemboweled Ego or @Factabulous?
Presumably that means the best we could do is to work around it and discover whether Wangakwan is still attacked.
Presumably that means the best we could do is to work around it and discover whether Wangakwan is still attacked.
It's probably an orbital AXCZ since it's a high-ish gravity non-atmo world and needs a DSS to confirm - sometimes AXCZs can require a DSS to show up even if there isn't an obvious one in orbit. I recently saw it in an uncontrolled system with AXCZs from last week.
There were a few TBM sites in counterstrike systems that I assume still were impossible to make progress in?
Understood, thank you, and sorry for mentioning the signal prematurely! Finding things this way is very new to me, to the extent that I had no idea where to find "Locations" until a friend suggested pressing H for help and I found it on the final page. I will verify it with the DSS immediately after we have finished at Hyades Sector HW-W d1-88, which has no planets and very much should be achievable.
Without having checked progress prospects yet, Trianguli Sector EQ-Y b0 has a counter-attack glow and has a site reported at planet 2.
Rather than using the DSS you can just look for the AXCZs. Number of thargoids locations = number of AXCZs + number of surface sites.
Indeed that Thargoid location was both attributable to a Conflict zone nearby and nothing to be seen on the DSS. With Fleet Carrier times as they are, I am considering building a dedicated explorer for it with the primary task of being interdicted and getting a few kills, with possible site discovery as an afterthought.
All of this feels very much like an error; it makes little sense that we have to get a few pilot-kills in candidate systems on the previous day just for an assured indication of possible defence options for the present day, that the Galaxy map does not reflect it, and that at least one counter-attack system is part of it. Too much seems out of place for that to be a decision to freeze those systems, and I think the simplest explanation is that the war activity was disrupted by mistake.
Thank you; this was very helpful! Hyades Sector AA-P b6-4 had a few more planets with Thargoid locations but all of them matched a Conflict zone. I think it may be slightly fallible though, with Hyades Sector EG-N b7-2 1 as an example of a planet which has a Conflict attached to it but shows None in the Locations, admitting the possibility of a genuine site were it to show a Thargoid location.
All of this feels very much like an error; it makes little sense that we have to get a few pilot-kills in candidate systems on the previous day just for an assured indication of possible defence options for the present day, that the Galaxy map does not reflect it, and that at least one counter-attack system is part of it. Too much seems out of place for that to be a decision to freeze those systems, and I think the simplest explanation is that the war activity was disrupted by mistake.
Thank you; this was very helpful! Hyades Sector AA-P b6-4 had a few more planets with Thargoid locations but all of them matched a Conflict zone. I think it may be slightly fallible though, with Hyades Sector EG-N b7-2 1 as an example of a planet which has a Conflict attached to it but shows None in the Locations, admitting the possibility of a genuine site were it to show a Thargoid location.
Thank you also, this explains the Thargoid signal in Cephei Sector AF-A c9, planet A1, where there is a combat zone, too.
Happens a lot
Best thing is to wait until you see the matrix in the nav panel. You can report by simply scanning any of the Codex items on the site while running an uploader - EDDN is being monitored o7Victories in 69 Upsilon Tauri, Col 285 Sector YT-Q c5-10, HIPs 111081, 4041, 5898 and 6268, and Hyades Sectors TJ-R c4-10 and TJ-R c4-11!
Alerts at 09:40 5th August 3309:
HIP 23716 Alert 82% *82.6% — Taranis 18 Ly, 2314 Ls starport, 2351 Ls outpost, 2354 Ls planet
Vistnero Alert 80% *83.2% — Raijin 21 Ly, 147 Ls starport, 365 Ls outpost, 147 Ls planet
Ebisu Alert 74% *78.4% — Taranis 21 Ly, 358 Ls starport, 63 Ls outpost, 1798 Ls planet
Muruidooges Alert 66% *68.2% — Hadad 18 Ly, 1018 Ls starport, 7321 Ls outpost, 7320 Ls planet
HIP 20492 Alert 64% *65.4% — Indra 24 Ly, 3308 Ls starport, 3168 Ls outpost, 5791 Ls planet
Holvandalla Alert 36% — Raijin 21 Ly, 86 Ls starport, 19 Ls outpost, 43 Ls planet
Evictions:
HIP 19781 Control 42% *43.3% — Indra 26 Ly, 871 strength
Clean-up:
Trianguli Sector ZJ-A b1 Alert 86% — Taranis 22 Ly, empty
Hyades Sector NS-T c3-14 Alert 50% — Taranis 23 Ly, empty
Col 285 Sector SM-C b13-0 Alert 36% *38.8% — Thor 22 Ly, empty
90 c1 Tauri Alert 34% — Indra 26 Ly, empty
Cephei Sector AV-Y b2 Alert 30% — Oya 18 Ly, empty
The excessive Fleet Carrier jump queue makes things a bit too difficult to defend as we have been doing, although it is recognised now as being likely more than a simple too high demand! In the meantime, after a delivery to guard Wangakwan and Ildano we will just proceed with Operation Redacted in HIP 9016, such that Fleet Carriers can remain stationary rather than attempting the usual agility during a time where it is prohibitive to use them.
Alerts at 09:40 5th August 3309:
HIP 23716 Alert 82% *82.6% — Taranis 18 Ly, 2314 Ls starport, 2351 Ls outpost, 2354 Ls planet
Vistnero Alert 80% *83.2% — Raijin 21 Ly, 147 Ls starport, 365 Ls outpost, 147 Ls planet
Ebisu Alert 74% *78.4% — Taranis 21 Ly, 358 Ls starport, 63 Ls outpost, 1798 Ls planet
Muruidooges Alert 66% *68.2% — Hadad 18 Ly, 1018 Ls starport, 7321 Ls outpost, 7320 Ls planet
HIP 20492 Alert 64% *65.4% — Indra 24 Ly, 3308 Ls starport, 3168 Ls outpost, 5791 Ls planet
Holvandalla Alert 36% — Raijin 21 Ly, 86 Ls starport, 19 Ls outpost, 43 Ls planet
Evictions:
HIP 19781 Control 42% *43.3% — Indra 26 Ly, 871 strength
Clean-up:
Trianguli Sector ZJ-A b1 Alert 86% — Taranis 22 Ly, empty
Hyades Sector NS-T c3-14 Alert 50% — Taranis 23 Ly, empty
Col 285 Sector SM-C b13-0 Alert 36% *38.8% — Thor 22 Ly, empty
90 c1 Tauri Alert 34% — Indra 26 Ly, empty
Cephei Sector AV-Y b2 Alert 30% — Oya 18 Ly, empty
The excessive Fleet Carrier jump queue makes things a bit too difficult to defend as we have been doing, although it is recognised now as being likely more than a simple too high demand! In the meantime, after a delivery to guard Wangakwan and Ildano we will just proceed with Operation Redacted in HIP 9016, such that Fleet Carriers can remain stationary rather than attempting the usual agility during a time where it is prohibitive to use them.
Victories in HIPs 20492 and 23716, Vistnero, Ebisu, Trianguli Sector ZJ-A b1, Col 285 Sectors SM-C b13-0 and JG-O c6-5, and Hyades Sectors AA-P b6-4, EG-N b7-2, HW-W d1-88 and QN-T c3-13! An astounding amount of Alert repulsion, and Wangakwan and Ildano are guarded.
Alerts at 18:10 5th August 3309:
Muruidooges Alert 80% *80.9% — Hadad 18 Ly, 1018 Ls starport, 7321 Ls outpost, 7320 Ls planet
Holvandalla Alert 52% *52.2% — Raijin 21 Ly, 86 Ls starport, 19 Ls outpost, 43 Ls planet
Khwal Alert 24% *24.6% — Cocijo 22 Ly, 67 Ls outpost, 89 Ls planet
HIP 25679 Alert 14% — Taranis 17 Ly, 108 Ls outpost, 1960 Ls planet
Evictions:
HIP 19781 Control 48% *48.3% — Indra 26 Ly, 795 strength
Clean-up:
Hyades Sector NS-T c3-14 Alert 80% — Taranis 23 Ly, empty
90 c1 Tauri Alert 54% *55.3% — Indra 26 Ly, empty
Cephei Sector AV-Y b2 Alert 44% *44.6% — Oya 18 Ly, empty
Arietis Sector JR-V b2-2 Alert 22% — Indra 26 Ly, empty
Alerts at 18:10 5th August 3309:
Muruidooges Alert 80% *80.9% — Hadad 18 Ly, 1018 Ls starport, 7321 Ls outpost, 7320 Ls planet
Holvandalla Alert 52% *52.2% — Raijin 21 Ly, 86 Ls starport, 19 Ls outpost, 43 Ls planet
Khwal Alert 24% *24.6% — Cocijo 22 Ly, 67 Ls outpost, 89 Ls planet
HIP 25679 Alert 14% — Taranis 17 Ly, 108 Ls outpost, 1960 Ls planet
Evictions:
HIP 19781 Control 48% *48.3% — Indra 26 Ly, 795 strength
Clean-up:
Hyades Sector NS-T c3-14 Alert 80% — Taranis 23 Ly, empty
90 c1 Tauri Alert 54% *55.3% — Indra 26 Ly, empty
Cephei Sector AV-Y b2 Alert 44% *44.6% — Oya 18 Ly, empty
Arietis Sector JR-V b2-2 Alert 22% — Indra 26 Ly, empty
Are the alerts going faster now because of the Scythe activity being investigated/countered?
We know that it’s a decent method to do Alerts, but there was a report from SNPX that the difficulty of Alerts was decreased- so, not certain.
This is only from observation, not testing as such, but I spent Thargsday night trying it out. I spent 3 hours in an unpopulated Alert with an escape pod in my hold and killed Scythes as I was continually interdicted. I killed 35 of them, sold the carapaces I'd gathered and the progress bar moved around 7 pips. There were some others there but could not have been that many, it only had one pip when I went in. So let's err on the side of caution and say I got 4-5 pips at most.
In around half the time I could have cleared the entire system with three NHSS4s and 270 samples. So even without exact numbers it is demonstrably not faster than sampling - unless you can balance that by having more people doing it. Which is possible because it's more fun. It's also guaranteed to get an encounter every few minutes, unlike a signal.
And yes, Alerts on the whole feel easier after U16. It's not just a target drop though, the change to the missions has played a large part as well. Evacs are clearing populated Alerts faster which again, without testing, I am assuming is due to mission bonuses because the missions are back to the old way of doing them with smaller numbers per mission. And now we have the addition of personal transportation missions, the first time a rescue mission has needed any cabin other than Economy.
Even if they have changed the weightings of the individual types of mission, which is highly likely but untestable with so many CMDRs in every populated Alert right now, the mission bonuses are very obviously still important, and with the smaller numbers per mission we're now handing in up to 20 per trip. This at least tallies with our earlier observations about mission bonuses and their value. The importance of mission bonus stacking appears unchanged in that respect at least.
The measurement-preventing storm of Alerts continues—victories in 90 c1 Tauri, Muruidooges, Holvandalla and Hyades Sector NS-T c3-14! Five populated Alert systems remain.
Alerts at 09:10 6th August 3309:
HIP 25679 Alert 70% *72.6% — Taranis 17 Ly, 108 Ls outpost, 1960 Ls planet
Khwal Alert 36% *38.9% — Cocijo 22 Ly, 67 Ls outpost, 89 Ls planet
Col 285 Sector ZE-P c6-11 Alert 18% — Cocijo 29 Ly, 11k Ls planet
Paitra Alert 12% — Cocijo 25 Ly, 511 Ls outpost
HIP 116360 Alert 2% — Raijin 21 Ly, 649 Ls outpost, 462 Ls planet
Eviction:
HIP 19781 Control 62% *63.2% — Indra 26 Ly, 566 strength
Clean-up:
Cephei Sector AV-Y b2 Alert 50% *50.7% — Oya 18 Ly, empty
Trianguli Sector EQ-Y b2 Control 34% *34.7% — Taranis 19 Ly, empty, 1095 strength
Arietis Sector JR-V b2-2 Alert 32% — Indra 26 Ly, empty
A few findings from visiting one of the new sites:
Alerts at 09:10 6th August 3309:
HIP 25679 Alert 70% *72.6% — Taranis 17 Ly, 108 Ls outpost, 1960 Ls planet
Khwal Alert 36% *38.9% — Cocijo 22 Ly, 67 Ls outpost, 89 Ls planet
Col 285 Sector ZE-P c6-11 Alert 18% — Cocijo 29 Ly, 11k Ls planet
Paitra Alert 12% — Cocijo 25 Ly, 511 Ls outpost
HIP 116360 Alert 2% — Raijin 21 Ly, 649 Ls outpost, 462 Ls planet
Eviction:
HIP 19781 Control 62% *63.2% — Indra 26 Ly, 566 strength
Clean-up:
Cephei Sector AV-Y b2 Alert 50% *50.7% — Oya 18 Ly, empty
Trianguli Sector EQ-Y b2 Control 34% *34.7% — Taranis 19 Ly, empty, 1095 strength
Arietis Sector JR-V b2-2 Alert 32% — Indra 26 Ly, empty
A few findings from visiting one of the new sites:
- For various reasons, these look designed for having two Commanders, ground and sky.
- Advanced Missiles from above are very effective at keeping the ground safe, using pairs of missiles with normal ammunition.
- On-foot or Scorpion attacks are good for protecting the starship above.
- Remote-release flak deals a small amount of damage, but seemed not to be a feasible option.
- If a Scout arrives it behoves the pilot to destroy it before it reaches the ground; two class 3 EAX multi-cannons are fine if targeted immediately.
- Coral Sap from destroying growths on the ground is corrosive and therefore inadvisable to store in a vehicle, however—
- Collector limpets from above are surprisingly effective at sensing materials and cargo!
This places corrosive items into the starship hold directly, and gathers numerous Thargoid materials for the pilot. Many Collectors will destroy themselves colliding with terrain, but watching their path and positioning the starship above their goal seems to work well. Because returning Limpets seek a specific clearance below the cargo scoop, this requires also to maintain a bit of altitude, otherwise they fly straight into the ground. - Having arrived on the night-side of the planet, apparently disabling Night vision on-foot made it quite spooky having only my headlights from above for illumination.
- I thought I saw a structure glow briefly but could not be sure, then later the on-foot Commander thought the same but could not be sure either.