Slav2 wrote:
On the side note. Can you fit miner I to your booster and act as a tank-miner? Fit active module to high slot and set 100-100 rule to activate. Place the same set of bookmarks to all your miners and ask them follow miner. Define mining yield/optimal range/targeting range/cycle duration as parameters to GetLaserData function in the algorithm. These measures will enable basic functional (without reloading booster's ammo).

Unfortunately, the Orca can not fit Mining lasers (needs turret slot) or strip miners (only fits on mining ships). I suppose you could define the Command Boost module as Mining Laser and manually set all values in GetLasersData so that it skips the part where it checks the yield. Unless you have drones mining, the problem is that the bot would detect no ore coming in and exit Eve. Well, LOL, I guess you could define the mining laser yield as 1 and the duration at 999 seconds? (Could someone with multiple clients on the same VM test this please?)

Slav2, would you be willing to add tank mode so it can be used between VMs? (Otherwise it wouldn't be worth it to boost because not enough eve clients can run on the same VM to make it worth a tank-mode booster.)

So, it looks like we're not going to get a meaningful solution to this issue before the booster changes hit. What will you do with your booster? Sell it? Retrain it to be another Miner, since you already bought a Miner license for it? I haven't done the projections yet on how much my yields will suffer.

Innominate, do you still have your mining drone code? Are you at all interested in releasing it, given these changes? Can we do anything as a community to convince you to release it?

I was thinking for Orca on grid boosts.
Select Orca as tank. Orca warps to belt on grid, starts active
modules, and waits for fleet members.

I'm not too sure how the barrier function works, but if I'm assuming
correctly we could use this to verify if fleet members are ongrid within range.
With max skills and implants boosts reach out to around 45km in a sphere if I'm not
mistaken (please correct me if I'm wrong here). So boosting on grid shouldn't be a problem.

Also, if you enable the looter algorithm, the one where it checks for the white text
in the containers tab, you could make use of its enormous ore hold that we are going to get.
This would also make use of its new slot configuration 6H/5M/1L
This way you could have 3 boosts going and 3 tractors.

For fleet members, all they would have to do is open fleet menu, right click and warp to member.
From then all they would need to do is reuse the current mining algorithm and jet cargo for Orca to pick up.

Thanks for weighing in!

I haven't really explored the Barrier Function or what it's supposed to do, but I think it's worth looking into if that is indeed the case! You can spare yourself a few months of training (Fleet Command V is kind of a nightmare) and still get like ~34 km out of it, which I think should be sufficient for most cases, especially if all the miners are warping to the same bookmarks.

I also dug this out of a somewhat unrelated thread: www.macrolab-online.com/en/forums/32-fee...limit=6&start=12

This custom script is based off the Miner license, so it'd work for your booster. It's actually designed to be a drone-based belt hunter: the bot warps in, launches drones, waits for NPCs, keeps waiting, etc. You can tweak the parameters like in Slav2's belt guard example (www.macrolab-online.com/knowledgebase/sc...nt_bot_examples.html) to make the bot sit there for as long as you want your miners in a given belt. You'd keep the boosts as active modules. Using as a Looter is another possibility, but I'm not sure if the Looter license would let you use all the Mining modules you'd need for this. The real growth area would be if you could make it target and "hunt" asteroids with mining drones In the mean time, having a flight of Medium Drones out would still be good protection, especially considering the damage bonus they'll be getting!

The obvious downside is that all the bots would need to be on the same computer/VM, until Slav2 can implement Selected Tank across a network. However, I've found that with the right configuration (Blind Miner, limiting how many bots check local, etc.), you can efficiently run as many as 6 miners effectively on a single system (RAM permitting).

I will test this tonight and let you know.

Sounds good.

What if again, you were to use the fleet window and monitor the fleet broad casts as a way for bots to communicate without having to be on the same VM. Say the tank/booster that is already ongrid in belt were to click on of the buttons on the bottom, such as one of the target calling ones. The other fleet members on a different VM could see this and interpenetrate it as warp to me and start mining operations. That way communicating is done by monitoring fleet broadcast history.

Edit:
So I did a little more research and the fleet window has 3 tabs; Fleet, History, Fleet Finder (nothing new here).

The tank/booster could, once in position, click the 8th button in the fleet tab. This will send a clickable message in the History tab that other fleet members could warp to. In theory the bot could recognize this broadcast alert as the signal to undock, warp to booster, and start mining.

I think using the fleet mechanics to make the selected tank work would be a very easy way to do it, I hope Slav2 has considered it as an option. I like the idea of using the Broadcasts as a signal for the other bots; that would jive nicely with the OCR detection!

I also think it's worth exploring (if you have any other ideas) on what we can do with the capabilities that we have right now; obviously Slav2 could make the best possible solution, but in the mean time, I think finding some way to make this work would be good. I personally don't want to lose the benefit to my yield or need to extract/retrain my booster into yet another miner. Do you have any ideas on how to improve what I've proposed above?