Hi Slav,

would it be possible to change something in the looter his sequence?

I noticed that the bot warps to the belt, approach location, then locks target and activates the tractor beam.
When a target is below 600m it will open the container.

Would it be possible to change it that if you approach the belt and the container is within 2000m, that you immediattely open it instead off locking and activating the tractor beam?

This even saves time...

Would be very good to be able to change that. sometimes I leave the MTU manually and war to mtu. It is less then 1000 meters as bot warp in, but it still turns one tractor or approach can if no tractor is fitted.

2,000 is very close to 2,500. I think current (short) range is probably set so that the bot can't start in range but drift out of range while slowing after warp and opening the can.

how did U do the MTU-integration?

Not done, as I'm still working on the methods for interacting with the inventory window.

(X means user defined)
But here's the outline for looter:
On warp in, hauler checks overview.
If MTU detected, approach to within 1km and open.
Else If the number of cans is greater than x, it deploys the MTU.
Else if any cans beyond x km, deploy MTU.
Else let EP loot all.

While there are any cans over 4km, or ship hold(s) not full or x time limit not met.
----If more than 2 cans further than 4km, bot can lock/tractor 3rd closest and beyond. (2nd closest could cause script to try and tractor same can as MTU = Bad)
----If tractored object closer than 4 km, unlock it and next loop will check if another can be tractored.(MTU will finish the job)
----Drag MTU items into appropriate hold(s).


Before leaving belt:
If cans beyond 4km, leave MTU in belt.
Else, scoop MTU (Eve puts all items within into cans)
Let EP take over (will return automatically)

That is off the top of my head while on phone.