What should i try with when it working nice except restarting honorbuddy after like 2 mins all time???
Also - delete any files inside your Honorbuddy 'Logs' folder. Launch the bot again via the HBRelog, if it closes again stop everything and read the new log. It may be an HB error rather than HBRelog stopping the game.
For those having issues with 1.0.0.190 would you try the new version on SVN (1.0.0.191) and let me know if you still have issues with HBRelog starting WoW. HBRelog now uses another launcher program to start Wow as a security measure to prevent HBRelog from getting recorded in Wow crash dumps. Cmd.exe was used to launch Wow in 1.0.0.190 but this would not work on systems that have command-line disabled.
[19:38:15] Sham: Starting D:\games\World Of Warcraft\Wow.exe [19:38:16] Sham: Waiting for Wow to start [19:38:22] Sham: Wow is ready to login. [19:38:23] Sham: Setting Window location to X:1064, Y:704 and Size to Width 316, Height:278 [19:38:24] Sham: Sending letters to AccountLoginPasswordEdit [19:39:06] Sham: Failed to login wow, lets restart [19:39:07] Sham: Starting D:\games\World Of Warcraft\Wow.exe ... :С he does not want to enter a password, and reboots
Now wow starting working, but HBrelog kill HB every few minits... [21:38:52] Ndd: Closing Honorbuddy because it took too long to attach [21:38:52] Ndd: Attempting to close Honorbuddy [21:38:53] Ndd: Closing Honorbuddy because it took too long to attach [21:39:08] Ndd: Killing Honorbuddy [21:39:08] Ndd: Honorbuddy process was terminated. Restarting Without HBrelog it works ok, and pc is working very fast so its not an issue
But why would HB crash? If it does, disable all plugins and run it "clean" - Never had a crash before (other than just after last patch) ^^ If something crashes, it's WoW, and HBRelog will detect it
That was the issue in the first place, then ig got "fixed" by update with even WoW launching dint worked, so were back to the starting point now. View attachment 115158
Would you attach a log from Honorbuddy. I might just get rid of the 'restart if not attached within timeframe' feature since restarting usually won't fix anything.
Please attach the log from Honorbuddy so I can look at it. HB is being restarted because there's an issue with the HBRelogHelper plugin
log: [17:39:10.449 N] Honorbuddy v2.5.9001.716 started. [17:39:10.471 N] Logging in. - Pastebin.com HBrelog kills HB once in ~ 6 mins
Thanks for log. It appears the Honorbuddy start up went fine with no issues. When the HBRelogHelper plugin is initialized it will open a communication pipe with HBRelog and let HBRelog know it's up and running however if HBRelog does not hear from the HBRelogHelper plugin after length of time since HB was started then it is assumed something went wrong and HB is restarted. The only idea I have is some application such as a firewall or AV is blocking the communication between HBRelog and HBRelogPlugin so if you have any of those running check their settings. You can try what virus2001 suggested however it's not likely to help any in this case since the log file doesn't indicate this was the reason HB was restarted. If it was you would see a "Honorbuddy is not responding.. So lets restart it" log entry
View attachment 115216 It turns off while waiting for dungeon, but works fine while gathering with custom botbase, so it seems that for some reason idling is being read as HB malfunction.
