Problem solved.

With the miners running BM's every 25-30 minutes
Start the looter 30 minutes after they start
Looter flys an orca with acendancy implants for a whopping 3.5 au warp speed
Targeting mods for almost instant locks
He is able to loot everything in plenty of time. even with fouled BM's

Ha! Awesome I love simple solutions! That said, offer of help stands if you ever find a problem you think scripting could fix

Something is borked. The last couple days I get home and I see way too many bookmarks, and they are more than 2 hours old, so I manually operate the looter to mop up.

I am going to need to either add a function to miner to self delete old BM's or modify a looter to remove all BM's in same belt.

Edit:
Further testing I see that they are marking empty belts too much. Every time they visit a belt and there are no roids, the belt gets marked with the belt script, towards the end of the day that can be quite a few. So I think there needs to be a timer just for belt marking, or add a .ini read/write for was a can jetted in this belt? Then mark the belt.

CorpBookmarkBelt.ahk Edit: Changed the upper section only to verify a can is in space and marked by the CorpBookmarkCan.ahk script



CorpBookmarkCan.ahk Edit: Changed the upper section


And the lower part added


With these changes it seems to be working a little better for me. I am going to try a couple days with the timer turned down to 12 minutes, so it will mark every other can drop, that way the looter is at least picking up 2 cans at each location. Fewer cans in space hopefully pirates leave me alone. I have seen as many as 8 cans at a location before. Very tempting target.

How feasible would it be to have the looter do a scrub for the Bookmark graphic before warping to the next Corp bookmark. Would it be more generally usable by more people than to scrub all of the Corp bookmarks for approach and remove?

Look for this image:


In this area:



I do foresee 1 small problem. Multiple bookmarks that overlap like this, the human eye can tell there are two there, but can the image scanner? Scrolling in and out does separate them enough to be recognized.

I would recommend you adding logic that clicks on each BM. If it has Approach, delete it.

Got a functional script running. BTW Pulovers Macro Creator program is awesome!
Edited: Vs 1.1


It is working as I like.
Checks top BM for "Approach Location" and removes it if found.
Rechecks top BM for "Approach Location" and removes it too, until "Approach Location" is not found.
Drops down to the next line and rinses & repeats until no more BM's match.

I am surprised I was able to do this in such little amount of code, I thought it would be longer and more complicated. If you can see a better or more efficient way of doing this, I am all ears... or eyes.

A big question is, where should I edit the Looter script to run this after looting and before choosing next destination?
I put it right here at 319 so it should check local, then rinse the bm's before picking new location

Edited: Using Looter script edited using Abbadons suggestion and moved Approach check to 649