Hey Slav2,

I had an idea, and I wanted to know how hard it would be to implement: a looter that uses "warp to member" to cycle through miners. Rather than using personal or corporate bookmarks, the looter would warp to each member using the fleet pane of the chat window (Right clicking on each name -> Warp to Member). In the case of a system with many belts or anomalies, I think it would be faster and more natural for the looter to move between members. The main issue I foresee are fleet members in the same anomaly that are far apart, but not within warp range. What are your thoughts?

It probably would be feasible to do. However it is flawed. Corporation bookmarks are better because miners can create them before they leave a belt. However, if a looter warps to a member, what if that miner is in warp or has already warped after leaving a can at a previous belt?

Also, it is unnecessarily complex because the program would have to share the names of the other miners in the group in order to know which ones to find.

I agree with you innominate. But if I can make one observation, many of us (at least myself) in Hi Sec, keep miners in NPC corporations to avoid War Declarations.

So I was thinking about that some time ago, and I have a suggestion/question...

And if instead using bookmarks or even warping to fleet member the bot has a comum file to communicate things?

As you know I have little to no knowledge of algorithm, but I got in some comments in this forum that bot will work with a new kind of tank mode for different VM or even PCs.

I hope (far as I understand correctly the idea) bot will be ware of the others (VM machine communications) using a comum file in a server online (at least I think it wold work this way or otherwise we couldn't use more than one computer if we use a comum folder in one pc) so the bot can make a registration of all there activity and it can have something like this exemple:

Miners and looter:

1. Miners jump to the belts. Do the first jettison.
2. It register the number of can it jettison and were it was, like 0.2-bookmark.
3. Looter jump to 0.2-bookmark and get the can and because it know the miner jettison 4 cans in this bookmark it won't miss any one the cans.

Booster, miners and looter.
1. booster jump to bookmark number one. start modules to give booster and leave start to mining the ore near it.
2. Miners do the same, but bookmark exemple (25km from booster). It start mining ores nearby it. Leave the mine drones getting the near ore.
3. miners do the jetson.
4. Orca (for exemple) get the cans.
5. Bots get new mining crystals from the orca and keep the Gods Work until orca is almost full.
6. If you have an Looter, looter jump to the belt and start getting all the ore from the orca fleet hangar... Orca don't need even to get ore inside it. Just get it close to looter be able to get the cans faster, or implement and MTU as well...

Of course It is almost all my wish list for Christmas. Mine drone suporte, VM and computers communication, efficient looter, MTU support, new orca booster... But just to give an idea of what I mean with this comum file use.

Best regards

I think that is possible if all in one VM, but I only skimmed it because I only work on stuff that applies across VMs. (Also I've reviewed similar suggestions here before.) So first, this. Then the other stuff should be easy for me to rig up. (I think...)

innominate wrote:
It probably would be feasible to do. However it is flawed. Corporation bookmarks are better because miners can create them before they leave a belt. However, if a looter warps to a member, what if that miner is in warp or has already warped after leaving a can at a previous belt?

Also, it is unnecessarily complex because the program would have to share the names of the other miners in the group in order to know which ones to find.

An excellent point. I think if miners could drop corporate bookmarks, that would be ideal.

As soon as I figure out how to obfuscate my code... Or rather, how to fix the obfuscation program someone provided so that it works with class objects.