Okay so I see all these complaints and I have no idea why everyone is having issues. I loaded up all the new HB required files. I Updated WoW through Bnet launcher. I launched WoW manually and updated HB. I shut it all down. Launched HBRelog 1.1.4 and it works fine.
But my client is up to date, no need to update it manualy. Also got newest HBrelog 1.1.4 and still have this "WoW failed to load and is an error popup; Restarting" issue
This is free and opensource project, so frequent support is not likely to get happen. But usually it is not needed, since the most stuff is cleared on first page.
okay do not know what to say. the weirdo is , im doing the samething updating my client via bnet app , hb is all fresh new clean install , fresh clean hbreloog install and trying to open than closes immadiately all over again. thats kinda mind blowing that some one can with same situation others cant. really weirdo
Did you not setup HBRelog correctly? There are instructions on the first page. If it opens and closes like you say you need to put a Wait Time in the Task section. If that's the problem you're not letting HBRelog know how long to run.
This is an absolute joke. I am sick and tired of coming to my computer and wow is completely off not even in site. Can this thing work for freaking once. What are our other alternatives? Arelog? I just want for once to wake up and see my BOT running and not shut down.
I'd recommend getting Alishas fork. It works like a charm. https://github.com/alishahb/HBRelog/releases If you continue seeing the error with "WoW failed to load and is an error popup; Restarting", run the battle.net app and let it fix the files wow is trying to.
HBRelog works for logging into wow and starting up. It just never at night when wow crashes comes back up properly. I mean never. I would like for once in the middle of night for whatever reason if the bot crashes, servers reboot, that HBRelog get WOW up and running again all by it self. For once.
[16:53:14] System.IO.FileNotFoundException: Could not load file or assembly 'Fasm.NET.dll' or one of its dependencies. The specified module could not be found. File name: 'Fasm.NET.dll' at GreyMagic.ExternalProcessReader..ctor(Process proc) at HighVoltz.HBRelog.WoW.WowLockToken.StartWoW() in D:\GitHub-Alisha\HBRelog\WoW\WowLockToken.cs:line 179 at HighVoltz.HBRelog.WoW.States.StartWowState.Run() in D:\GitHub-Alisha\HBRelog\WoW\States\StartWowState.cs:line 42 at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse() in D:\GitHub-Alisha\HBRelog\FiniteStateMachine\Engine.cs:line 41 at HighVoltz.HBRelog.WoW.WowManager.Pulse() in D:\GitHub-Alisha\HBRelog\WoW\WowManager.cs:line 349 at HighVoltz.HBRelog.TaskManager.Pulse() in D:\GitHub-Alisha\HBRelog\TaskManager.cs:line 62 at HighVoltz.HBRelog.HbRelogManager.DoWork() in D:\GitHub-Alisha\HBRelog\HBRelogManager.cs:line 87
Got same problems as many before me here I can see....when I try to start. It fires up wow, when the wow app starts it quickly turns it down....and does this prosses over an over again saying " Waiting for wow to start...starting wow ..... waiting for wow to start ....starting wow... " and so on
HBRelog is working. Just update to NET 4.6.1 and copy over the new 1.1.4 version over the old one. It should auto-accept the old settings, since they are not stored in the HBRelog folder, but in current windows profile etc. So far, only the authenticator usage fails in the current version.
You have several people complaining that it's not working and having the same issue and you're trying to say it's user error and not an issue with the program nice meme m8
Since it is working here and on several other places, means the program is generally working. Anyone, who cannot run it on its place should at least provide any kind of log, so the HBRelog developer could take a look at it. Any complains that its not working, without any approach towards proving log or so, are classified as trolling, if I am not wrong.
Many, many people have exact same problem and you blame users omg... Newest HB, Newest HBRelog, Newest NET, Newest WoW, and still... here the full log take a look on it:
