We slept way too long...

[Ksexasiaris]

We slept way too long waiting for the bot thread to give control back. Aborting thread. Client may crash!

I get this message often and I have to close the bot and re-open it. When I try to close the bot it gives me error and than I have to wait around 2-3 minutes for server to understand that I have logged out, in order to reconnect (I get max sessions error).

I use the bot only to control the combat for me, but often there are long times without a fight and into cinematics, that I guess bot goes "afk"...dunno.

How can I avoid to get that message and often restart the bot?

Log file: http://www.easybytez.com/ah0katmjcgok (Cannot upload it here, say invalid file)

 

[somethisrandomname]

The bot fails when going to new locations or sometimes in a cutscene. Usually stopping the bot, or closing the bot right before is helpful. Also log into buddyauth.com/User/Sessions You can kill the session there. So you don't have to wait to log back in, but you have to keep refreshing and killing when you need to use it.

 

[Cryogenesis]

For Max sessions go to Buddy Auth on top of this page, log in and kill the session if BW crapped out.
If this is the first time you login on buddy auth, you have to create an account with the emailaddress which you bought a key with.
Switching between planets and other stuff that may shift alot of memory, like changing zones, may crap out the bot.
This is due to the game and not really the bot.

 

[somethisrandomname]

I disagree, this is due to the bot and not to the game.
No offense, but if the devs spent an hour or two on the bot, they could automate the detection of such events (if they are really the problem), then stop the bot (and restart), or add some other error handling. The error handling in this program is abysmal.
Honestly though, that's all we need.... A built in relogger for the bot and/or the game itself. OR simply some logic we can use to enable our own systems easily, if they continue to refuse to add fundamental features.

A lot of the issues that people are having is due to poor application design / little to no error handling.

I realize they want to protect their IP on this bot, and also obfuscation prevents Bio from easily seeing what's going on on the inside, but had it not been obfuscated, I'd take the tame to implement a hooking system to improve the functionality a large bit.

 

[Ksexasiaris]

Thanks, yes its usually happens when there is a long cutscene or a series of cutscenes...didnt know the trick to kill max sessions..nice to know.

 

[Cryogenesis]

I disagree, this is due to the bot and not to the game.
No offense, but if the devs spent an hour or two on the bot, they could automate the detection of such events (if they are really the problem), then stop the bot (and restart), or add some other error handling. The error handling in this program is abysmal.
Honestly though, that's all we need.... A built in relogger for the bot and/or the game itself. OR simply some logic we can use to enable our own systems easily, if they continue to refuse to add fundamental features.

A lot of the issues that people are having is due to poor application design / little to no error handling.

I realize they want to protect their IP on this bot, and also obfuscation prevents Bio from easily seeing what's going on on the inside, but had it not been obfuscated, I'd take the tame to implement a hooking system to improve the functionality a large bit.

Shame you think its the bot itself... Its mostly to do with the Engine itself. Even bioware devs complain they are restricted and COULD have fixed more stuff if they havent taken stupid decisions in the beginning.
Aevitas and other devs, did what they could and yes there could be more in the bot itself, but from 3.2 it was a struggle to get it back. Plus the botbase/revinue aint that big to make a 100% perfect bot.

Still a relogger would be nice, but that would be full community aspect, to build.

 

[somethisrandomname]

EDIT NOTE: Rephrase of my previous statement,

This bot needs proper unhandled exception handling. Followed by a method to automatically restart the bot(re-run the executable), then after that the bot needs an automatic configuration option (i.e config file) so upon restarting the bot it will resume with the same settings and profile automatically. I'm assuming there will need to be an automated session killing mechanism as well.

Psuedo code:

if ( unhandled exception occurs ) {
       Save.Log
       Kill.Session.Key
       Start.Restarter.Executable
       if ( Restarter.Executable.Was.Used ) {
               Load.Configuration.And.Resume
               }
}

Maybe even for good measure, add a relogger for swtor itself, if it crashes.

 

[Cryogenesis]

EDIT NOTE: Rephrase of my previous statement,

This bot needs proper unhandled exception handling. Followed by a method to automatically restart the bot(re-run the executable), then after that the bot needs an automatic configuration option (i.e config file) so upon restarting the bot it will resume with the same settings and profile automatically. I'm assuming there will need to be an automated session killing mechanism as well.

Psuedo code:

if ( unhandled exception occurs ) {
       Save.Log
       Kill.Session.Key
       Start.Restarter.Executable
       if ( Restarter.Executable.Was.Used ) {
               Load.Configuration.And.Resume
               }
}

Maybe even for good measure, add a relogger for swtor itself, if it crashes.

How do you let that code run, if BW craps out completely?

 

[somethisrandomname]

How do you let that code run, if BW craps out completely?

Really? The only reason it "craps out", is because of unhandled exceptions. So handle them..... all of them.
Besides... I have not had it stop completely, which is really a problem. It spams the log file with useless information, instead of closing up, which would be more useful to us.