It's been a while since my last post, this has mostly been due to a very tight deadline I have at work. It's hard to keep up the blog when I'm even working in the weekends :(

However I have made a lot of progress with the bot. I wont upload a new source just yet (hence the 4.5-part instead of 5), mostly because I am waiting for the performance-release of ISXEVE. I'm beta testing the release and it still has some bugs, but as soon as those are gone then the new version of the mission bot will be released. Releasing it now would result in unacceptable performance (truly unacceptable!).

But to give you a bit of a heads up on what has been added since the last release:

• Drone support, although it still loses drones in missions (The Mordus Headhunters eats up drones), the support works pretty darn good! :)
• Loot-pickup support, this means it will check each can to see if the mission item is in there.
• Full mission "scripting" support, allowing you to select what actions the bot will take in missions.
• Priority-looting, using an XML with market-prices from eve-central the bot is able to dump less-valued loot and pickup more valuable loot.
• Create salvage bookmarks (if a mission has more then x-wrecks left then it'll make a salvage bookmark for that mission pocket)
• After-mission salvaging, the bot has the ability to jump into a salvage ship after completing a mission and visiting the bookmarks that it made to salvage (and loot) all the wrecks there.
• Better ammo-support, you can have multiple types of ammo with multiple ranges, and it will pick the right type of ammo for the right range. (I will be adding additional options to this in later versions, to (for example) select rage-torps for battleships)
• Speed tanking, when enabled the bot will orbit the target its attacking (it still has some bugs but works pretty well)
• And most importantly: a settings-xml file which allows you to change any setting in the bot

There are still bugs in there, but its getting very close to perfect for combat missions. 

I hope that the ISXEVE performance update gets released soon, as I can't really release it like this. It would be too slow.