Ever since the upgrade to 220, I have had serious issues with HBRelog not working properly. It will work fine for 1-3 iterations of toons, however, once it gets to the 3rd or 4th in the string of around 20 or so toons I have set up to run, it dies on trying to log into WoW. This did not occur prior to this release, and it is always the same issue. It opens WoW, but, doesn't seem to recognize it is there. If it does recognize it isn't, after minutes, it will attempt to close and reopen it. Which sometimes, it acknowledges is open, and attempts to send the password, however, nothing seems to get sent, and then I get a pop up asking to enter the password in. Which it cycles through, repeatedly, instead of timing out, closing out WoW, and trying again.
If that doesn't occur, or I close WoW out manually, it will try to log in again, and usually fails repeatedly, over and over. I have completely removed HBRelog, and did a fresh/new install, I saved a backup of my settings.xml file, and attempted to import it, and HBRelog crashed. So I manually edited it after creating a fake settings.xml file so it would save a new one, which I removed the whole directory in the save directory as well, and then replaced the new settings file with my old created one. Same issue. It will not work. Would appreciate this being fixed! HBRelog as it stands currently, is broken for use for me, and I can't seem to find any information on here that can correct it.
Here is a copy of the log file from HBRelog as it tries, keep in mind, I had to kill WoW manually to get it to work again, after waiting nearly 5 minutes while typing all this, to see if it would log in:
Code:
[7:39:38 AM] Garrison: Opened communication with HBRelogHelper
[7:49:01 AM] Garrison: Logging on different character.
[7:49:01 AM] Garrison: Attempting to close Honorbuddy
[7:49:01 AM] Garrison: Attempting to close Wow
[7:49:07 AM] Garrison: Starting C:\Program Files (x86)\World of Warcraft\Wow.exe
[7:49:07 AM] Garrison: Successfully closed Honorbuddy
[7:49:07 AM] Garrison: Killing Wow
[7:49:08 AM] Garrison: Waiting for Wow to start
[7:49:08 AM] Garrison: Successfully closed Wow
[7:49:09 AM] Garrison: Waiting for Wow to start
[7:49:17 AM] Garrison: Wow is ready to login.
[7:55:54 AM] System.ArgumentException: wowManager.Globals is null
Parameter name: wowManager.Globals
at HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
at HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogButton1Text()
at HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsErrorDialogVisible()
at HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
at HighVoltz.HBRelog.WoW.WowManager.Pulse()
at HighVoltz.HBRelog.TaskManager.Pulse()
at HighVoltz.HBRelog.HbRelogManager.DoWork()
[7:55:55 AM] Garrison: Starting C:\Program Files (x86)\World of Warcraft\Wow.exe
[7:55:56 AM] Garrison: Waiting for Wow to start
[7:56:05 AM] Garrison: Wow is ready to login.
As you can see, nearly 6 minutes, not 5 passed, while HBRelog sat and did nothing at all, didn't even time out, because it didn't realize it was doing nothing. Would appreciate some kind of fix/resolution. Thanks!