Hello, after installing the new EVE update today 6/24/2025 and the new Evepilot update to fix the new colors added I ran into some errors while botting. Normally when a drone starts to get damaged, the bot will tell the damaged drone to return and then send another drone from your drone bay out to replace it. After this latest update, a drone will be given the command to return to the drone bay after taking damage, but then Evepilot becomes stuck trying to send out the replacement drone. The bot will stay stuck with only one drone out and it won't cycle any modules or anything until eventually it triggers itself to go back to station to do a whole reload of ammo/drones. It will then attempt to go back to the anomaly, but it will start to loop this error with replacing the damaged drone and creates a huge inefficiency for isk/hr and a liability for your ship while in space. The log ends abruptly because I paused the bot after seeing the error twice. I have attached a screenshot of the moment the error occurs and below I'll post the log from the client I was using. If you would like any more information to help fix the error, feel free to ask.

ibb.co/KcCsz15y - image of the drone bay at time of the error, it seems that is what the error is centered around.



*Edit 6/25 - Refer to post below for log error.

I ran a few more cycles today to test out the error and here is a better log of the issue. The error happens with the, "Launching drone position is empty, Func" towards the end of the log around 14:28:09 after a drone has taken damage and needs to relaunch a fresh drone from the drone bay.

*edit problem fixed, log removed

Should be fixed in 12.10.83. Report in case of a problems. Line intervals between drones became bigger despite activated compact view after the patch

Hello, thank you for the quick patch that fixed the drone bay for the hunt bot. I have found two additional bugs. The first bug is much more important to fix because it leads to your ship being destroyed by NPCs when it shouldn't be. I refer to the first bug as the, "orbit," bug. The bot will warp you to a combat anomaly, but your ship won't start orbiting and will just sit there at 0.0 m/s taking full unmitigated damage from the NPCs and will eventually lead to your ship's death. This error is very annoying because you will lose ships completely randomly just because orbit isn't being started. I have included the last error handler screenshot posted in the log shortly before I had to pause the hunt bot to take manual control to prevent my ship from being destroyed. Take a look in the log starting around 18:16:00 to 18:24:00. This was the last full run from station to the anomaly where the orbit bug occurred.

As for the second hunt bot bug, it has to do with the drone bay selecting drones and hanging there for about 30-45 seconds before fixing itself and continuing on. I have yet to get a log of this bug happening due to real life timing, but I will get it for you. The orbit bug is a much bigger issue than the drone bay bug because it actually stops your hunt bot from continuing to work due to your ship dying. Hope this helps, If you need more logs of this happening I can watch out for this error again and send more logs.

I sent the logs via email and can't post them to the forums for posterity due to sensitive information being included within them.