No offese from me, I collaborated to realize the logic of A-Bot, but the architetture of it it’s made by @Viir, however I agree about the prioritization logic, for this I have in plan to work on it.
But Im not working on A-Bot, precisally Im rewriting some A-Bot functions for make it working with capitals and mothership, my coding it’s actually in a private repository where I update the various status here: A-Bot for Capitals and Motherships
What I can do to “help you” is to share the code for the priority targhet, when I finish the project
My plan is to make all damage to frigates, then cruisers and then bs, the project it’s to recalculate the primary when the actually primary is dead, this will give to A-Bot a dinamic primary calculation, plus another function to check “webs and point” if someone point or web the ship then will switch primary.
This is what I can do for help you, but before do it I have to finish the squadrons integration, atm Im able to launch and retreat all squadrons, tonight/tomorrow I will work for make them shoot on the primary, then I will work on the code for the dinamic primary calculation
About the coordinations, I don’t think it’s the just approach, Idk why bur from your approach it’s like a double work, sincerally what I would try to do at your point, would be integrate sanderling’s structure to your poject and then retrieve the path directly from sanderling and not from the pointer position inside the client. This avoid to go to recalculate the corners time by time.