HonorBuddy stopping, as if I clicked stop

So after the crazy Auth issues today I finally got the bot running again and it was working fine, but now I am getting this strange error, When I exit a BG, I get a lot of red text and it just stops
Line 477: [21:49:13.562 D] Stop called!
Line 478: [21:49:13.562 Q] Bot Stopped! Reason: None Given
So I click start and get it going again, it puts me in the random BG queue and then joins the game, gives me more red text and
Line 477: [21:49:13.562 D] Stop called!
Line 478: [21:49:13.562 Q] Bot Stopped! Reason: None Given
( Yes I know I quoted the same lines but I am attaching a log )

Any help would be wonderful I just hit 89 and would really like to finish up to 90
View attachment 2884 2012-09-29 14.46.zip

Code:

Stop called!
Bot Stopped! Reason: None Given
Changed tilemap to Kalimdor, Tiled: True
Changing current profile to Grinding Profile
[BGBuddy]: BGBuddy Session Report:
[BGBuddy]: -----------------------------------------
[BGBuddy]: Battle for Gilneas: Wins - 0 Losses - 2
[BGBuddy]: Isle of Conquest: Wins - 0 Losses - 3
[BGBuddy]: Twin Peaks: Wins - 0 Losses - 1
Activity: Honorbuddy Stopped
[BotEvents] EventChecker 
 threw exception Thread was being aborted. in check
System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.CommonBot.BotEvents.PulseEvents()
   at Styx.Pulsator.Pulse(PulseFlags flags)
   at Styx.CommonBot.TreeRoot.()
   at Styx.CommonBot.TreeRoot.()
System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.CommonBot.TreeRoot.()

 

Tony I did just that, but when I tell it to upload the log file it just stalls and then it wont upload, is there a size limit because this log file is nearly 2MB currently.

 

there we go Tony I zipped it as you wanted and it is uploaded via the site now.




Edit: Any word at all on this? I mean even a yeah, you need a new patch and it should come out in the next update would be nice, just something I am sitting here kinda like uhhh, what do I do?

 

I have encountered the same issue of "does not support Combat for this class/spec combination, in this context!" for the last week or so. However, I have a solution that works with fairly consistent results. I usually only use grindbot or combat bot and the problem can occur while starting up either one. When the bot fails to start, I change between grindbot and combatbot and press start again. It will usually start up normally. At that point, I manually stop the bot and swap back to the desired botbase and press start again. The bot then starts correctly and works as intended. Attached is a log of me going though the procedure. Good luck and hope this helps.