I have done enough for a while.

If someone else wants to make the booster algorithm. I'll adjust this to work with it.
Look at the original post for what the booster should do.

If you're getting burned out, I'd definitely recommend taking a break. Innominate can tell you, he saw me nearly lose my sh*t entirely when I got overworked and frustrated with something I was working on. I took a week off, and came back renewed and feeling much better about it. You've done a lot of great work, I wouldn't toss it in the pile just yet. Later this week, I should have some free cycles if you'd like for me to look at your code?

(On phone, sorry.)
Dude, you have no idea how close you are! You just need to take a page from Slav's book.


Booster uses slightly modified version of your miner algorithm.
When booster is about to warp (after BMBelt.ahk), log off, or crashes set shared ini to 0.

For synchronized BMs:
When booster arrives at site, it right clicks on each BM to find Approach so it knows where it is.
Writes BM# to shared ini.
Booster mines with drones as normal until algorithm goes path of

Let INI value (set by booster) determine what miners do.    
INI=0, Miner algorithm needs to sit at or return to base.
INI=[BM#], Miner warps to synched BM#

For non-synched BMs
User must save name of booster so miners can right click and Warp To it.
INI=1, Miner warps to synched BM#


Miner algorithm:
Change 401 to be something like WarpToBooster.ahk. That script would check shared ini and either initiate warp to booster (BM# or warp to member) or go back to 120 if ini is 0. Then for mining piece, Before StopOperation it checks shared ini. If ini is 0, it skips over StopOperation to go to 270. Have 270 always go to 240, which Means MiningModeEx and CalcBeltToWarp isn't used.

Booster algorithm:
Have it set shared ini to 0 before BookMarkBelt.
After AvoidShips, have it get BM# and write it to shared ini. (Or just write 1 if doing warp to fleet member)
Before all CloseEveWindow and EP modules that warp, write 0 to shared ini.
In EP GUI, set mining laser module to activate fleet boost module.

I think that should work?

Well, I did just finish coding full on grid booster and miners Vs 3.0

Got in the mood to just bang it out. Now I need to test it.

Here is the Looter algorithm.

It warps to the first belt BM, finds asteroids and drops a BM.

If it warps in and does not find asteroids, it warps back to POS and just chills there constantly looking at the top BM.

Where would I change it to go to BM 2, then 3. Or do I need to write another ahk to do that?

Assuming you mean Looter deletes BM.

I think it is LooterTS that determines whether there are no more cans in the area (and deletes old BM)... So, if there are no cans left have it route to a script that checks for the number of BMs. If more than just the station BM route to warpingToLocation(1), else warpingToStation. That would do it.