Bot has been working very well all the time, but today there was an unexpected loss. Later, when I checked the screenshots of the bot, I found that during the battle in the Abyss, when my ship's repair stopped working due to running out of charge, the bot attempted to restart the repair. However, the first attempt failed because of insufficient charge. As a result, the bot never tried to start the repair again, and that's why I lost my ship XD. I'm not sure if this is a bug or if there is something wrong with my settings?

Bot detects activation status of repairer/AB/active modules every 20 seconds. I think pointless to start activation module earlier if first attempt failed due to low capacitor. Exception is second repairer, its status checked in separated thread, bot monitor HP level and activate/deactivate it as fast as possible.

If you fit is not cap stable, better to update it. You will loose ships anyway.

My fit is actually cap stable. It's just that sometimes a situation occurs where the cap is neutralized, and the re-detection after 20 seconds might be a bit dangerous for the abyss. I'm wondering if I can change this detection interval time. Thanks for your help!

I will temporary add this delay to settings to tune. But if bot will detect module statuses more frequently, it will also fight slowly. Best solution is to move detection to separated thread as I did for second repairer.

That sounds like a good idea. I'll go and test it.

Slav2 wrote:
I will temporary add this delay to settings to tune. But if bot will detect module statuses more frequently, it will also fight slowly. Best solution is to move detection to separated thread as I did for second repairer.


Have tried it, I set two repairs and the second one is real, it sometimes may not activate repair after cap out, so I think better way is that set up detection interval time shorter(set up by user if need it)