Got a working mining drone script.

VERY BASIC FUNCTIONS. Will mine the current targeted roids only for now.
Take a look


I'll test this for a few days to see if it needs adjusted. and also run some numbers testing. Then I'll put up all the files in a new thread to share.

1st things first. Where to change the script module to run this, and then make another version of this for combat drones to launch them for fight module.

in front of
270: MiningModeEx
or
370: MiningLasersControl()

Wow, that was quick! Nice job. I went the route of making classes so that it was easier in the long run. I also made it so that they mine a different roid so that they didn't affect EP's ore calculations.
Here's mine. It doesn't loot because I had enough miners so that my looter goes almost full time. Never tried it as tank so others go to it because all my characters are on separate VMs.
In case it isn't obvious, I have code to detect if the drones have shield damage.
Just wondering, how many characters you have?

Wow, that was quick! Nice job.
Thanks

I also made it so that they mine a different roid so that they didn't affect EP's ore calculations.
in Later versions I'll probably do this, now that I know how to do it.

, I have code to detect if the drones have shield damage.
This is your EPScript not your AHK lol, I can't see shit.

Just wondering, how many characters you have?
I have between 5-9. I wont say for sure. I am not even registered here with the same email I use for eve. Can't be too safe.

I agree, can't be too safe.

Well, I can't release the core code, (because I've found that it can be applied to create bots that each yield 350 to 1,000 million per day with normal play times) but here is what I can share that you might find helpful.

Here is the fun stuff.

Testing out new code and changes to EPscript, gets hung up and autocloses Eve.

So I revert back to original MinerCorpBMV1.txt script, and it warps to POS and gets in a loop at unloadcargoX for 5 minutes then closes out, won't go any further.

Now I got to figure out how I broke it.

Found it: It thinks I am in a pod now.
??:??:??: UnloadCargoEx(220)

---> ??:??:??: ExitCode 2. Method consumed 132 sec. in 1 runs (average 132 secs/run), Next Line: 002+
---> Desc: Returns 2 if pod detected

Welcome to the wide world of scripting! Awesome to see you've started so strong and so quickly. Innominate shared his code above, but obviously refers to a lot of classes that you don't have. What I'd infer from them, if you want to replicate his functionality, is to either A. make a class yourself, modeled after his, or B. look at the functionality achieved by the class functions (e.g., dmgr.Dock_Some(wrongDrones, False), dmgr.Launch("Mining",False) and replicate it outside of a class. The classes would take a much longer time to make, but after you've made them, you could re-use them and scale them for any kind of bot/functionality you want.

You mentioned using the Orca as a booster, and there are a few potential pitfalls to bear in mind:
1. Range from Booster: with an Orca in a HS belt, this is a moot point, even a modestly skilled Orca will have boosts that extend over an entire belt. If you're in nullsec and working on anomalies (which can be hundreds of km across), you'll need some way to keep the miners close to the Orca. However, then there's the problem of what happens if keeping a bot close-enough-for-boosts makes them too-far-to-mine? Also, how do you keep them close without them all targeting the same rocks and reducing efficiency that way?

2. Yield Calculations: Slav's bot checks the yield once when you log-in, and saves those values. That's how it determines (with estimation) when to turn mining lasers on/off to reduce wasted cycle time. If you dramatically increase yield/reduce cycle time, those calculations will be off. Thought: make the bot look for the Boost icon above the HUD/Capacitor, and if it finds it, make it go to GetLaserData() (or whatever it's called) with pre-calculated numbers for range, yield, etc. If it doesn't find the Boost icon, make it go to a *different* GetLaserData() with default values.

Separately, your prototype drone script looks awesome, I'd just caution one thing. When you use just numbers for things like ImageSearch, you run the risk of the script breaking if those windows move. Granted, there may never be a reason for a window to move, but Eve and EP can be tricky sometimes One alternative method is to find an "Anchor" image first (like the unique name of the window, like "Drone Manager"), and then make every other reference point relative to that, e.g., AnchorX + 20, AnchorY + 50. To go deeper with the example: you know that "Drones In Bay" is going to be so many pixels from "Drone Manager", so you can find that. Then, you know that if it's collapsed, it will A. have an arrow pointing to the right next to "Drones In Bay" or an arrow pointing down. Depending on which you find, you'll know that "Drones in Space" must be so many pixels beneath it (depending on if the menu is expanded or collapsed). This way, no matter who's using the script or where their drone manager is, it'll be able to find those windows. That's how my Mail Call script works (when it works, that is...), excluding instances where 1. There are transparencies that make finding the image exceedingly difficult and 2. they are fixed GUI components that cannot move.

It's awesome that you're interested in developing more scripts for this, the sky really is the limit when you start to think about everything you could automate. Between AHK and a few EP methods (things like OverviewScan and Slav's OCR text reader), believe me when I say you can automate nearly anything...