Slav2,

Seems like there are additional errors in your latest fix to the orehold looting problem. It looks like once it unlocks the container with loot, it errors because it "can't detect locked container." I sent you logs and a screenshot. Here's an example:

04:46:18: LooterTS(380)

04:46:18 (26725) Warp not detected/finished. Code 2, Func : WarpingSubStop
04:46:19 (26725) Finish. Code 1, Func : SetupCargoManager
04:46:19 (26725) Window opened (orehold). Code 1, Func : OpenWindow
04:46:19 (26725) Tractors = 5, TOR = 70000m , Salvagers = 0, SOR = 5000m , looting wreks = False, looting yellow wrecks = False, looting containers = True, Func : LooterTS
04:46:20 (26726) Looting and salvaging block, Func : LooterTS
04:46:20 (26726) ContainerWhite: d=627, lock=0, sel=True, Func : LooterTS
04:46:20 (26726) ContainerWhite: d=752, lock=1, sel=False, Func : LooterTS
04:46:20 (26726) ContainerWhite: d=2917, lock=1, sel=False, Func : LooterTS
04:46:20 (26726) ContainerYellow: d=11000, lock=0, sel=False, Func : LooterTS
04:46:20 (26726) ContainerYellow: d=11000, lock=0, sel=False, Func : LooterTS
04:46:24 (26731) Finish. Code 1, Func : SetupCargoManager
04:46:25 (26731) Opening New Window, Func : OpenAndSetupSecondCargoManager
04:46:35 (26741) Container = 0/27500, probably wrong container without ore. Unlocking and closing container, Func : LootWreckOrContainer
04:46:35 (26741) Selected item window detected, Func : UnlockAndCloseContainer
04:46:35 (26741) locked target not detected, Func : UnlockAndCloseContainer
04:46:35 (26742) SS: C:\Users\Administrator\AppData\Local\MacroLab\Eve Pilot\ErrorHandler\EVEPilot-7.13.17.0-LockedContainerNotDetected-2016-12-05_04-46-35.bmp, Func : UnlockAndCloseContainer
04:46:35 (26742) second cargo manager detected, closing, Func : UnlockAndCloseContainer
04:46:40 (26746) Error: an attempt to loot line 1 failed. Code 2, Func : LooterTS
---> 04:46:40: ExitCode 2. Method consumed 6654 sec. in 837 runs (average 7 secs/run), Next Line: 325
---> Desc: Returns 2 if in progress of looting, salvaging, approaching or warping

Slav2,

Any update on this? It remains an issue.

Check this version. Bot will loot the container using loot all button if vol < 350. What is the max volume of this scrap?

The scrap is tiny (0.1 m^3), the ammo is also pretty small (~1 m^3 iirc) and the modules are maybe ~5 m^3 each. The cargohold of the Orca at least is something like 36k m^3, I can't fathom that it would fill up before I check on it after a day or two. When I used to use the normal cargohold, it was rare that I'd have more than 15-20 m^3 of loot. The reason it happens at all is that people come and salvage the rat wrecks, leaving the loot behind in a cargo container. If that doesn't happen on any given day, there's no issue at all. However, when it does happen, it costs me 50-66% of my day's yield since it typically kills the looter until a timer pops up.

Either way, Thank you!!

Slav2,

An update on this: it's working really well! Sometimes I notice ore in my cargohold, small amounts (<350 m^3). I realized why: when the looter partially loots a can, it can leave only a small amount behind. Would it be possible to drop the threshold to 50 m^3? I don't think any rat is going to drop anything close to that much loot, even in nullsec. It's a total non-issue for me using an Orca, cause the 36k cargohold is huge, but for a Miasmos with only 500 m^3, it'd be possible to fill that cargohold pretty fast.

I will change minimal volume to 50 in the next version.