Taking a first-pass look at the new extra alert on each titan, I'm thinking that the number of alerts each titan can do has just gone up to 6, and the titan is the last to alert. This would explain why some of the 6-alert titans still have alerts further out than 15 ly. Meanwhile, Taranis didn't alert at all, but every system within 10 ly is on cooldown.
Analysing the Thargoid Simulation
- Thread starter Ian Doncaster
- Start date
Indeed; clearly HIP 8887 has attacked HIP 9016 as its only non-respite target, meanwhile HIP 30377 has two non-respite targets it ignored. Unknown is whether the Titan only attacks if it has no other systems.
Yes - we'll need to watch Taranis for a few weeks to see how it reacts as it regains systems. "6 Alerts, or it can swap all of them to send an Alert from the Titan" is a plausible rule as well given the observations so far. We'll also find out if Titans have attack cooldown in the same way as normal Controls, or if they can do it every week.
Once allowing for a sixth alert, another discrepancy at Thor - HIP 21125 attacked rather than EA-Q c5-7 by (presumably) EA-Q c5-5 - but otherwise everything was as expected.
Looking at the target options, this was another "attacked 4th rather than 5th" situation so it's possible that there's a rule that it can't look more than 4 targets out when selecting (I'm fairly sure that won't break any previous weeks - works for Tougeir and I think also for HIP 8525/7338) but I'd like to get a few more observations first, and it doesn't explain Ixbalan going 3rd rather than 2nd so it feels like there might be a more general explanation to be found.
Once allowing for a sixth alert, another discrepancy at Thor - HIP 21125 attacked rather than EA-Q c5-7 by (presumably) EA-Q c5-5 - but otherwise everything was as expected.
Looking at the target options, this was another "attacked 4th rather than 5th" situation so it's possible that there's a rule that it can't look more than 4 targets out when selecting (I'm fairly sure that won't break any previous weeks - works for Tougeir and I think also for HIP 8525/7338) but I'd like to get a few more observations first, and it doesn't explain Ixbalan going 3rd rather than 2nd so it feels like there might be a more general explanation to be found.
Narwhal Nose report generated 7 December
-------------------------------------------
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Target: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting.
Target Distance: The distance in LY to the Maelstrom of the target. A primary component of Thargoid prioritisation.
Control Distance: The distance in LY to the Maelstrom of the attacking Control. A primary component of Thargoid prioritisation when attacking outside the control sphere.
Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a Spire are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here.
Inhabited: Whether the system contains standing human population.
Until we get more data on exactly when Titans can place Alerts I'm not going to change that aspect of the prediction, but I have adjusted the Alert budget to 6 as this can affect backtrack calculations. Both Taranis and Leigong should give useful information in that respect over the next few weeks.
-------------------------------------------
Calculating Taranis
Read 0 control systems and 999 targets.
Total connected: 0
Furthest Control: 0.000 LY
Taranis 10 LY targets are all on cooldown for another week anyway
-------------------------------------------
Calculating Leigong
Read 0 control systems and 996 targets.
Total connected: 0
Furthest Control: 0.000 LY
Furthest potential capture: 9.603 LY
And similarly at Leigong
-------------------------------------------
Calculating Indra
Read 47 control systems and 945 targets.
Total connected: 35
Disconnected Controls
Furthest Control: 21.108 LY
A normal six at Indra, narrowly. Knocking out HIP 20679 would lose it an Alert due to the mode switch.
-------------------------------------------
Calculating Oya
Read 24 control systems and 968 targets.
Total connected: 24
Furthest Control: 17.920 LY
Furthest potential capture: 18.528 LY
Only three possible targets so all should go through.
-------------------------------------------
Calculating Cocijo
Read 57 control systems and 936 targets.
Total connected: 56
Disconnected Controls
Furthest Control: 21.999 LY
Again an option to lose Cocijo an alert by knocking out HIP 38235
-------------------------------------------
Calculating Thor
Read 36 control systems and 956 targets.
Total connected: 32
Disconnected Controls
Furthest Control: 18.989 LY
Furthest potential capture: 24.842 LY
Only six possible, but the backtrack is there to get all of them.
-------------------------------------------
Calculating Raijin
Read 79 control systems and 914 targets.
Total connected: 79
Furthest Control: 27.097 LY
A normal interior six at Raijin
-------------------------------------------
Calculating Hadad
Read 45 control systems and 948 targets.
Total connected: 45
Furthest Control: 24.118 LY
And a normal interior 6 at Hadad.
-------------------------------------------
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Target: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting.
Target Distance: The distance in LY to the Maelstrom of the target. A primary component of Thargoid prioritisation.
Control Distance: The distance in LY to the Maelstrom of the attacking Control. A primary component of Thargoid prioritisation when attacking outside the control sphere.
Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a Spire are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here.
Inhabited: Whether the system contains standing human population.
Until we get more data on exactly when Titans can place Alerts I'm not going to change that aspect of the prediction, but I have adjusted the Alert budget to 6 as this can affect backtrack calculations. Both Taranis and Leigong should give useful information in that respect over the next few weeks.
-------------------------------------------
Calculating Taranis
Read 0 control systems and 999 targets.
Total connected: 0
Furthest Control: 0.000 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| - | - | - | Control Sphere Edge | - |
-------------------------------------------
Calculating Leigong
Read 0 control systems and 996 targets.
Total connected: 0
Furthest Control: 0.000 LY
Furthest potential capture: 9.603 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| - | - | - | Control Sphere Edge | - |
-------------------------------------------
Calculating Indra
Read 47 control systems and 945 targets.
Total connected: 35
Disconnected Controls
| System | Distance |
| 75 Tauri | 12.76477392 |
| HIP 19098 | 13.95811956 |
| Arietis Sector IG-X b1-4 | 15.09711401 |
| 76 Tauri | 15.46350921 |
| Arietis Sector HG-X b1-1 | 15.84982009 |
| Arietis Sector HG-X b1-2 | 15.8593673 |
| HIP 21179 | 16.59951642 |
| Hyades Sector NN-S b4-2 | 17.95964443 |
| Hyades Sector NN-S b4-1 | 18.37212988 |
| Hyades Sector JH-V c2-13 | 18.59377626 |
| Hyades Sector PI-S b4-3 | 19.51369211 |
| Lei Hsini | 21.10781938 |
Furthest Control: 21.108 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| HIP 20577 | 17.806 | 14.040 | Hyadum I; HR 1354; HIP 20679; | Yes |
| Obamumbo | 18.655 | 14.788 | HIP 19263; Gaezatorix (9.996 LY); | Yes |
| Arietis Sector LM-V b2-3 | 20.115 | 13.958 | HIP 19098; | No |
| Scythia | 20.227 | 13.254 | Arietis Sector EQ-Y c18; HIP 20187; Gaezatorix; etc | Yes |
| HIP 21261 | 20.241 | 17.820 | HR 1354; HIP 20679; | Yes |
| 70 Tauri | 20.963 | 17.871 | HIP 20679; | Yes |
| - | - | - | Control Sphere Edge | - |
| Hyades Sector ST-Q b5-5 | 21.702 | 13.569 | HIP 21912; | No |
| HIP 19157 | 21.650 | 15.097 | Arietis Sector IG-X b1-4; | Yes |
| Hyades Sector PI-S b4-2 | 22.428 | 15.464 | 76 Tauri; | No |
| Arietis Sector HG-X b1-3 | 22.469 | 15.850 | Arietis Sector HG-X b1-1; (backtrack Arietis Sector HG-X b1-0) | No |
-------------------------------------------
Calculating Oya
Read 24 control systems and 968 targets.
Total connected: 24
Furthest Control: 17.920 LY
Furthest potential capture: 18.528 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| - | - | - | Control Sphere Edge | - |
| HIP 7338 | 18.853 | 12.495 | Kanus; | Yes |
| Cephei Sector AF-A c22 | 21.188 | 12.692 | Niu Yun (9.908 LY); | No |
| Luggerates | 21.962 | 14.713 | Sambaho; | Yes |
-------------------------------------------
Calculating Cocijo
Read 57 control systems and 936 targets.
Total connected: 56
Disconnected Controls
| System | Distance |
| Col 285 Sector WY-F b12-1 | 20.85255624 |
Furthest Control: 21.999 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Col 285 Sector UN-H b11-5 | 19.376 | 16.621 | Ulche; Col 285 Sector UN-H b11-4; | No |
| Col 285 Sector YT-F b12-6 | 20.034 | 17.688 | Col 285 Sector WY-F b12-3; | No |
| Col 285 Sector SS-H b11-4 | 20.309 | 14.428 | Col 285 Sector VY-Q c5-15; Col 285 Sector VY-Q c5-17; Col 285 Sector SS-H b11-6; etc | No |
| Mahlina | 21.146 | 15.964 | Col 285 Sector VY-Q c5-17; | Yes |
| Col 285 Sector ZT-F b12-4 | 21.191 | 20.745 | HIP 38235; | No |
| Col 285 Sector OS-T d3-105 | 21.681 | 16.153 | Col 285 Sector OS-T d3-143; | No |
| - | - | - | Control Sphere Edge | - |
| Col 285 Sector VN-H b11-5 | 24.181 | 14.622 | Col 285 Sector VN-H b11-1; (backtrack Col 285 Sector VN-H b11-6) | No |
| Col 285 Sector OS-T d3-136 | 22.883 | 15.249 | Col 285 Sector OS-T d3-92; (backtrack Col 285 Sector OS-T d3-69) | No |
| Col 285 Sector VN-H b11-6 | 22.723 | 15.670 | HIP 36809; | No |
| Col 285 Sector KM-V d2-53 | 22.365 | 16.216 | Col 285 Sector VN-H b11-3; | No |
-------------------------------------------
Calculating Thor
Read 36 control systems and 956 targets.
Total connected: 32
Disconnected Controls
| System | Distance |
| Rajuarpai | 11.4695589 |
| Chanyaya | 16.10879151 |
| HIP 19894 | 16.20887223 |
| Col 285 Sector IG-O c6-14 | 17.71585625 |
Furthest Control: 18.989 LY
Furthest potential capture: 24.842 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| - | - | - | Control Sphere Edge | - |
| Col 285 Sector UH-C b13-2 | 21.239 | 16.097 | Col 285 Sector QB-E b12-0; | No |
| Col 285 Sector JA-G b11-3 | 26.122 | 17.210 | Col 285 Sector NG-E b12-5; (backtrack Col 285 Sector NG-E b12-4)(backtrack Col 285 Sector NG-E b12-3) | No |
| Col 285 Sector NG-E b12-3 | 24.094 | 17.596 | Col 285 Sector NG-E b12-2; (backtrack Col 285 Sector OG-E b12-1)(backtrack Col 285 Sector NG-E b12-1) | No |
| Col 285 Sector KB-O c6-2 | 23.534 | 18.083 | Col 285 Sector RW-D b12-3; (backtrack Col 285 Sector KB-O c6-3) | No |
| Col 285 Sector KA-G b11-0 | 26.493 | 18.984 | Col 285 Sector JA-G b11-1; (backtrack Col 285 Sector EA-Q c5-6)(backtrack Col 285 Sector JA-G b11-0)(backtrack Col 285 Sector OC-V d2-96)(backtrack Col 285 Sector EA-Q c5-7)(backtrack Col 285 Sector EA-Q c5-1) | No |
| Col 285 Sector SW-D b12-2 | 25.824 | 18.989 | Col 285 Sector QB-E b12-2; | No |
-------------------------------------------
Calculating Raijin
Read 79 control systems and 914 targets.
Total connected: 79
Furthest Control: 27.097 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Pegasi Sector QE-N a8-1 | 19.034 | 19.893 | Pegasi Sector DG-X c1-5; HIP 115162; Pegasi Sector MY-O a7-5; etc | No |
| Nu Guang | 19.330 | 11.760 | Snoqui; | Yes |
| Pegasi Sector NN-S b4-4 | 21.135 | 15.433 | HIP 112823; Pegasi Sector NN-S b4-5; Pegasi Sector NN-S b4-3; | No |
| Pegasi Sector KH-V c2-20 | 22.027 | 18.026 | Pegasi Sector PI-S b4-0; Pegasi Sector PI-S b4-5; Pegasi Sector GW-W d1-115; | No |
| Pegasi Sector NY-O a7-1 | 22.028 | 21.106 | Pegasi Sector MY-O a7-5; | No |
| Iduni | 22.038 | 18.082 | Pegasi Sector PI-S b4-5; Pegasi Sector GW-W d1-115; | Yes |
| Pegasi Sector IH-U b3-8 | 22.044 | 18.160 | Pegasi Sector KC-U b3-6; Pegasi Sector IH-U b3-9; Pegasi Sector KC-U b3-7; | No |
| Nibelaako | 22.263 | 16.841 | Pegasi Sector IH-U b3-0; Pegasi Sector IH-U b3-4; HIP 115162; | Yes |
| Pegasi Sector PI-S b4-3 | 22.274 | 16.575 | Kaurukat; HIP 113785; | No |
| Pegasi Sector OI-S b4-4 | 22.349 | 17.789 | Pegasi Sector JH-V c2-13; | No |
-------------------------------------------
Calculating Hadad
Read 45 control systems and 948 targets.
Total connected: 45
Furthest Control: 24.118 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Col 285 Sector RH-B b14-2 | 9.378 | 11.063 | HIP 29226; | No |
| Col 285 Sector SH-B b14-2 | 18.310 | 15.315 | Col 285 Sector QM-B b14-1; Col 285 Sector QM-B b14-2; | No |
| Col 285 Sector KW-M c7-31 | 20.046 | 11.724 | Col 285 Sector KW-M c7-7; Col 285 Sector KW-M c7-4; HIP 31648; etc | No |
| Col 285 Sector RM-B b14-8 | 20.607 | 17.626 | Col 285 Sector RM-B b14-3; | No |
| Col 285 Sector PM-B b14-3 | 20.783 | 14.577 | HIP 31648; Col 285 Sector KW-M c7-5; Col 285 Sector KW-M c7-2; etc | No |
| Col 285 Sector PM-B b14-4 | 20.982 | 14.845 | Col 285 Sector KW-M c7-5; Col 285 Sector KW-M c7-2; Col 285 Sector KW-M c7-3; etc | No |
| Col 285 Sector RM-B b14-4 | 21.892 | 15.344 | HIP 31223; Col 285 Sector VS-Z b14-3; | No |
| Col 285 Sector KW-M c7-28 | 22.158 | 17.395 | Col 285 Sector QM-B b14-7; Col 285 Sector KW-M c7-30; | No |
| Col 285 Sector WN-Z b14-2 | 22.372 | 18.869 | Col 285 Sector WN-Z b14-1; Col 285 Sector SH-B b14-6; | No |
| Col 285 Sector RM-B b14-6 | 22.792 | 17.550 | Col 285 Sector KW-M c7-30; | No |
Code:
-- Taranis
-- Leigong
-- Indra
HIP 20086:1
63 Tauri:1
HIP 20350:1
HIP 20916:1
HIP 20349:1
64 Tauri:1
-- Oya
HIP 8525:1
HIP 10778:1
Ardhri:1
Cephei Sector AV-Y b3:1
Daruwach:1
-- Cocijo
Col 285 Sector OS-T d3-96:1
Mapon:1
Col 285 Sector SS-H b11-7:1
Col 285 Sector WY-F b12-1:1
Col 285 Sector SS-H b11-1:1
Col 285 Sector ZT-F b12-3:1
-- Thor
Col 285 Sector JA-G b11-2:1
Col 285 Sector OG-E b12-2:1
Chanyaya:1
HIP 19894:1
Col 285 Sector LV-F b11-1:1
Col 285 Sector EA-Q c5-5:1
-- Raijin
Sholintet:1
Marindhs:1
HIP 113535:1
Mora:1
Pegasi Sector MN-S b4-9:1
Pegasi Sector MN-S b4-7:1
-- Hadad
Col 285 Sector QM-B b14-5:1
HIP 30502:1
Col 285 Sector US-Z b14-2:1
Col 285 Sector RN-T d3-78:1
Col 285 Sector US-Z b14-7:1
Col 285 Sector KW-M c7-15:1For the first time in a while, neither any control recaptures nor any successful Alerts moving the "furthest control" borders outwards, so the original prediction stands.
One miss at Thor (again), which only placed its first five Alerts despite placing a backtrack within those five.
It's possible that the our model for how external Alerts and backtracks are budgeted isn't quite right, and there's a better model which would explain both the 5- and 6-Alert backtracking behaviour.
One miss at Thor (again), which only placed its first five Alerts despite placing a backtrack within those five.
It's possible that the our model for how external Alerts and backtracks are budgeted isn't quite right, and there's a better model which would explain both the 5- and 6-Alert backtracking behaviour.
Last edited:
Narwhal Nose report generated 14 December
-------------------------------------------
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Target: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting.
Target Distance: The distance in LY to the Maelstrom of the target. A primary component of Thargoid prioritisation.
Control Distance: The distance in LY to the Maelstrom of the attacking Control. A primary component of Thargoid prioritisation when attacking outside the control sphere.
Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a Spire are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here.
Inhabited: Whether the system contains standing human population.
-------------------------------------------
Calculating Taranis
Read 0 control systems and 999 targets.
Total connected: 0
Furthest Control: 0.000 LY
No conventional attacks possible, of course, but the 10 LY shell is now off cooldown so Taranis should have the opportunity to make an attack (or even multiple attacks?). Hupang is probably the most likely target if only a single attack is made, but others are possible.
-------------------------------------------
Calculating Leigong
Read 1 control systems and 997 targets.
Total connected: 0
Disconnected Controls
Furthest Control: 9.603 LY
We won't discover anything new at Leigong until the cooldowns expire on the other inner systems.
-------------------------------------------
Calculating Indra
Read 47 control systems and 946 targets.
Total connected: 35
Disconnected Controls
Furthest Control: 21.108 LY
Indra brushes the edge of its Control Sphere and should lose an Alert this week as a result.
-------------------------------------------
Calculating Oya
Read 24 control systems and 972 targets.
Total connected: 24
Furthest Control: 17.920 LY
Furthest potential capture: 21.188 LY
No backtracks available, so Oya should only get five Alerts this week.
-------------------------------------------
Calculating Cocijo
Read 62 control systems and 930 targets.
Total connected: 61
Disconnected Controls
Furthest Control: 21.999 LY
A normal interior week expected at Cocijo
-------------------------------------------
Calculating Thor
Read 36 control systems and 958 targets.
Total connected: 32
Disconnected Controls
Furthest Control: 18.989 LY
Furthest potential capture: 26.493 LY
The conventional model would be that Thor places the first five Alerts, then uses the backtrack placed by JA-G b11-2 to get a sixth at JA-G b11-0 - but with the last two weeks at Thor not fitting the conventional model, that should be considered a less confident prediction than normal.
(As a matter of science, continuing to close down Alerts at Thor is likely to get us the most data on external attacks)
-------------------------------------------
Calculating Raijin
Read 79 control systems and 913 targets.
Total connected: 79
Furthest Control: 27.097 LY
Normal interior week at Raijin
-------------------------------------------
Calculating Hadad
Read 49 control systems and 944 targets.
Total connected: 49
Furthest Control: 24.118 LY
A normal interior week at Hadad too.
-------------------------------------------
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Target: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting.
Target Distance: The distance in LY to the Maelstrom of the target. A primary component of Thargoid prioritisation.
Control Distance: The distance in LY to the Maelstrom of the attacking Control. A primary component of Thargoid prioritisation when attacking outside the control sphere.
Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a Spire are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here.
Inhabited: Whether the system contains standing human population.
-------------------------------------------
Calculating Taranis
Read 0 control systems and 999 targets.
Total connected: 0
Furthest Control: 0.000 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| - | - | - | Control Sphere Edge | - |
-------------------------------------------
Calculating Leigong
Read 1 control systems and 997 targets.
Total connected: 0
Disconnected Controls
| System | Distance |
| HIP 9016 | 9.602805173 |
Furthest Control: 9.603 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| - | - | - | Control Sphere Edge | - |
| HIP 9709 | 15.211 | 9.603 | HIP 9016; (backtrack Arietis Sector BQ-P b5-0) | No |
-------------------------------------------
Calculating Indra
Read 47 control systems and 946 targets.
Total connected: 35
Disconnected Controls
| System | Distance |
| 75 Tauri | 12.76477392 |
| HIP 19098 | 13.95811956 |
| Arietis Sector IG-X b1-4 | 15.09711401 |
| 76 Tauri | 15.46350921 |
| Arietis Sector HG-X b1-1 | 15.84982009 |
| Arietis Sector HG-X b1-2 | 15.8593673 |
| HIP 21179 | 16.59951642 |
| Hyades Sector NN-S b4-2 | 17.95964443 |
| Hyades Sector NN-S b4-1 | 18.37212988 |
| Hyades Sector JH-V c2-13 | 18.59377626 |
| Hyades Sector PI-S b4-3 | 19.51369211 |
| Lei Hsini | 21.10781938 |
Furthest Control: 21.108 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Arietis Sector MM-V b2-1 | 17.419 | 15.035 | HIP 20187; Gaezatorix; | No |
| HIP 22265 | 17.506 | 9.798 | Hyades Sector RT-Q b5-3; HIP 21912; Hyades Sector NN-S b4-3; etc | No |
| HIP 21475 | 18.346 | 11.498 | HIP 21112; HIP 21179; | No |
| HIP 20397 | 18.494 | 17.090 | Gaezatorix (9.952 LY); HIP 20419; | No |
| HIP 20712 | 18.554 | 11.332 | HR 1385; HIP 20350; HIP 20349; etc | No |
| - | - | - | Control Sphere Edge | - |
| HIP 20485 | 21.436 | 11.826 | 63 Tauri; | Yes |
| HIP 20890 | 21.889 | 13.186 | 64 Tauri (10.013 LY); (backtrack HIP 20815) | Yes |
| Hyades Sector ST-Q b5-5 | 21.702 | 13.569 | HIP 21912; | No |
| HIP 19157 | 21.650 | 15.097 | Arietis Sector IG-X b1-4; | Yes |
| Hyades Sector PI-S b4-2 | 22.428 | 15.464 | 76 Tauri; | No |
-------------------------------------------
Calculating Oya
Read 24 control systems and 972 targets.
Total connected: 24
Furthest Control: 17.920 LY
Furthest potential capture: 21.188 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Cephei Sector WO-A b4 | 15.395 | 8.517 | Cephei Sector WO-A b3; Lyncis Sector KX-U c2-16; HIP 10778; | No |
| - | - | - | Control Sphere Edge | - |
| Cephei Sector ZE-A c8 | 19.896 | 12.244 | HIP 10778; | No |
| Cephei Sector AV-Y b6 | 21.332 | 13.650 | Ardhri; | No |
| Cephei Sector AV-Y b0 | 23.575 | 14.331 | Cephei Sector AV-Y b3; | No |
| Cephei Sector AF-A c21 | 20.669 | 15.212 | HIP 13179; | No |
| HIP 3006 | 18.930 | 15.711 | Daruwach; | No |
| Poqomathi | 24.136 | 17.920 | HIP 8525; (backtrack BD+77 84)(backtrack Cephei Sector DQ-Y b2)(backtrack Bumbo)(backtrack HIP 2422)(backtrack Cephei Sector DQ-Y b6)(backtrack Gliese 3050) | Yes |
-------------------------------------------
Calculating Cocijo
Read 62 control systems and 930 targets.
Total connected: 61
Disconnected Controls
| System | Distance |
| Col 285 Sector WY-F b12-1 | 20.85255624 |
Furthest Control: 21.999 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Col 285 Sector WY-F b12-5 | 19.034 | 17.824 | Mapon; | No |
| Col 285 Sector ZE-P c6-10 | 20.476 | 18.409 | Col 285 Sector ZE-P c6-15; Col 285 Sector ZE-P c6-16; | No |
| HIP 38718 | 20.765 | 19.205 | Col 285 Sector ZE-P c6-16; | No |
| Col 285 Sector UN-H b11-2 | 21.222 | 18.193 | Col 285 Sector UN-H b11-4; Col 285 Sector VY-Q c5-18; Col 285 Sector UN-H b11-3; | No |
| Col 285 Sector BF-E b13-0 | 21.416 | 11.908 | Col 285 Sector OS-T d3-117; Col 285 Sector OS-T d3-144; Col 285 Sector OS-T d3-137; | No |
| Col 285 Sector KM-V d2-52 | 21.465 | 16.216 | Col 285 Sector VN-H b11-3; Col 285 Sector VN-H b11-4; Col 285 Sector VN-H b11-7 (9.935 LY); etc | No |
| Col 285 Sector ZT-F b12-2 | 21.760 | 16.728 | Col 285 Sector ZT-F b12-3; Col 285 Sector ZT-F b12-8; | No |
| - | - | - | Control Sphere Edge | - |
| Col 285 Sector VN-H b11-5 | 24.181 | 14.622 | Col 285 Sector VN-H b11-1; (backtrack Col 285 Sector VN-H b11-6) | No |
| Col 285 Sector OS-T d3-136 | 22.883 | 15.249 | Col 285 Sector OS-T d3-92; (backtrack Col 285 Sector OS-T d3-69) | No |
| Col 285 Sector VN-H b11-6 | 22.723 | 15.670 | HIP 36809; | No |
-------------------------------------------
Calculating Thor
Read 36 control systems and 958 targets.
Total connected: 32
Disconnected Controls
| System | Distance |
| Rajuarpai | 11.4695589 |
| Chanyaya | 16.10879151 |
| HIP 19894 | 16.20887223 |
| Col 285 Sector IG-O c6-14 | 17.71585625 |
Furthest Control: 18.989 LY
Furthest potential capture: 26.493 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Col 285 Sector MG-E b12-0 | 18.595 | 14.293 | Col 285 Sector MG-E b12-1; Dhang Tzela; | No |
| - | - | - | Control Sphere Edge | - |
| Col 285 Sector MG-E b12-2 | 19.631 | 9.871 | HIP 19091; | No |
| Col 285 Sector OB-E b12-4 | 21.039 | 12.054 | Col 285 Sector OB-E b12-1; | No |
| Col 285 Sector OC-V d2-96 | 22.000 | 13.139 | Col 285 Sector JA-G b11-2; (backtrack Col 285 Sector EA-Q c5-6)(backtrack Col 285 Sector OC-V d2-79)(backtrack Col 285 Sector JA-G b11-0) | No |
| HIP 18075 | 21.405 | 13.208 | Col 285 Sector IG-O c6-11; | Yes |
| Col 285 Sector OG-E b12-1 | 22.646 | 14.391 | Col 285 Sector OG-E b12-2; | No |
| Col 285 Sector LV-F b11-0 | 25.395 | 16.563 | Col 285 Sector LV-F b11-1; | No |
| Col 285 Sector JA-G b11-0 | 20.924 | 16.706 | Col 285 Sector EA-Q c5-5; (backtrack Col 285 Sector EA-Q c5-7) | No |
| Col 285 Sector SW-D b12-2 | 25.824 | 18.989 | Col 285 Sector QB-E b12-2; | No |
(As a matter of science, continuing to close down Alerts at Thor is likely to get us the most data on external attacks)
-------------------------------------------
Calculating Raijin
Read 79 control systems and 913 targets.
Total connected: 79
Furthest Control: 27.097 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Pegasi Sector LC-U b3-2 | 18.935 | 14.246 | Alads; Chnemine; HIP 116351; | No |
| Pegasi Sector JH-U b3-9 | 19.751 | 12.944 | Pegasi Sector JH-U b3-1; HIP 113535; | No |
| HIP 116360 | 20.902 | 16.841 | Pegasi Sector IH-U b3-0; Pegasi Sector BQ-Y d71; | Yes |
| Vistnero | 21.009 | 20.431 | HIP 113535; | Yes |
| Pegasi Sector DG-X c1-6 | 21.188 | 20.143 | HIP 115162; | No |
| Pegasi Sector RE-N a8-0 | 21.214 | 19.355 | Pegasi Sector VK-L a9-0; | No |
| Holvandalla | 21.476 | 16.445 | Pegasi Sector NN-S b4-10; Kaurukat; Humarala; etc | Yes |
| Pegasi Sector IH-U b3-8 | 22.044 | 18.160 | Pegasi Sector KC-U b3-6; Pegasi Sector IH-U b3-9; Pegasi Sector KC-U b3-7; | No |
| Nibelaako | 22.263 | 19.988 | Pegasi Sector IH-U b3-4; | Yes |
| Pegasi Sector PI-S b4-3 | 22.274 | 16.575 | Kaurukat; HIP 113785; | No |
-------------------------------------------
Calculating Hadad
Read 49 control systems and 944 targets.
Total connected: 49
Furthest Control: 24.118 LY
| Target | Target Distance | Control Distance | Attackers | Inhabited? |
| Col 285 Sector RH-B b14-5 | 15.324 | 12.113 | Col 285 Sector PM-B b14-0; Col 285 Sector JW-M c7-10; | No |
| Col 285 Sector RH-B b14-4 | 16.441 | 17.369 | Col 285 Sector JW-M c7-10; | No |
| Col 285 Sector KW-M c7-16 | 20.418 | 13.947 | Col 285 Sector KW-M c7-14; HIP 31223; Col 285 Sector KW-M c7-15; | No |
| Col 285 Sector OR-B b14-4 | 20.752 | 17.346 | Col 285 Sector US-Z b14-1; Col 285 Sector KW-M c7-12; Col 285 Sector SX-Z b14-0; | No |
| Col 285 Sector KW-M c7-29 | 21.254 | 13.877 | Col 285 Sector KW-M c7-4; Col 285 Sector RN-T d3-78; Col 285 Sector QM-B b14-7; etc | No |
| Col 285 Sector RM-B b14-0 | 21.388 | 15.317 | Col 285 Sector RN-T d3-78; Col 285 Sector RM-B b14-2; | No |
| Col 285 Sector SH-B b14-7 | 21.723 | 15.882 | Col 285 Sector WN-Z b14-0; | No |
| Col 285 Sector RM-B b14-4 | 21.892 | 15.344 | HIP 31223; Col 285 Sector RM-B b14-2; Col 285 Sector VS-Z b14-3; | No |
| Col 285 Sector KW-M c7-28 | 22.158 | 17.395 | Col 285 Sector QM-B b14-7; Col 285 Sector KW-M c7-30; | No |
| Col 285 Sector WN-Z b14-2 | 22.372 | 18.869 | Col 285 Sector WN-Z b14-1; Col 285 Sector SH-B b14-6; | No |
Code:
-- Recaptures above (2 if confirmed, probability otherwise; exhausts below at exactly 1)
-- Taranis
-- Leigong
-- Indra
Hyadum I:1
HIP 19263:1
HIP 19098:1
Arietis Sector EQ-Y c18:1
HR 1354:1
HIP 20679:1
-- Oya
Kanus:1
Niu Yun:1
Sambaho:1
-- Cocijo
Ulche:1
Col 285 Sector WY-F b12-3:1
Col 285 Sector VY-Q c5-15:1
Col 285 Sector VY-Q c5-17:1
HIP 38235:1
Col 285 Sector OS-T d3-143:1
-- Thor
Col 285 Sector QB-E b12-0:1
Col 285 Sector NG-E b12-5:1
Col 285 Sector NG-E b12-2:1
Col 285 Sector RW-D b12-3:1
Col 285 Sector JA-G b11-1:1
-- Raijin
Pegasi Sector DG-X c1-5:1
Snoqui:1
HIP 112823:1
Pegasi Sector PI-S b4-0:1
Pegasi Sector MY-O a7-5:1
Pegasi Sector PI-S b4-5:1
-- Hadad
HIP 29226:1
Col 285 Sector QM-B b14-1:1
Col 285 Sector KW-M c7-7:1
Col 285 Sector RM-B b14-3:1
HIP 31648:1
Col 285 Sector KW-M c7-5:1Thinking a bit about the budget and looking a bit at the available Control systems at M. Thor, then—I wonder whether attacking beyond the present radius incurs a cost to scan for targets, perhaps additional cost incurred per target found, and perhaps even a separate scanning budget. I suggest that based on Col 285 Sector JA-G b11-1, which would have squandered six scans as the fifth attacker, possibly leaving too little for a sixth attacker.
Loosely, its process could be:
- Col 285 Sector QB-E b12-0 costs one scan to find Col 285 Sector UH-C b13-2, and attacks it.
- Col 285 Sector NG-E b12-5 three scans for Col 285 Sectors NG-E b12-4, NG-E b12-3 and JA-G b11-3, attacks the latter.
- Probably Col 285 Sector NG-E b12-2 does not scan, or at most costs two to scan Col 285 Sectors OG-E b12-1 and NG-E b12-1, but may opt otherwise if it would be forced to pay four and repeat some scans. Ultimately, it attacks Col 285 Sector NG-E b12-3 scanned earlier.
- Col 285 Sector RW-D b12-3 two scans for Col 285 Sectors KB-O c6-3 and KB-O c6-2, attacks the latter.
- Col 285 Sector JA-G b11-1 six scans for Col 285 Sectors EA-Q c5-6, JA-G b11-0, OC-V d2-96, EA-Q c5-7, EA-Q c5-1 and KA-G b11-0, attacks the latter.
- Either Col 285 Sector QB-E b12-2 has no more scans to find Col 285 Sector SW-D b12-2, or the budget was common and spent too much on prior scans for a sixth attack.
- Seven inner attacks are not possible, because that would cost 70.
- Six outer attacks are not possible without attackers sharing scans, because that would cost at least 66.
- Six outer attacks were not possible here even with one sharing, because all those scans for the fifth push the sixth cost up to 71.
- Six outer attacks are achievable generally with minimum cost 56 and typical cost 64.
- Seven outer attacks are impossible, having minimum cost 65.
It could be a bit too much to hope that Ixbalan does Ixbalan things by watching the budget and making more complicated decisions such as knowing not to overspend on scanning. As usual though, if any of that inspires a more sensible idea then I am quite happy!
Last edited:
It does also seem to show that Spire recapture is not prioritised when selecting targets - NG-E b12-2 could have tried to retake OG-E b12-1 but didn't.
JA-G b11-1's attack targeting 6th of 6 (all uninhabited) is definitely a record, too, so there goes any basic "no further than 4th" sort of theory.
JA-G b11-1's attack targeting 6th of 6 (all uninhabited) is definitely a record, too, so there goes any basic "no further than 4th" sort of theory.
A slight question I have about the alert predictions -
What exactly does ‘targets’ refer to/mean for each Titan, here? I just quoted it from Taranis since it’s first up in the list and I can’t quite make sense of ‘999 targets’ while the Titan system itself is not (yet) included as a potential attacker due to uncertainties persisting around their behavior.
(Though so far it seems Hadad is not interested in covering those <10 ly gaps itself. So unless/until Leigong itself continues to misbehave, that might support the idea of them only launching alerts when exposed… but that’s another subject to be looked at in more detail starting next week, I assume, and not the one behind my query.)
Targets is the total number of non-control systems in the vicinity being considered as potential targets, which is essentially "however many rows yttrbio's spreadsheet has", and goes considerably beyond their actual short-term reach. I'll change it to "nearby systems" in future reports for clarity - it's mainly only there for my debugging anyway.
I'm sorry, I don't mean to offend you!
Why are there no such tables for Power Play?
I'm just a supporter of the theory that the Power cannot be destroyed, it's just one of the elements of the game, yes people can gather and exalt some force, but in time everything will come back to normal.
I.e. we can always (and any new player) can play in Power Play.
I think it's exactly the same plot with War with the Thargods. It will always be in the game, people will close Spires, new ones will be opened, this zone will decrease and increase.
Maybe even the developers (which I doubt) will make it possible to destroy the mothership, but I think in this case another one will arrive immediately.
This is necessary so that any new player who came to the game could also participate in the AX zones conflict, save people from the titan, infect spires, etc.
I don't think any player is interested in fighting a Forever War. As of yet we simply can't destroy the titans because FD didn't implement a way to do so, but at some point that will have to change. Pushing the goids back and keeping them down requires a constant effort by players who know what they are doing. If these players at one point conclude that it's all futile because success will never be possible, many of them will lose interest and stop.
I reckon that Frontier closely monitors weekly player involvement and introduces changes not necessarily when they make the most narrative sense, but when players threaten to lose interest and need to be thrown a bone to stay engaged.
But if players conclude that the big prize can never be attained, they will stop to be lured by little treats.
I think it's high time FD enabled us to take out the naked maelstroms. The current situation is a bit like a "June 1945, the Nazi forces are all but destroyed, the Soviet army stands at the gates of Berlin but can never capture the city".
I reckon that Frontier closely monitors weekly player involvement and introduces changes not necessarily when they make the most narrative sense, but when players threaten to lose interest and need to be thrown a bone to stay engaged.
But if players conclude that the big prize can never be attained, they will stop to be lured by little treats.
I think it's high time FD enabled us to take out the naked maelstroms. The current situation is a bit like a "June 1945, the Nazi forces are all but destroyed, the Soviet army stands at the gates of Berlin but can never capture the city".
Last edited:
I expect that comparable tables do exist but, as Powerplay is competitive between 11 groups of players, they'll be securely locked away where the other sides can't see them.
Powerplay's information requirements are also somewhat different, and it doesn't have the same geographic constraints, so they wouldn't look that similar, I expect.
Powerplay is a bit different in that there aren't any moves being taken there except the ones of players. So wiping out a Power so it only holds its HQ is theoretically possible (though practically impossible so long as the Power has supporters) and it wouldn't recover from that until it got supporters again.
It's possible that in those circumstances Frontier might manually remove the power to replace it with one with more ability to attract supporters, of course. Powerplay would continue but there's no reason that Zemina Torval has to be a Power in perpetuity (and the original design did allow for individual Powers to be destroyed and replaced - it was just never implemented)
Certainly it's unlikely that they'll have spent all this time developing these new features and environments with the intent that they'll be a short-term thing to disappear forever at the end of the storyline.
That said, the strategic layer in itself only has a point if it actually does anything: titans, spires, conflict zones, etc. could all be set up far more simply as permanent environments without it. If it can't be "won" (even on a purely local level in terms of repelling a Titan temporarily, and it goes to recharge and then comes back later) and it can't be "lost" (it would take years for anywhere of importance to be threatened even if every player ignored it completely from today) then the automation isn't really achieving anything.
And what makes you think they don’t intend to have the Thargoids push back so it actually makes narrative sense for the Nemesis Failsafe to exist instead of it being able to head into deep space and nobody would care as the Thargoids were fended off without him?
(That’s also not too much a subject for an analysis thread, besides, I don’t quite believe it will just be as simple as “You bested the Titans, great, now go back to whatever it was you were doing”.)
I also find it hard to believe that they've built all this stuff just for the players to win and for the thargoid content to go away.
But who knows, maybe we will actually win the war and find away into some locked region full of titans and spire sites, or alternatively there will be even more thargoids coming to the bubble to help the failing titans.
But who knows, maybe we will actually win the war and find away into some locked region full of titans and spire sites, or alternatively there will be even more thargoids coming to the bubble to help the failing titans.
Looking a bit more at the outer attack behaviour and outlining a few more ideas:
Then, consider attackers—
Being a scanner, Ixbalan can attack only Hyades Sector PN-T c3-8, but it found so many other targets that the remaining four attacks seem to be all expended first, as if its staged attack had to wait.
Interestingly with M. Thor week 54, Col 285 Sector NG-E b12-5 reveals targets for Col 285 Sector NG-E b12-2; I think it holds fire because it has additional targets of its own, then its scan leaves it staged with Col 285 Sector NG-E b12-3 anyway. Either way, five scans reveal over a dozen targets without enough attackers, then poor Col 285 Sector QB-E b12-2 has no scan to use.
M. Thor week 53 really got me thinking, although I cannot quite make it work alongside Ixbalan. The turns to scan must have reached Col 285 Sector EA-Q c5-5 eventually, which answered the foreknowledge question by means of HIP 19894 not scanning and instead attacking Col 285 Sector SM-C b13-0 due to having nothing else it could illuminate during the Chanyaya scan. The big puzzle is why HIP 21125 was attacked instead of Col 285 Sector EA-Q c5-7; at first it seems potentially obvious that the non-scanner Col 285 Sector JA-G b11-1 was present to steal the attack against the closer system, but that fails to explain why it withheld attacking earlier during the first scan from Col 285 Sector JA-G b11-2.
That whole idea needs a special order of events to hold, exclusivity for the scanner targets, and also a bit of intelligence applied at the end. Col 285 Sector JA-G b11-2 scans and readies to strike Col 285 Sector EA-Q c5-8, but neither Col 285 Sector EA-Q c5-5 nor Col 285 Sector JA-G b11-1 attack yet because both have more targets to be revealed via scans of their own. At minimum due to Ixbalan, the staged attack waits until scanning is complete. After that:
Apologies for the incompleteness; it is all with hope for inducing inspiration!
One quite good speculation is exactly that said region could be Col 70 Sector, the general direction from which the moving Titan signals originated! Precise sector aside, I imagined it possible that the Thargoid empire is revealed somewhere around achieving a very difficult fourth Titan depletion.
Having been much of the cause of said Titan-failing, my more immediate expectation was somewhere in between; we reach an impasse for now, Galnet acknowledges that the lone Titan is still functioning, and perhaps a foreshadowed weakness is identified but without an immediate way to exploit it. Later updates make Titan research relevant for achieving something like a modified Seismic Charge, meanwhile we have to rescue all survivors while stopping Scythes from attacking nearby ports and taking more, then perhaps finally destabilise one Titan with enough targeted detonations. I imagine that also having layers, such as the detonations just stopping the Hazardous Environment so that Guardian weapons can be used to strike it.
While that absolutely could still happen, the irksome short-term issue is that a Titan has now attacked despite declining the opportunity for months, and I have no basis to ask anyone for their time to help achieve anything like that again if it does not at least pacify the attacks!
- With M. Taranis week 44 and M. Thor weeks 53 and 54, it looks a bit as if Control systems have to perform scans to find outer targets.
- Assess may be a better verb, given that find implies wasting a lot of scans which would make outer attacks far more rare than they have been.
- I think the scans could be the limiting factor; five-target rules seemed to have at most four scans, with fewer per inner attack.
- It is as if the Titan has to spend one scan for a long-range illumination of one target, without prior knowledge of whether any more targets exist, thus expending a scan when it reaches its perimeter.
- Conversely, clearly individual Control systems do know not to waste a scan if no valid target will be seen.
- It looks as if a Control system scan works outwards by Titan distance, and leaves it locked onto that final, outermost target.
- I think non-scanning attackers may be attacking outer targets normally, nearest-first from those revealed targets each can see.
| Scanner | Target | Distance |
| Hyades Sector HW-W d1-52 | Hyades Sector CV-O b6-4 | 23.212104 |
| Ixbalan | Hyades Sector PN-T c3-7 Hyades Sector PN-T c3-5 Hyades Sector PN-T c3-8 | 22.903457 23.218161 23.972111 |
| Hyades Sector FB-N b7-2 | Hyades Sector KH-L b8-0 | 22.760128 |
Then, consider attackers—
| Target | Distance | Attackers |
| Hyades Sector KH-L b8-0 | 22.760128 | Hyades Sector FB-N b7-2 |
| Hyades Sector PN-T c3-7 | 22.903457 | Ixbalan Hyades Sector DQ-O b6-3 Hyades Sector GW-W d1-99 |
| Hyades Sector CV-O b6-4 | 23.212104 | Hyades Sector HW-W d1-52 |
| Hyades Sector PN-T c3-5 | 23.218161 | Ixbalan Hyades Sector DQ-O b6-3 Hyades Sector GW-W d1-99 |
| Hyades Sector PN-T c3-8 | 23.972111 | Ixbalan |
Being a scanner, Ixbalan can attack only Hyades Sector PN-T c3-8, but it found so many other targets that the remaining four attacks seem to be all expended first, as if its staged attack had to wait.
Interestingly with M. Thor week 54, Col 285 Sector NG-E b12-5 reveals targets for Col 285 Sector NG-E b12-2; I think it holds fire because it has additional targets of its own, then its scan leaves it staged with Col 285 Sector NG-E b12-3 anyway. Either way, five scans reveal over a dozen targets without enough attackers, then poor Col 285 Sector QB-E b12-2 has no scan to use.
M. Thor week 53 really got me thinking, although I cannot quite make it work alongside Ixbalan. The turns to scan must have reached Col 285 Sector EA-Q c5-5 eventually, which answered the foreknowledge question by means of HIP 19894 not scanning and instead attacking Col 285 Sector SM-C b13-0 due to having nothing else it could illuminate during the Chanyaya scan. The big puzzle is why HIP 21125 was attacked instead of Col 285 Sector EA-Q c5-7; at first it seems potentially obvious that the non-scanner Col 285 Sector JA-G b11-1 was present to steal the attack against the closer system, but that fails to explain why it withheld attacking earlier during the first scan from Col 285 Sector JA-G b11-2.
That whole idea needs a special order of events to hold, exclusivity for the scanner targets, and also a bit of intelligence applied at the end. Col 285 Sector JA-G b11-2 scans and readies to strike Col 285 Sector EA-Q c5-8, but neither Col 285 Sector EA-Q c5-5 nor Col 285 Sector JA-G b11-1 attack yet because both have more targets to be revealed via scans of their own. At minimum due to Ixbalan, the staged attack waits until scanning is complete. After that:
- Col 285 Sector OG-E b12-2 then stages Col 285 Sector OG-E b12-0.
- Chanyaya stages Col 285 Sector JG-O c6-5 and reveals Col 285 Sector SM-C b13-0, to be attacked immediately by HIP 19894 with nothing else of its own to find.
- Col 285 Sector LV-F b11-1 stages HIP 19600.
- Finally Col 285 Sector EA-Q c5-5 stages Col 285 Sector EA-Q c5-7, revealing again those targets Col 285 Sector JA-G b11-1 let slip earlier, but additionally with HIP 21125 this time. Despite being able to reveal Col 285 Sector KA-G b11-0 were it to scan, Col 285 Sector JA-G b11-1 attacks HIP 21125 immediately because the scans are now depleted.
- It cannot just be that the farthest scanner misses, otherwise Ixbalan would attack Hyades Sector PN-T c3-8.
- It cannot just be that the farthest target is missed, otherwise Chanyaya would miss Col 285 Sector JG-O c6-5.
- Notably Col 285 Sector IG-O c6-14 is also present here, but it cannot be simple target-stealing because Col 285 Sector EA-Q c5-7 would have been attacked.
Apologies for the incompleteness; it is all with hope for inducing inspiration!
One quite good speculation is exactly that said region could be Col 70 Sector, the general direction from which the moving Titan signals originated! Precise sector aside, I imagined it possible that the Thargoid empire is revealed somewhere around achieving a very difficult fourth Titan depletion.
Having been much of the cause of said Titan-failing, my more immediate expectation was somewhere in between; we reach an impasse for now, Galnet acknowledges that the lone Titan is still functioning, and perhaps a foreshadowed weakness is identified but without an immediate way to exploit it. Later updates make Titan research relevant for achieving something like a modified Seismic Charge, meanwhile we have to rescue all survivors while stopping Scythes from attacking nearby ports and taking more, then perhaps finally destabilise one Titan with enough targeted detonations. I imagine that also having layers, such as the detonations just stopping the Hazardous Environment so that Guardian weapons can be used to strike it.
While that absolutely could still happen, the irksome short-term issue is that a Titan has now attacked despite declining the opportunity for months, and I have no basis to ask anyone for their time to help achieve anything like that again if it does not at least pacify the attacks!
Exactly why i figure one of the following happens:
- we eventually get a way to defeat the Titans or make them dormant, which translates to one of:
--- they eventually go active again, or,
--- new ones are sent to replace on a routine basis
... which means we just get perpetual churn of things in the war... or
- we win the war, and push them out the bubble. But, we get the Thargoid regions unlocked (e.g cone sector) which have comparable things, across those whole sectors, and people can dip in and out as they like.
Yeah games having an end instead of an endless grind is unimaginable nowdays.
It's unfortunately somewhat in opposition with wanting the galaxy to actually change more permanently which doesn't just mean always adding more stuff.
That's right.
You always have to think about the game from the perspective of newcomers coming into the game after a year.
I personally just consider these add-ons as DLCs.
I just bought the game, I want to go into the DLC guards, flew to Ram Tah and took the quest for the obelisks.
Same with the DLC of the war with Thargoids, I want to go there, I don't want to go there.
But that's the Elite genre's whole bag; there isn't an end... it's just endless procedurally generated stuff... and where ED kinda dropped the ball.
They didn't lean hard enough into the procedural, and instead erred on GM-injected content, requiring significantly more effort longer term, for significantly less impact.
Last edited: