Rescues and/or undetermined activity X apply to all controls outside a certain radius, but non-barnacle systems cannot progress beyond 85% this way, while barnacle systems can.
But no, that doesn't work for Cocijo. So maybe...
Rescues apply to all counterstrike systems still?
Undetermined activity X applies to controls outside a certain radius?
What does not work for M. Cocijo? If you refer to the Counterstrike systems completion, it will help a lot to know that it was an INIV sweep, caused by neither Titan rescues nor Matrix activity! Assuming so, I presume that leaves the hypothesis that Matrix activity also affects (by some means) Peripheral systems (however defined) until 85% is reached, even if they are ahead, and in precise strength proportion.
On those parenthesised points, I am much more interested in the former over the latter; deducing affected systems could be fun, but we can see them already quite clearly when listed, so that is very much secondary compared to knowing whether they are hindering Matrix progress until they reach 85% or if we enjoy that 85% regardless. The decision-making impact is large; hindrance means we should act swiftly on Thursday–Friday to relieve that burden, whereas bonus progress means we should leave it until Tuesday–Wednesday.
All right, including the INIV sweep, I think what we have is consistent with the following hypothesis:
Each week, a radius around the titan is determined, which at least correlates with the number of control systems (more control systems means higher radius)
Titan-wide progress is applied to ALL control systems outside that radius, but cannot progress non-spire control systems past 85%
This titan-wide progress does NOT scale with system difficulty.
Titan-wide progress is caused by titan rescues, and likely can also be caused by certain activities related to the spire systems, though which ones is not clear at this time. Possibilities include:
A. Killing stuff (or maybe only certain kinds of enemies, like Orthrus or Banshees)
B. Turning in spire goods to Palin/Baird
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
Name: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation. 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 barnacle matrix 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.
Last week's prediction was again all correct, so other than a note about our known issue at Taranis, no changes to the algorithm are planned. This week is predicting a record low of just four inhabited targets. Doesn't seem to be any way to get that down to three without some ridiculously large strikes on either Oya or Raijin, but the containment strategies are clearly being effective.
-------------------------------------------
Calculating Taranis
Read 28 control systems and 965 targets.
Total connected: 27 Disconnected Controls
Yet again we're in a position where Ixbalan should be able to attack PN-T c3-8, but probably won't. Ixbalan going for PN-T c3-5 allowing a fifth backtracked Alert onto PN-T d3-7 seems more likely, for the targets highlighted in green. Of course, a lot of the systems involved in the PN-T side of Taranis are fringe ones it might well lose this week if last week's periphery attack continues, so this is probably going to need revising anyway.
-------------------------------------------
Calculating Leigong
Read 24 control systems and 970 targets.
Total connected: 24
Straightforward five inner attacks at Leigong this week.
-------------------------------------------
Calculating Indra
Read 86 control systems and 907 targets.
Total connected: 84 Disconnected Controls
System
Distance
Arietis Sector JM-T a4-0
25.94015423
Arietis Sector NS-R a5-1
26.00619668
Furthest Control: 27.394 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
71 Tauri
15.082
9.009
HIP 20086 (9.925 LY); HIP 20350; HIP 20916; etc
No
79 b Tauri
19.444
17.089
HIP 20916; HR 1358;
No
Scythia
20.227
13.254
Arietis Sector EQ-Y c18; HIP 20187; Gaezatorix; etc
Yes
HIP 20815
21.704
17.806
HIP 20577; HIP 20679; HR 1358;
No
HIP 20890
21.889
17.871
HIP 20679;
Yes
HIP 20616
22.168
22.042
HR 1358;
Yes
Arietis Sector NH-V b2-0
22.472
18.655
Obamumbo;
No
Hyades Sector ON-S b4-6
22.610
22.272
HIP 21918; Ross 378; Hyades Sector ON-S b4-7;
No
Arietis Sector JR-V b2-3
23.081
16.450
HIP 20480;
No
HIP 20491
23.341
15.974
HIP 19934 (10.022 LY); Arietis Sector NS-R a5-1;
Yes
Also straightforward at Indra
-------------------------------------------
Calculating Oya
Read 26 control systems and 969 targets.
Total connected: 24 Disconnected Controls
System
Distance
Liu Huang
17.75687587
Akbakara
18.17006789
Furthest Control: 18.170 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
-
-
-
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; (backtrack Cephei Sector AV-Y b2)(backtrack HIP 4041)
No
Cephei Sector AV-Y b0
23.575
14.331
Cephei Sector AV-Y b3;
No
Luggerates
21.962
14.713
Sambaho; (backtrack HIP 3006)
Yes
HIP 11111
24.118
15.212
HIP 13179;
Yes
HIP 3006
18.930
15.711
Daruwach; (backtrack Aowicha)
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
AV-Y b6 places some backtracks nothing else is in a position to use, but Sambaho's backtrack can be picked up by Daruwach to attack HIP 3006. HIP 11111 should therefore be skipped this time.
-------------------------------------------
Calculating Cocijo
Read 67 control systems and 925 targets.
Total connected: 66 Disconnected Controls
System
Distance
Col 285 Sector WY-F b12-1
20.85255624
Furthest Control: 28.116 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector ZE-P c6-15
18.409
9.869
Col 285 Sector OS-T d3-96; Mapon;
No
Col 285 Sector ZE-P c6-16
19.205
17.824
Mapon;
No
Col 285 Sector UN-H b11-3
19.395
13.304
Col 285 Sector SS-H b11-7;
No
Col 285 Sector SS-H b11-5
20.306
12.899
Col 285 Sector SS-H b11-1; Col 285 Sector VY-Q c5-15; Col 285 Sector SS-H b11-6; etc
No
Col 285 Sector SS-H b11-4
20.309
14.428
Col 285 Sector VY-Q c5-15; Col 285 Sector SS-H b11-6;
No
Col 285 Sector KM-V d2-69
23.672
17.774
Col 285 Sector SS-H b11-6; Col 285 Sector KM-V d2-109;
Yes
Col 285 Sector YY-F b12-0
23.772
23.150
Col 285 Sector XY-F b12-6;
No
Col 285 Sector YT-F b12-7
23.878
24.231
Col 285 Sector YT-F b12-2;
No
Col 285 Sector US-H b11-2
24.101
21.295
Col 285 Sector TS-H b11-4; Col 285 Sector US-H b11-3;
No
Col 285 Sector UN-H b11-6
24.140
16.621
Ulche;
No
Standard inner attacks set here.
-------------------------------------------
Calculating Thor
Read 46 control systems and 946 targets.
Total connected: 40 Disconnected Controls
Calculating Hadad
Read 54 control systems and 940 targets.
Total connected: 54
Furthest Control: 24.118 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector KW-M c7-12
17.571
13.132
Col 285 Sector US-Z b14-2; Col 285 Sector KW-M c7-30;
No
Col 285 Sector RM-B b14-2
18.164
15.317
Col 285 Sector RN-T d3-78; Col 285 Sector RM-B b14-3;
No
Col 285 Sector VS-Z b14-0
18.841
10.064
Col 285 Sector US-Z b14-7; HIP 31223; Col 285 Sector KW-M c7-15;
No
Col 285 Sector WN-Z b14-5
21.482
16.067
Col 285 Sector KW-M c7-15;
No
Col 285 Sector RM-B b14-4
21.892
15.344
HIP 31223; Col 285 Sector RM-B b14-3; Col 285 Sector VS-Z b14-3;
No
Col 285 Sector SX-Z b14-2
22.853
19.079
Col 285 Sector SX-Z b14-0;
No
Col 285 Sector VS-Z b14-6
23.515
24.118
Col 285 Sector VS-Z b14-3;
No
Col 285 Sector NR-B b14-1
23.674
19.276
Col 285 Sector PM-B b14-1;
No
-
-
-
Control Sphere Edge
-
Col 285 Sector OR-B b14-9
25.303
17.550
Col 285 Sector KW-M c7-30;
No
Col 285 Sector OB-D b13-1
24.332
17.575
Col 285 Sector SH-B b14-4; (backtrack Col 285 Sector OB-D b13-0)
No
And similarly here, though recent recaptures have pushed the Control Sphere Edge in somewhat to the point where some Hadad weeks might hit it. Not this time, though.
Code:
-- Recaptures above (2 if confirmed, probability otherwise; exhausts below at exactly 1)
-- Taranis
Trianguli Sector EQ-Y b0:1
HR 1737:1
Hyades Sector EG-N b7-1:1
Hyades Sector GB-N b7-2:1
-- Leigong
Arietis Sector NX-U c2-20:1
Arietis Sector WJ-R b4-1:1
Arietis Sector MX-U c2-19:1
Hyades Sector KN-K b8-2:1
Hyades Sector KN-K b8-3:1
-- Indra
HR 1385:1
63 Tauri:1
64 Tauri:1
Hyadum I:1
HR 1354:1
-- Oya
Cephei Sector WO-A b3:1
Akbakara:1
Cephei Sector AF-A c9:1
Kanus:1
-- Cocijo
Col 285 Sector WY-F b12-3:1
Col 285 Sector OS-T d3-143:1
Col 285 Sector UN-H b11-4:1
Col 285 Sector VY-Q c5-17:1
Col 285 Sector VY-Q c5-18:1
-- Thor
Col 285 Sector OB-E b12-1:1
Chanyaya:1
Col 285 Sector EA-Q c5-5:1
Col 285 Sector RW-D b12-3:1
Col 285 Sector JA-G b11-1:1
-- Raijin
Alads:1
Pegasi Sector JH-U b3-1:1
Pegasi Sector MY-O a7-5:1
Pegasi Sector IH-U b3-4:1
Sholintet:1
-- Hadad
HIP 30502:1
Col 285 Sector KW-M c7-14:1
Col 285 Sector US-Z b14-1:1
Col 285 Sector KW-M c7-4:1
Col 285 Sector QM-B b14-7:1
All right, including the INIV sweep, I think what we have is consistent with the following hypothesis:
Each week, a radius around the titan is determined, which at least correlates with the number of control systems (more control systems means higher radius)
Titan-wide progress is applied to ALL control systems outside that radius, but cannot progress non-spire control systems past 85%
This titan-wide progress does NOT scale with system difficulty.
Action so far at Taranis is interesting:
- the Spire systems ended last week at 90%, were reinforced to 57%, and have since risen to 62%
- the non-Spire systems ended at 85%, were reinforced to 52%, and have since risen to 56%
- Hyades Sector HW-M b7-3, the next system in, is now showing 4% progress as well, consistently with Taranis being two Controls down on last week.
There was likely some non-pod recovery activity at the spire sites around Leigong - I myself was busy at the site in Hyades Sector NT-I b9-4, and there probably will have been a few other players. Though my actions were not enough to account for a full percent of progress, most likely.
Hmm. Noting that Thor's boundary is in a slightly different place this week - Col 285 Sector OC-V d2-79 isn't affected, despite no Controls changing hands at Thor last week - I thought to check the Alert progress as well ... and the Alerts outside the boundary also have 2% progression (excluding the one which was actually completed), which would have been concealed by last week starting this process on Monday after most Alerts were clear.
The same appears true - or a massive coincidence - counting the outer Alerts at Taranis, while Raijin's alerts are all safely on the interior as it gets going this time.
A simple rule of boosting the ten outermost systems - whatever of Alert, Invasion, Control or Spire state they're in - might be the answer.
(With some very interesting implications if true...)
Following up on a report of 1200 titan rescues from Cocijo, I scoped out a few systems:
Combined with Dark Session's 720 Leigong pods last week giving 1.10% progress, this looks like roughly the same rate. So "Titan rescues give progress to the outer 10 systems" is looking solid so far.
So that suggests - assuming recaptured spires stay recaptured this time, of course! - an efficient approach to destroying Leigong could be as follows:
- recapture any three of FG-Y d38, HIP 7819, HIP 7277 and WJ-R b4-1 normally (HIP 7277 looks like the one to leave for later, from the map)
- that guarantees that KN-K b8-3 will be brought into periphery-attack range, so the following week do a large-scale periphery attack to take it (and the more distant ones) out
- clean up the rest of the HIP 8033 cluster before it can bring KN-K b8-3 back on line (ideally also knocking out AQ-P b5-0 to stop it reactivating its spire, though it's not a disaster if it does). With the right order of action this could be spread out over at least six weeks.
- knock out (almost?) all the remaining low-strength controls on the ZE-R b4-3 cluster to bring the two stronger ones and two spires on that side into periphery range
- a second "periphery" attack destroys the remaining spires and makes completion of the remaining two controls much more straightforward
Re: Difficulty, given that Cocijo this week and Leigong last week had roughly equivalent progress from titan rescues, and that Leigong's included a once-populated system at 17.61 ly, while Cocijo this week is all unpopulateds no closer than 22.72 ly, I'm guessing that it does not scale with the difficulty of the systems being moved. That said, contributions from Spire activities could scale with the difficulty of the spire being interacted with.
A bit of an experiment here with putting some more of the routine information onto the connection maps. Taranis has now been cut up into lots of little pieces and the remaining big cluster isn't formally connected to a spire - though it'll be interesting to see what happens with HW-M b7-4 later. On the predictive side, Ixbalan will not be placing usable backtracks anymore so it's probably down to 4 Alerts next week. But will that affect where it attacks in the first place?
As noted above, Ixbalan's backtrackers are gone, so only four attacks expected this week. On previous form, Ixbalan will go for c3-5 rather than c3-8, though we still don't understand why.
Slight change in the top 5 at Leigong with most of its attacks this week coming from Spire systems.
-------------------------------------------
Calculating Indra
After recaptures, read 73 control systems (86 originally) and 907 targets.
Total connected: 73
Furthest Control: 25.780 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
71 Tauri
15.082
9.009
HIP 20086 (9.925 LY); HIP 20350; HIP 20916; etc
No
79 b Tauri
19.444
17.089
HIP 20916; HR 1358;
No
Scythia
20.227
13.254
Arietis Sector EQ-Y c18; HIP 20187; Gaezatorix; etc
Yes
HIP 20815
21.704
17.871
HIP 20679; HR 1358;
No
HIP 20616
22.168
22.042
HR 1358;
Yes
Hyades Sector ON-S b4-6
22.610
22.272
HIP 21918; Ross 378;
No
Arietis Sector JR-V b2-3
23.081
16.450
HIP 20480;
No
HIP 20491
23.341
15.974
HIP 19934 (10.022 LY);
Yes
HIP 19757
24.520
17.955
HIP 20419;
Yes
HIP 21788
24.693
23.647
Hyades Sector AR-J a10-0;
No
Indra's connectivity means that recaptures making an immediate difference are rare - they're usually more important for their effect in a month's time - but it happens this week, with HIP 20616 coming into the top 5 to replace HIP 20890.
Col 285 Sector JA-G b11-2; (backtrack Col 285 Sector OC-V d2-96)
No
Col 285 Sector SM-C b13-0
21.776
16.209
HIP 19894;
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-3
26.122
17.210
Col 285 Sector NG-E b12-5;
No
Col 285 Sector NG-E b12-1
22.991
17.596
Col 285 Sector NG-E b12-2;
No
Col 285 Sector SW-D b12-2
25.824
18.989
Col 285 Sector QB-E b12-2;
No
Col 285 Sector IG-O c6-18
25.852
19.631
Col 285 Sector MG-E b12-2;
No
Col 285 Sector OC-V d2-96
22.000
20.096
Col 285 Sector EA-Q c5-6; (backtrack Col 285 Sector EA-Q c5-9)(backtrack Col 285 Sector EA-Q c5-2)(backtrack Col 285 Sector EA-Q c5-1)(backtrack Col 285 Sector KA-G b11-0)
No
Col 285 Sector EA-Q c5-10
27.378
20.882
Col 285 Sector OC-V d2-79 (9.923 LY);
No
Thor loses a bunch of outer controls, pushing its edge in, which sets it into outer mode immediately.
First four, then the backtrack to OC-V d2-96, is the expected pattern.
-------------------------------------------
Calculating Raijin
After recaptures, read 79 control systems (86 originally) and 906 targets.
Total connected: 79
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
Name: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation. 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 barnacle matrix 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.
As expected, the model again had Ixbalan going for c3-8 whereas it actually went for c3-5. Without other examples it's hard to think of reasons for this - and there's a good chance of Ixbalan being recaptured before it happens again - so no changes to the model yet. All other predictions last week fit the model.
-------------------------------------------
Calculating Taranis
Read 20 control systems and 973 targets.
Total connected: 7 Disconnected Controls
Taranis has been thoroughly disconnected from its remaining Spires, making the "disconnected" list include most of its systems. Only four Alerts expected this week though if there's another periphery run that might fall further.
-------------------------------------------
Calculating Leigong
Read 21 control systems and 972 targets.
Total connected: 21
Is there any quick and easy way to tell what that magical discount value is at a given time? I am refering to that number that caps at 85% and is raised by rescueing pods from the Titans and doing things at the spires.
I just slowly begin to make some sense of things...
Is there any quick and easy way to tell what that magical discount value is at a given time? I am refering to that number that caps at 85% and is raised by rescueing pods from the Titans and doing things at the spires.
Go to https://dcoh.watch/systems
Set the filters to show Control, Alert and Invasion only
Enable the optional "distance to Titan" column and sort descending by it (so the furthest systems are at the top)
Set the filters to show only a single Maelstrom at a time
Make sure the two "Hide" checkboxes are turned off, and the Features filter is all turned on.
The discount value is then the lowest percentage reached by the first ten listed systems in that Maelstrom.
(Switch to the next Maelstrom in the filters to check the rest.)
So at time of writing this gives 14% for Raijin, 36% for Oya, 100% for Taranis, etc.
Note that the order of events is significant - it's not a discount as such, just a capped and indirect way of adding progress to systems: 85% indirect activity followed by 15% direct activity will complete the system. 15% direct activity followed by 85% indirect activity will leave the system at 85% complete.
Go to https://dcoh.watch/systems
Set the filters to show Control, Alert and Invasion only
Enable the optional "distance to Titan" column and sort descending by it (so the furthest systems are at the top)
Set the filters to show only a single Maelstrom at a time
Make sure the two "Hide" checkboxes are turned off, and the Features filter is all turned on.
The discount value is then the lowest percentage reached by the first ten listed systems in that Maelstrom.
(Switch to the next Maelstrom in the filters to check the rest.)
So at time of writing this gives 14% for Raijin, 36% for Oya, 100% for Taranis, etc.
Note that the order of events is significant - it's not a discount as such, just a capped and indirect way of adding progress to systems: 85% indirect activity followed by 15% direct activity will complete the system. 15% direct activity followed by 85% indirect activity will leave the system at 85% complete.
Gosh. Thanks for that answer. I can follow your steps - but I really am afraid to ask how the heck you made all this data happen. Great work. Really appreaciated. And thanks for those "easy" steps. This helps.
The site is Dark Session's work, not mine - nowadays the data feed I think is mainly from the journals but in the early days there was a whole set of screenshot OCR tools to get them together. All very impressive, I agree.
Indra: Action doesn't change the primary prediction ... but it's close - the Control Sphere Edge is now positioned after the 8th target. It's likely to get rather more immediate consequences from further system losses.
Oya: Liu Huang was closer in than HIP 8525 is closer than Akbakara, so the recapture moves Poqomathi up into the attack zone as the backtrack is still valid.
(This prediction somewhat uncertain as Poqomathi is selected based on a single precedent several months ago also from the HIP 8525/HIP 7338 cluster)
Target
Target Distance
Control Distance
Attackers
Inhabited?
-
-
-
Control Sphere Edge
-
Cephei Sector FB-X b1-1
20.261
12.495
Kanus;
No
Cephei Sector AF-A c22
21.188
12.692
Niu Yun (9.908 LY);
No
HIP 11111
24.118
15.212
HIP 13179; (backtrack Cephei Sector AF-A c21)
Yes
Cephei Sector AF-A c21
20.669
15.681
Cephei Sector AF-A c9;
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
HIP 21386
20.509
18.170
Akbakara;
No
Cocijo: even worse than Indra - the CSE comes back to position 5, losing it an attack.
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector YT-F b12-6
20.034
17.688
Col 285 Sector WY-F b12-3;
No
Mahlina
21.146
15.964
Col 285 Sector VY-Q c5-17; Col 285 Sector WY-F b12-1;
Yes
Col 285 Sector ZT-F b12-8
21.247
16.728
Col 285 Sector ZT-F b12-3;
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 XT-Q c5-6
25.235
16.365
Col 285 Sector VN-H b11-4; (backtrack Col 285 Sector VN-H b11-0)
No
Col 285 Sector XT-Q c5-2
24.746
16.621
Ulche; (backtrack Col 285 Sector XT-Q c5-1)(backtrack Col 285 Sector UN-H b11-6)
No
Col 285 Sector VN-H b11-0
25.038
17.735
Col 285 Sector VN-H b11-7;
No
Col 285 Sector KM-V d2-69
23.672
17.774
Col 285 Sector SS-H b11-6; (backtrack Col 285 Sector QX-H b11-2)
Yes
Paitra
24.880
18.193
Col 285 Sector UN-H b11-4; (backtrack HIP 36901)(backtrack Col 285 Sector WT-Q c5-22)
Yes
Col 285 Sector RS-H b11-6
26.660
18.572
Col 285 Sector VY-Q c5-18; (backtrack Col 285 Sector SS-H b11-2)(backtrack Col 285 Sector VY-Q c5-19)
No
Thor: down to four attacks
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 NG-E b12-3
24.094
17.596
Col 285 Sector NG-E b12-2; (backtrack Col 285 Sector NG-E b12-4)(backtrack Col 285 Sector NG-E b12-1)
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-1)
No
Col 285 Sector SW-D b12-2
25.824
18.989
Col 285 Sector QB-E b12-2;
No
Raijin: gets away with no high-end changes this week, but since everyone else is getting reprinted, why not.
Target
Target Distance
Control Distance
Attackers
Inhabited?
Nu Guang
19.330
11.760
Snoqui;
Yes
HIP 116360
20.902
16.841
Pegasi Sector IH-U b3-0; Pegasi Sector BQ-Y d71;
Yes
Vistnero
21.009
21.106
Pegasi Sector MY-O a7-5;
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;
