What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

HB ARCHIVES: HBRelog--DO NOT DELETE

[3:56:58 PM] : Honorbuddy is not responding.. So lets restart it
[3:56:58 PM] : Attempting to close Honorbuddy
[3:56:59 PM] : Closing Honorbuddy because it took too long to attach
[3:57:13 PM] : Killing Honorbuddy
[3:57:14 PM] : Successfully closed Honorbuddy
[3:57:14 PM] : starting D:\New Honorbuddy\nieuw honorbuddy\Honorbuddy.exe

This bug has now been present for a very long time and has received many reports, can you please look into it

jemguan said:
why HBRelog tell me the server is offline? i'm server is Area 52!!! is only this server have problem
？
Click to expand...

I believe it has something to do with cross realms.

-M_M- said:
snip
Click to expand...

A quick fix would be to disable Check HB's Responsiveness, but I can't tell you what will happen when HB becomes unresponsive.
 
Last edited:
why HBRelog tell me the server is offline? i'm server is Area 52!!! is only this server have problem
？
 
When I'm running AHBuddy via HBRelog, my HB window closes and reopens two or three times, screwing everything up (max sessions, auctions not getting posted, etc.). This only happens when I'm running HBRelog. I have the "HBRelogHelper" plugin enabled, and only a wait and idle task is applied to the profile.

Any fixes? Everything should be up to date via the SVN.

Edit - attached is a piece of the log... the rest is pretty much the same

[09/16/2014 23:16:58] HBRelog Version 1.0.0.207
[09/16/2014 23:16:58] ******* Settings ********
[09/16/2014 23:16:58] Auto AcceptTosEula: False
[09/16/2014 23:16:58] Auto Start: False
[09/16/2014 23:16:58] Auto Update HB: True
[09/16/2014 23:16:58] Check Hb's Responsiveness: True
[09/16/2014 23:16:58] Check Realm Status: False
[09/16/2014 23:16:58] HB Delay: 3
[09/16/2014 23:16:58] Login Delay: 0
[09/16/2014 23:16:58] Minimize Hb On Startup: False
[09/16/2014 23:16:58] Set GameWindow Title: True
[09/16/2014 23:16:58] Wow Start Delay: 0
[09/16/2014 23:17:00] **ProfileName**: ********* Tasks ***********
[09/16/2014 23:17:00] **ProfileName**: Wait: 12 minutes
[09/16/2014 23:17:00] **ProfileName**: Idle: 40 minutes
[09/16/2014 23:17:00] **ProfileName**: ********* End of Task list ***********
[09/16/2014 23:17:01] **ProfileName**: Starting C:\World of Warcraft\Wow.exe
[09/16/2014 23:17:02] **ProfileName**: Waiting for Wow to start
[09/16/2014 23:17:10] **ProfileName**: Wow is ready to login.
[09/16/2014 23:17:13] **ProfileName**: Setting Window location to X:0, Y:0 and Size to Width 1366, Height:768
[09/16/2014 23:17:13] **ProfileName**: Sending letters to AccountLoginPasswordEdit
[09/16/2014 23:17:14] **ProfileName**: Connecting...
[09/16/2014 23:17:36] **ProfileName**: Login sequence complete
[09/16/2014 23:17:37] Checking for new Honorbuddy update
[09/16/2014 23:17:37] Honorbuddy is up-to-date
[09/16/2014 23:17:37] **ProfileName**: starting C:\Honorbuddy\Honorbuddy.exe
[09/16/2014 23:17:52] **ProfileName**: WoW and HB startup sequence complete
[09/16/2014 23:17:52] **ProfileName**: Opened communication with HBRelogHelper
[09/16/2014 23:17:52] **ProfileName**: Waiting for 13 minutes before executing next task
[09/16/2014 23:19:53] **ProfileName**: Honorbuddy is not responding.. So lets restart it
[09/16/2014 23:19:53] **ProfileName**: Attempting to close Honorbuddy
[09/16/2014 23:19:54] **ProfileName**: Closing Honorbuddy because it took too long to attach
[09/16/2014 23:20:08] **ProfileName**: Killing Honorbuddy
[09/16/2014 23:20:09] **ProfileName**: Honorbuddy process was terminated. Restarting
[09/16/2014 23:20:09] **ProfileName**: Successfully closed Honorbuddy
[09/16/2014 23:20:10] **ProfileName**: starting C:\Honorbuddy\Honorbuddy.exe
[09/16/2014 23:20:24] **ProfileName**: WoW and HB startup sequence complete
[09/16/2014 23:20:24] **ProfileName**: Opened communication with HBRelogHelper
[09/16/2014 23:22:25] **ProfileName**: Honorbuddy is not responding.. So lets restart it
[09/16/2014 23:22:25] **ProfileName**: Attempting to close Honorbuddy
[09/16/2014 23:22:26] **ProfileName**: Closing Honorbuddy because it took too long to attach
[09/16/2014 23:22:40] **ProfileName**: Killing Honorbuddy
[09/16/2014 23:22:41] **ProfileName**: Honorbuddy process was terminated. Restarting
[09/16/2014 23:22:41] **ProfileName**: Successfully closed Honorbuddy
[09/16/2014 23:22:42] **ProfileName**: starting C:\Honorbuddy\Honorbuddy.exe
 
Last edited:
Has anyone figured out what we need to put into the CC to make the pop ups not come up or are we waiting on an update? It seems as though HBRelog does something to HB that even if you aren't using it, it will still look for a CC. It also seems to be random when it asks for one. I can sometimes start a toon and it will run find then the next time the pop up for the CC will be there. Sucsk because I made a nice setup so it goes from toon to toon and does the farming stuff for me. Would be nice to have that run while I'm in class.
 
hi,highvoltz
i found a bug.In the log,after WowClient8 started up,HBRelog went to start WowClient3,but it skiped opening wow window,no process of "Waiting for Wow to start" ,see log:
PHP: 
[09/19/2014 20:21:53] WowClient3: Starting C:\World of Warcraft\Wow.exe
[09/19/2014 20:21:54] WowClient3: Wow is ready to login.

in fact WowClient3 didnt started,HBRelog continued to attach Honorbuddy,but all failed.
so i manually selected WowClient3 entry and pressed the Stop button to close WowClient3,what surprised me is that WowClient8 was closed after i pressed the stop button.

View attachment Log[2014-09-19_08-08-24].txt
 
This is a bit stupid but how do i even open HBrelog? how do i set settings, i dont even know there is any information how to get it start?? I download the SVN but no idea how to open it.
 
Hi all !

First of all i want to thanks Highvoltz again for this wonderful program that is HBRelog !
My request will perhaps seem strange to you but I am tearing my hair for days looking for a solution.

I need to be able to run 2 instances of HBrelog on the same computer but with different "settings". (List of account)
The problem is that as the "settings" are stored in %Appdata% even with different folders containing HBrelog, both have the same "settings" and the same "list of account" (even if i put the 2nd HBrelog files on USB drive)
I wish have two separate "instances" of HBrelog with "settings" for each one. Do you think that is possible? (On the same computer)

Waiting for your reply, sincerely.

(Sorry for my english )
 
First time trying HBRelog since I've been experience issues with Arelog. So far I am impressed, and quite satisfied. I am seeing a lot of users bringing up issues with their HBRelog experiences, however I am not having such issues at this moment. That is not to say their issues are not real, I am simply saying I am not experiencing them myself as of now. So far it's been running smoothly, and I've been very pleased with it. If I notice a bug that hasn't already been posted, I will post it in this same reply.

Thank you for making this program available to the HB Community.
 
Hi. This thing is pretty annoying. I dont know what to do. Its happening very often. I dont see that its not responding. Its working, character running and BAH --->>
Honorbuddy is not responding.. So lets restart it
[18:28:18] Lvl: Attempting to close Honorbuddy
[18:28:19] Lvl: Closing Honorbuddy because it took too long to attach
[18:28:34] Lvl: Killing Honorbuddy
[18:28:34] Lvl: Honorbuddy process was terminated. Restarting
[18:28:35] Lvl: Successfully closed Honorbuddy

Im pissed. Can anyone help with that? thx.
 
I have a question.

How exactly do I get HBRelog to bot 24/7 with breaks in between.

Lets say I want to bot 24 hours and every three hours take a one hour break. Is this possible? How do I set it up?

I know ARelog has strong logging on/off options but its nothing compared to HBRelog.

I see a setting that I can add time to wait or something but does this just wait to log on the first time?

I mean how to I get HBRelog to start and bot for like 4 hours and then take an hour off and then start again for another 4 hours until I tell it to stop doing that?
 
I find HBrelog to relog WOW and HB if HB is not doing anything. If it idles for too long, ie HB stopped, then it relogs. I stop HB a lot to do "maintenance" on my toons.
 
You start HBrelog and it starts WOW and HB. Then HB is not running a profile or bot, in other words it is stopped then HB relog ends the current sessions and starts new ones. A new WOW and New HB session. In my limited experience it seems that this is what is going on with HBrelog ending current sessions and starting new ones.
 
BubbaDad said:
You start HBrelog and it starts WOW and HB. Then HB is not running a profile or bot, in other words it is stopped then HB relog ends the current sessions and starts new ones. A new WOW and New HB session. In my limited experience it seems that this is what is going on with HBrelog ending current sessions and starting new ones.
Click to expand...

I see. But how do you get HBRelog per say to run for 5 hours and take a break for 1 hours and then run again for 5 hours? Does it have the capability to do that?
 
WorldsApart said:
I see. But how do you get HBRelog per say to run for 5 hours and take a break for 1 hours and then run again for 5 hours? Does it have the capability to do that?
Click to expand...

[
mMYjSUP.png


Yes, through the task menu. Idling is when HBRelog logs out and shuts down WoW and then resumes again after the specified time.
 
For those of you where its working fine, what do you have under your combat routines for singlar? That is the only thing that hangs up on me at random but it makes HBRelog useless for what I want to use it for.
 
WorldsApart said:
If I wanted to bot for 8 hours and rest for 12 hours what would that look like?
Click to expand...

One wait task that lasts 8 hours and an idle task lasting 12 hours. I would recommend splitting up the 8 hour period into smaller chunks though, with short idling periods in between.
 
Hello I see this error. Is there another way to download HBRelog? I installed it from the first post. Tried both of the links.

Code: 
[20:03:19] HBRelog Version 1.0.0.207[20:03:19] ******* Settings ******** [20:03:19] 	Auto AcceptTosEula:            False[20:03:19] 	Auto Start:                    False[20:03:19] 	Auto Update HB:                True[20:03:19] 	Check Hb's Responsiveness:     True[20:03:19] 	Check Realm Status:            False[20:03:19] 	HB Delay:                      3[20:03:19] 	Login Delay:                   3[20:03:19] 	Minimize Hb On Startup:        False[20:03:19] 	Set GameWindow Title:          False[20:03:19] 	Wow Start Delay:               20[20:03:22] Bokbokbok: ********* Tasks ***********[20:03:22] Bokbokbok: ********* End of Task list ***********[20:03:23] Bokbokbok: Warning: Possible corrupt \WTF\Config.wtf file at line #:53.\n\tReason: Number of elements does not equal 3[20:03:23] Bokbokbok: Starting Z:\D\Temiz US\Wow.exe[20:03:24] Bokbokbok: Waiting for Wow to start[20:03:29] System.IO.FileNotFoundException: 'fasmdll_managed.dll' dosyasını veya derlemesini ya da bağımlılıklarından birini yükleyemedi. Belirtilen modül bulunamadı.
Dosya adı: 'fasmdll_managed.dll'
   konum: GreyMagic.ExternalProcessReader..ctor(Process proc)
   konum: HighVoltz.HBRelog.WoW.WowLockToken.StartWoW()
   konum: HighVoltz.HBRelog.WoW.States.StartWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()

[20:03:30] Bokbokbok: Setting Window location to X:150, Y:220 and Size to Width 480, Height:320[20:03:31] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:34] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:37] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:40] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:43] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:46] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:49] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()[20:03:52] System.ArgumentException: wowManager.Globals is null
Parametre adı: wowManager.Globals
   konum: HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
   konum: HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
   konum: HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   konum: HighVoltz.HBRelog.WoW.WowManager.Pulse()
   konum: HighVoltz.HBRelog.TaskManager.Pulse()
   konum: HighVoltz.HBRelog.HbRelogManager.DoWork()
 
You must log in or register to reply here.
Back
Top