All credits to @Viir for the development of the same.
I just did some testing and being an annoyance with my comments and errors encountered. I am creating this thread due to still encountering some issues the need attention and as reference to those who would like to use this bot.
The below link is the bot engine.
@MutantWizard , I found a solution. You can avoid that error by using the new BotEngine console app from https://botengine.blob.core.windows.net/blob-library/by-name/2019-10-10.BotEngine.Console.zip
I implemented multiple improvements to help with this scenario:
Compression of the downloaded data. The size of the large file which was the bottleneck and led to the crash is now reduced to 13 MB. (This file will again be cached in the file system, so only needs to be downloaded the first time a bot is started on a Windows user account).
Increased timeout of the download process to 4 minutes. With the older version of the app, the download failed after 100 seconds, leading to the error message you saw.
It should be sufficient to use the new executable file; the other parts of the guide still apply as before.
This link is the full guide for using the bot.
# How to Automate Traveling in EVE Online - Using a Warp-To-0 Autopilot
When playing EVE Online, you might spend significant time traveling between solar systems. This activity is so common that there is even an in-game autopilot to automate this process. But that autopilot has a critical flaw: It is quite inefficient and will cause long travel times. You can travel faster by manually commanding your ship.
Fortunately, this process can be automated using a bot. The bot we are using here follows the route set in the in-game autopilot and uses the context menu to initiate warp and dock commands. Using the following steps, you can set up your warp-to-0 auto-pilot bot, to travel fast and safe in EVE Online.
+ Download the BotEngine console from the following URL:
[https://botengine.blob.core.windows.net/blob-library/by-name/2019-09-26.BotEngine.Console.zip](https://botengine.blob.core.windows.net/blob-library/by-name/2019-09-26.BotEngine.Console.zip). Extract this Zip-Archive. This will give you a file named `BotEngine.exe`.
+ The bot we will use in this guide only works when the EVE Online client is configured to not run in 64-bit mode. Make sure that the setting `Run clients with 64 bit` is *disabled* for the EVE Online client. You can check this in the settings dialog shown in the screenshot below:
+ Start the EVE Online client and log in to the game.
+ To start the autopilot bot, run the `BotEngine.exe` program with the following command:
```cmd
C:\path\to\the\BotEngine.exe start-bot --bot-source="https://github.com/Viir/bots/tree/1a1af8ad177a56e006bcf583b3ef98f8b629e83d/implement/applications/eve-online/eve-online-warp-to-0-autopilot"
```
You can enter this command in the Windows app called ['Command Prompt' (cmd.exe)](https://en.wikipedia.org/wiki/Cmd.exe). This app comes by default with any Windows 10 installation.
After you have entered this command, the bot needs a few seconds to start and find the EVE Online client process. It also shows status messages to inform what it is doing at the moment and when the startup is complete.
show original
@Viir
following encountered just a few min ago.
https://photos.app.goo.gl/PySwwG1hoqkExSyw5
Has been like this for 10-15 min no reaction to anything I do in Eve.
There is a new version of Bot Engine by @Viir that solved some of the single file executable packaging issues I had and apparently some other people had as well. This is the download link.
https://botengine.blob.core.windows.net/blob-library/by-name/2019-10-21.BotEngine.Console.publish.debug.zip
I dont like to copy paste, open windows and mess around with running this thing so I created a shortcut with the following target.
C:\Windows\System32\cmd.exe /k C:\EVE\BotEngine\2019-10-21.BotEngine.Console\BotEngine.exe start-bot --bot-source=“bots/implement/applications/eve-online/eve-online-warp-to-0-autopilot at 1a1af8ad177a56e006bcf583b3ef98f8b629e83d · Viir/bots · GitHub ”
1 Like
Viir
October 26, 2019, 8:04am
4
Do you still see this problem?
Thanks NO, that was solved a couple days ago together with the mining bot.