In order to test betaversion faster please enable logging and detailed logging for the program. You can switch to settings or logs view any time from menu: view settings<->view logs.

One thing. When you beta test program try to not touch eve window, take any actions on your computer or change settings for miner in real time in GUI. We dont have time to test something we can easily avoid. New expansion is near and need to get working version of the program as soon as possible.

During beta tests record logs togather with detailed logs please. In view setings you have tabs 0-9, tab for processor and other tab. In client 0-9 tab you see logs recorded by main thread with details on algorithm logic. If you activate detailed logs program allows to show details, but not all possible logs will be recorded. I made manual activation of detailed logging for each module. To debug something we should find problematic module, then I activate details for this module and we can continue to test it in new version.

Other tab contains information recorded from HP check/down time/connect lost thread. This thread can interrupt normal algorithm logic and start connect lost routine, fighter, emergency warp outs or log offs. This is good and bad. Bad because it is very sensitive for different errors. For example in eve not responding for a while it might think that eve crashed. To understand how both threads working togather DT/HP thread writes one line to client0-9 log window starting from "***". That means next module to start for the client is defined by DT/HP check thread.

To send logs please append logs to file from client0-9 tabs (if they present) and from other tab to files with appropriate button located in each tab, then open in editor, resave somewhere and send to me.