community.eveonline.com/news/dev-blogs/m...-foreman-revolution/
It looks like along with the changes to boosts, the industrial command ships will be powerful drone-based mining ships. I know the user "innominate" has a private mining drone solution. If innominate reads this, would you be willing to revisit sharing this code in some way, shape, or form?
Another detail is the size of the booster ammo; 0.01 m^3 per unit. Given that each unit lasts at least a minute, and the Orca has a 30k m^3 cargo hold, this means that the Orca could boost continuously for approximately 50000 hours. I sincerely hope no one is running their bots for 50000 hours straight
I intend, at least, on finding SOME way to keep using a boosting ship with my miners (until it shows itself to be so inefficient that I turn my booster into yet-another Miner...). I'd like this thread to be a discussion of people with ideas on how we, as a community, can create a custom algorithm that would enable us to use command burst ships. Slav2 has made it clear that he is not interested in creating a new bot/module for the new boosting, so let's please keep those comments out of this thread. I'll try to aggregate some ideas that have been discussed:
Booster-as-Selected-Tank: Booster acts as the Selected Tank of the mining fleet. Fit it with a Miner I laser in a high slot. The Orca's ore hold has been increased to 150k m^3, and no mining yield bonus, so a single Miner I would take a long, long time to fill up (which is a non-issue if you're jet-canning anyway). Use the same set of bookmarks for each miner, with each one being in the center of each belt. In the Algorithm Editor, define the mining yield/optimal range/targeting range/cycle duration as parameters to GetLaserData function for each Miner so that you don't need to worry about when/where the miners "check".
Assumptions/Requirements/Issues:
- Keeping in Range of the Booster: This may come down to the individual booster, but decent boosting skills (Leadership V, Wing Commander III) will give you a 34 km range, which would likely cover the vast majority of an asteroid belt. I think that using the same bookmarks at the center of the belt and limiting miners' maneuver distance would probably keep your miners covered. The huge glaring flaw of this is anomalies: they're so much bigger than belts, I struggle to think about how to keep all the miners close to the tank without some new functionality...
- Mining the Same Ore Type(s): chances are you'd need to make every miner mine all the same type(s) of ore, otherwise some would run out before others and be idling. Belt stripping might be a new way of being.
- Mining the Same Asteroid: Not sure if there's any way to avoid this in any setup that uses the Selected Tank and the same ore type.
- Mining Yield Calculations: you'd want to define it in the GetLaserData function as above. I for one will not be using the range boost because that would be a great way to confuse the bot. If you define the bot's yield/duration as the boosted one, then it will only overestimate its yield if the miner gets out of range of the boosts. I imagine that would hurt your yield less than underestimating the yield (and wasting cycle time on already-empty rocks).
Ideas to Consider for changes:
1. Keeping distance to Booster - is there a way to leverage the "avoid PC" functionality to check for Industrial Command Ships and Industrial Capital Ships and keep at range?
2. Mining Drones - the mining drones can make an Orca yield almost as much ore as an unboosted Procurer, that alone would make it a pretty valuable addition. Contingent on innominate, though.
Forums
