Hi how I told here: A-Bot for Capitals and Motherships
Im trying to configure A-Bot to work with captials and mothership.
But I found an possible “API error”.
The “Probe Scanner Window” is not under " WindowProbeScanner but we find it under "WindowOther.
Into the AnomalyEnter.cs we found this:
var probeScannerWindow = memoryMeasurement?.WindowProbeScanner?.FirstOrDefault();
but this not work because the measurement of WindowProbeScanner is empty…
it’s possible fix that?
To make more understable the issue and my question I report this screen:
How you can see the Window of probe scanner is indexed under the structure “WindowOther” and not into the “WindowProbeScanner” this make the probeScannerWindow and the relative result null.
I think this is done by the new version of “Probe Scanner Window” of eve, but Idk how I can fix this.
So… @Viir can you help me or just fix the index so I can continue to work to make A-Bot compatible with Carriers and Motherships?
Problem Fixed, the issue was on my window configuration on the client, the probe scanner window have to be alone and not grouped.
But now I have another problem… now the code get correctly the list of anomaly, but he do not go to the anomaly, he stay in stuck with this operations:
3 leaves 2 s ago at 02:20:15
(BotTask->EnableInfoPanelCurrentSystem)
Effect(BotTask->BotTask)
(BotTask->UndockTask)