Slav2,

As has been discussed before, if the Ore Hold is used and the looter encounters a cargo container that has loot in it (specifically, when people salvage wrecks without looting them), the looter will attempt to drag the loot into the ore hold, which won't work. The looter bot gets stuck in a loop. Is there any hope that you can fix this?

My idea was an option to make the Looter only loot cans that have names that match a text string, so that then our miners could use that same text string when renaming their cans.

The alternative was to attempt to use the algorithm editor to make it try to "Loot All" (to cargohold) if the drag/drop method (to orehold) fails. If this is not an option with the algorithm editor, would you be willing to implement such a method?

With the Orca having an orehold of over 150k m^3 and the death of the Booster Bot, it would be great to repurpose it into a Looter. However, the inability to resolve loot-filled jetcans means that large portions of mining time can go to waste while the looter bot gets stuck in its loop.

I would be grateful for any feedback or response. Thank you!

Thanks for report. I was not aware of such a problem. Need to think how to do this better. Can we apply filter to not show other corp containers in overview? Miners may jettison two containers instead of one and I am not sure if both are properly renamed after that.

Unfortunately, I didn't see an overview setting to filter non-corp containers. Would it be onerous to add in a text string detection like I mention above? I realize that would not help with the two containers, but it would at least work the vast majority of the time. The downside of the "Loot All" method is that it could, in theory, fill up the normal cargohold and you'd have to write in some way to check that as well (not sure if that'd actually be hard or not, not sure).

Some resolution of this would be outstanding, I'm thankful for your attention!

If an NPC attacks the bot before it has named the new jet can, then the jet can does not get named.

OK, I think we can just skip containers with content load < 350 m^3 if orehold use is selected. This will mark container as visited in overview and bot will not open it again.

Also, making the abandon wreck work reliably I fleets would work too.