First of all, it is awesome to see someone else on here writing code! Thanks for sharing! (Saved... If you add that little extra bit will you please post the update? I'm working on my project so that MTUs can be used and an Orca can use all it's available space as a looter.)

Minesalot wrote:
I would like to be able to send commands to each VM to tell them to dock, or POS up before stopping the vm. So they are not in space alone, in the dark, where no one can hear you scream.
There is a loop miners go through in belts. The wormhole mining algorithm already has this in place around 370 I think. 370 goes to an ini read that tells the bots what they should do. Just use that part, and have the iniRead go into the logoff branch 5-10 minutes before shut-down.

Finished with working version.

??? designates information I don't want public. Need to change it to suit yourself before it will work.

I just came across the "MenuOpenLineClick" so i decided to give that a whirl. I ended coming back here and rereading the OP and I see why you abandoned that route.

However, I think I am going to go about it a little different. I intend on only mining A, then Spod on1 B then spod on another, C then Spod on another.... so only 2

Warptostation while warping unload.
MenuOpenLineClick "Unload to Cargo" the mining crystal that is loaded on f1 ;testing on skiff for now.
Once docked or at POS
openwindow cargohold
drop everything in cargo to station.
readini roid 2 choice
search for and drag crystals to ship cargohold
undock, or at POS
MenuOpenLineClick "Reload All" on F1. Since there is only 1 type of mining crystal it auto loads.



You know what? screw it. T1 strip miners work Juuuuuuuuust fine.

But I do want to work a way out to change asteroid overviews that way I am mining A then B then C choices.

Exactly! I just use another miner, so they all mine something different and can use T2 crystals. Way easier!

I am sounding out some ideas before I go into the logic and making changes. Feel free to shoot these down in as few words as possible.

1. Use multiple client mode on a VM. The same pilot, just different overview settings for asteroids. Say client 1 arkonor, client 2 bistot, client 3 Crokite. Then run client 1 for 4 hrs 2 for 4 hrs 3 for 4 hours. Just using the timers in EP

2. modify algorithm to change asteroids overview if empty, and have overview settings for each roid type.

3. BM each anom from 200km away. then each pilot warps to BM, sees overview of goodies, sorts by name once to get ABC order. Pick first roid, initiate warp. Sort by distance, then continue. (Think I am going to go this route. Seems easiest, and most effective. Would need to break into algorithm after warp to BM. fire a AHK to sort by name, then click first roid, warp to, then end AHK to let EO take over again)

4. Have 5 miners running t2 crystals on each roid type. the one guy on Arkonor flys about 4 hrs a day and rests the rest of the time. The bistot guy gets about 6 hrs of work in and rests the rest. The spod lady, can work for 3 days straight jet canning and still be working the same single roid.

Ideally, I'd start with #2.

Make an algorithm with AHK scripts that would warp to the first Anomaly at 100km, bookmark, return to home, warp to bookmark at 100km, delete first bookmark, make new bookmark at 200k. You could either work that into the anomaly algorithm or put it on a different EP client.

Make AHK to change overview and crystal type (EP might do some of this). Work it into algorithm so when a roid type is all gone it changes roid overview/crystal and keeps mining.

It's not the easiest route, but it would work best IMHO.