Hi, Not normally one to complain as I have had almost zero issues in the past using HB, simply put, I do proper installs, research forums and try to debug any issues I have on my own. Until lately, HB was a very stable product imho. But now, well, it has become quite unstable and seems to have so many issues. My use of HB is to use a simple Grindbot profile in a small area along with Pokehbuddy plugin to grind level my characters fighting pet battles. So my only active plugin is Pokehbuddy. HB will within 10 minutes to 1 hour suddenly close and close the wow client as well. It seems random how long it will last for but yes, sure enough within an hour it just closes everything. I am attaching logs of it just now happening to 2 accounts at the same time, both simply shutdown almost same time. But it has happened even with only one client running before. The end of the log reads: [19:33:05.549 D] Stop called! [19:33:05.549 Q] Bot Stopped! Reason: Auth Session is invalid [19:33:05.575 D] Behavior flags changed! All -> All [19:33:05.578 D] Activity: Honorbuddy Stopped [19:33:06.588 D] Behavior tree thread did not return within 1000 ms to stop, and was forcibly aborted [19:33:06.588 N] Session is invalid! [19:33:07.718 N] So that is my most pressing issue, I cannot get my HB to run smoothly without this Auth Session is invalid to happen. Also, I need to Task Manager and end the HB process, or it will never log in once relaunched, sometimes to get it working again after this shutdown, a reboot is necessary. Furthermore, 1) HB takes an unreasonable amount of time to "Log in". Sometimes it will sit for 3-4 minutes logging in. It used to take maximum 30 seconds, often faster. 2) HB takes a long time to load simply profiles. Profiles take 3-4 minutes to load, this is something that used to take 10 seconds. 3) The whole HB launcher thing is such a pain in the ass. Used to be so simple, load up WoW, launch HB, profit. Now I need to load the HB launcher, which fires up WoW, then manually log in the character (something I used to do before sure) AND THEN, close HB client and relaunch HB client to prevent numerous other errors (see other thread solutions). However, the above three points are QoL issues and I will deal with them and hope one day the devs fix these problems, but the random complete shutdown is preventing me from actually using HB for what I want, something I used to run 24/7 before all these changes and updates, so I really need some help here to get this to stop happening. Thanks, Azile
for [3] You can still do it that way, just make a shortcut to wow.exe with the noautolaunch64 tag. If you're having a 3-4 minute issue logging in you may want to backup the folder and do a fresh install of hb..
so, a few issues, you say that your running a grind profile. singular seems to think your in a battleground. running the BGBuddy bot in Vale of Eternal Blossoms then whatever the hell [PB] is seems to be locking the thread (i assume its professionbuddy or a another combat routine or plugin) doing that is making HB fail to communicate back to the servers and causing auth failed. download the latest version of honorbuddy from here. http://updates.buddyauth.com/GetNewest?filter=Honorbuddy after that do a CLEAN Install into a new folder, do not re-install to an previous installation and do not copy over any plugins, combat routines or quest behaviors into this new installation.
Hi, Thanks for some answers. I will try to clarify. The reason it had the notation about BGBuddy was this was the first time I was using it on a fresh character and had not changed to Grind Bot at time of loading, BG Buddy is the default, but it was set to Grind Bot before I was running. PB is Pokehbuddy plugin. So I use: - Singular default - Pokehbuddy (no other plugins turned on) - Grind Bot with a few hotspots to move me around my pet battle grind area (does not get stuck or anything weird) Now when you see Grind Bot barking about being stuck and trying to jump and strafe, it is because it is in a pet battle and cannot move. However, I have run this setup with the same errors from grind bot and never had a close down issue before. Literally ran this bot for days on end with the same setup and never had any issue with crash or downtime etc. I have since then, now, completely uninstalled and deleted all HB and plugins. Now reinstalled completely fresh version and added pokehbuddy plugin via SVN checkout, also fresh. I am testing it again to see if there is any change, I will reply back what happens.
And again...run for about 7 minutes...closes down: [01:44:08.355 Q] Bot Stopped! Reason: Auth Session is invalid [01:44:08.430 D] Behavior flags changed! All -> All [01:44:08.465 N] [Gatherbuddy2]: Stopped gatherbuddy after gathering 0 nodes in 2h 3m 21s. [01:44:08.466 D] Activity: Honorbuddy Stopped [01:44:09.477 D] Behavior tree thread did not return within 1000 ms to stop, and was forcibly aborted [01:44:09.477 N] Session is invalid! [01:44:10.863 N] Can somebody please weigh in here on this issue. I have changed nothing about how I do things, my record doing this exact same set up with HB, 3 license was 3 accounts all running the same setup, uptime 34 hours. Now I cannot even keep one account going for 15 minutes...your changes or whatever you "fixed" has ruined what I use HB for. Almost 1 week downtime now over this issue. Please help.
Further insight: It seems to be directly related to when 3 Battle Pets are dead. Whether it is trying to engage a new pet battle or res the pets, I am not sure, but watching it crash, I can see that once all 3 battle pets are dead, it gets that "Session Invalid" message within a few seconds and closes down.
Both my firewall and antivirus have been shutdown already to make sure it was not that...issue still happens. I do not think that is the problem here.
Ok these issues have been solved as far as I can tell. The author of "Pokehbuddy" allowed me to try the beta version and the beta of that plugin seems to not have any of the issues. HB now loads fast, HB profiles load fast and most important, the HB client no longer shuts down like it was. Seems to be working 100% again for me. Thanks for the help all, Azile
i told you it was the plugin locking the thread. theres nothing we could of done for you besides told you not to use it.
