It still sounds like you do not have ore hold checked in the gui. My code would not do that. That is EP. I was using an Orca that way about a month ago. Not sure what your problem is there, but I can promise it isn't my code.

I think it was the tick box under shared settings>custom delays, "slowest mouse drag" that did it. Or the 3rd first run, or me punching the monitor. Either way, looter is functioning. Wasn't blaming your super duper code, just pickin yer brain.

Kudos Innominate. After running this for a few days, it is a significant increase in profits, running 6 miners and 1 looter in an orca scooping.

I have the CorpBookmarkCan.ahk set to varying times of 23-29 minutes, so they do not all drop at the same time. Kinda fishy if I am dropping 6 BM's at the same time. I am in a system with 20ish belts. Each miner is using 4-7 belts, not the whole system, but some do share a belt sometimes.

Only 1 issue. It is not your script, it would be for the Looter. I made the adjustments to the base looter script to warp from BM to BM instead of BM to Station/POS. It is running smoothly. I think that was Abbadons edit I used. The suggestion is, After the looting, the bot goes back to the first book mark to "Remove BM"... RIGHT HERE, can you add a right click check to each of the other BM's that fit the "Look for this word" criteria, to see if there are duplicate BM's for the same belt, and remove them? Since I think the bot looks for "Approach location" to verify it is in the right spot, after checking the other BM's and sees an "Approach Location" it would remove that BM.

If you're interested, I could show you how to make that fix yourself. I had the same issue with it (but never fixed it). It's actually not terribly complicated, AHK is pretty easy to write.

I probably should. I have done some coding and adaptation of what others have done patched together to what I need. But It takes me long long time to get it right. Kind of like "Weeks worth of coding saves hours of planning." That's why I bow to the expert opinion and talents of others.

I hear you. Only downside being that you're dependent on the time and inclination of others to get the job done If you are interested in taking a stab at this in AHK, I'd do this:

Right click on a bookmark that you're on-grid with (so it says "Approach Location") and hit alt-print screen to capture a screenshot of the active window (Eve, in this case) and paste it into MS Paint. From there, you can accomplish two things: 1. make a tight screenshot of "Approach Location", a tight screenshot being a .png image with as few extraneous pixels as possible to appear unique on the screen. and 2. figure out the distance/displacement from where you right-clicked to where it says "Remove Location". Now, figuring out which one it already clicked on to know what image to look for is somewhat irrelevant. Having it do OCR (reading the screen and turning it into text for searching, etc.) is not something available in EP as a function and is very complex in AHK, I wouldn't bother.

What I'd do is see if you can write a function that looks in the Corporate Bookmarks for a common image of a corp BM made by your miners (a tight screenshot of the green text with like "01-Bookmark" in it or whatever). The first one it finds (the AHK ImageSearch function returns the X and Y coordinates of the first occurrence within a given area of the active window), have it right click, do an ImageSearch of the "Approach Location" button (use the displacements we found before to make it only look within the area of that right-click context menu). If it finds it, the AHK function MoveMouseClick can take the cursor to the correct displacement of "Remove Location". You may also need to code a way to make it detect the "are you sure?" menu, unless the settings to confirm "Don't ask Again" is already set. I said the ImageSearch looks for the first occurrence within an area, so now you want to make sure that your search area doesn't include the first one you just checked. The solution to that is to make the thing a Loop (google "AHK Loop" to see the documentation to how that works), and at the end of each loop, alter some SearchAreaY variable or whatever you want to call it to be below the current location found (accounting for the width of each row in pixels... maybe 17? Confirm for yourself). A piece of advice on ImageSearch: the smaller the search area, the faster it goes. Use the same screenshot you made before the find the coordinates in the People and Places window where it's likely to be: no need to look anywhere else, right?

Anyway, I know I've thrown a lot out here, so if you do give it a shot, and what I've said makes no sense, feel free to post here and I'll do my best to answer. If you don't give it a shot, then no big deal