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

Aash's HBRelog improvements & support thread

yarmateys said:
How did you obtain my changes? I had pushed several changes to HBRelog that are probably not compatible with aashz's relog program. Can you make sure you're using commit bf6b71fb76a4ff5bbb9051e0e1104f7d9bbe6cd3 ? In fact, try to just re-clone the repo from https://github.com/KSUMatt/HBRelog at master (which should be the commit I listed above). Update the build.cmd to point to your Honorbuddy install location, and then rebuild. Make sure you run the newly built binary in bin\Release\HBRelog.exe (check the modified time to verify it just got built).

I tried these steps this morning (I normally build from visual studio) and I was able to get it to work successfully. Good luck keep me posted.
Click to expand...

I'm used to be on the knowledge side of a topic, but this time I'm totally lost. First of all, thank for your time yarmateys.
I have no idea what a fork is, what a commit is, what cloning is, etcetera...

Here is what I did:
1- Wiped old aashz relog installation to start from scratch,
2- Downloaded and unzipped aashz relog sources,
3- Manually applied your changes to the three files listed here: https://github.com/KSUMatt/HBRelog/commit/bf6b71fb76a4ff5bbb9051e0e1104f7d9bbe6cd3 ,
4- Built aashz relog as showed in first page video by running build.comd, giving HB installation folder when prompted by the installer.

Compilation resulted in no errors, but HB still being killed.
This evening I'll give a new try!
 
Blackrussian said:
I'm used to be on the knowledge side of a topic, but this time I'm totally lost. First of all, thank for your time yarmateys.
I have no idea what a fork is, what a commit is, what cloning is, etcetera...

Here is what I did:
1- Wiped old aashz relog installation to start from scratch,
2- Downloaded and unzipped aashz relog sources,
3- Manually applied your changes to the three files listed here: https://github.com/KSUMatt/HBRelog/commit/bf6b71fb76a4ff5bbb9051e0e1104f7d9bbe6cd3 ,
4- Built aashz relog as showed in first page video by running build.comd, giving HB installation folder when prompted by the installer.

Compilation resulted in no errors, but HB still being killed.
This evening I'll give a new try!
Click to expand...

That all sounds correct... you are using the new binary in bin\Release\Honorbuddy.exe ? Did you confirm it was modified/update (check file date/time)

EDIT: There are definitely reasons why this patch could not work... I'm not totally familiar enough with HB to have any kind of authority on it. The patch looks for a window created by the HB process that has a window title that starts with "Honorbuddy"... are there different languages or locales of Honorbuddy that would change this window title? Is there an option in HB to change the window title? More importantly, does your Honorbuddy window start with "Honorbuddy" ? (it's case sensitive...)
 
Last edited:
yarmateys said:
That all sounds correct... you are using the new binary in bin\Release\Honorbuddy.exe ? Did you confirm it was modified/update (check file date/time)

EDIT: There are definitely reasons why this patch could not work... I'm not totally familiar enough with HB to have any kind of authority on it. The patch looks for a window created by the HB process that has a window title that starts with "Honorbuddy"... are there different languages or locales of Honorbuddy that would change this window title? Is there an option in HB to change the window title? More importantly, does your Honorbuddy window start with "Honorbuddy" ? (it's case sensitive...)
Click to expand...

Yep I'm using the updated HBRelog.exe, and yep the HB windows is named "Honorbuddy - Attached to WoW with ID nnnnn".
 
garoboldy said:
Any info on this yet?
Click to expand...
Sorry I am not familiar enough with dungeonbuddy to answer this question... my guess is yes you could with the appropriate profile, bot base, and possibly plugin as well...

Blackrussian - sorry I have not had time to take a look at it this further yet. I think I will have time in the next few hours.
 
yarmateys said:
Sorry I am not familiar enough with dungeonbuddy to answer this question... my guess is yes you could with the appropriate profile, bot base, and possibly plugin as well...

Blackrussian - sorry I have not had time to take a look at it this further yet. I think I will have time in the next few hours.
Click to expand...

It's fine, you're already doing more than you should. Take your time.
 
Blackrussian said:
It's fine, you're already doing more than you should. Take your time.
Click to expand...
At this point... I really don't know why it wouldn't work. I could add a commit that enumerates the Honorbuddy windows and their titles and log them to the log to aid in debugging... but I am kind of stuck on this one. You also are likely the second person to ever try this patch (first being myself). Besides making sure that you made the changes to the files correctly... not sure how to proceed debugging.

Can you try just downloading the source directly from here: https://github.com/KSUMatt/HBRelog (click download ZIP) and building that and running that? You had mentioned that you had previously downloaded, made the same changes, and rebuilt... but maybe you didn't quite make the same changes? Just guessing at this point.
 
yarmateys said:
At this point... I really don't know why it wouldn't work. I could add a commit that enumerates the Honorbuddy windows and their titles and log them to the log to aid in debugging... but I am kind of stuck on this one. You also are likely the second person to ever try this patch (first being myself). Besides making sure that you made the changes to the files correctly... not sure how to proceed debugging.

Can you try just downloading the source directly from here: https://github.com/KSUMatt/HBRelog (click download ZIP) and building that and running that? You had mentioned that you had previously downloaded, made the same changes, and rebuilt... but maybe you didn't quite make the same changes? Just guessing at this point.
Click to expand...

Unfortunately not working :(
 
Not sure if I need to set this in the issue tracker or here.
[Bug]
When setting a WaitBotStop followed by a Logon, it will relog and launch honorbuddy but will not start the bot. This seems to happen only when using non "profile" botbases like Garrisonbuddy / Garrisonboss / Dungeonbuddy / BGBuddy / etc.

Edit:
To clarify this happens even during the first logon of the sequence.

character 1 - garrisonboss or any botbase
waitbotstop
characters 2 - random botbase

Startup opens WoW and HB, but even for character 1, it will not "start" HB. You have to manually click the start button.
 
Last edited:
garoboldy said:
Not sure if I need to set this in the issue tracker or here.
[Bug]
When setting a WaitBotStop followed by a Logon, it will relog and launch honorbuddy but will not start the bot. This seems to happen only when using non "profile" botbases like Garrisonbuddy / Garrisonboss / Dungeonbuddy / BGBuddy / etc.
Click to expand...

I'm having the same issue
 
HB5351F38 said:
I'm having the same issue
Click to expand...

Yeah, I've done some testing so far and it will not start the bot even with a profile loaded in the "Questing" botbase. I'm guessing there was a code change on the HB side and the Developer of this fork needs to update the code for it to use the start button.

The original HBRelog works just fine.
 
garoboldy said:
Yeah, I've done some testing so far and it will not start the bot even with a profile loaded in the "Questing" botbase. I'm guessing there was a code change on the HB side and the Developer of this fork needs to update the code for it to use the start button.

The original HBRelog works just fine.
Click to expand...
The original will not close honorbuddy for me, so I cannot log on to different characters. The only work around I have for this is having multiple HBRelog profiles, the only way I can get it to start is to hit edit and check "Auto start bot" under the bot tab. However this will only work for the first character which is why I need to set up multiple HBRelog profiles. Each profile for a different character.
 
HB5351F38 said:
The original will not close honorbuddy for me, so I cannot log on to different characters. The only work around I have for this is having multiple HBRelog profiles, the only way I can get it to start is to hit edit and check "Auto start bot" under the bot tab. However this will only work for the first character which is why I need to set up multiple HBRelog profiles. Each profile for a different character.
Click to expand...

You always want to have "Auto start bot" checked or you manually have to start things. Some of us are having the issue of not starting or swapping properly even with autostart enabled.
 
HB5351F38 said:
The original will not close honorbuddy for me, so I cannot log on to different characters. The only work around I have for this is having multiple HBRelog profiles, the only way I can get it to start is to hit edit and check "Auto start bot" under the bot tab. However this will only work for the first character which is why I need to set up multiple HBRelog profiles. Each profile for a different character.
Click to expand...

if you want to setup individual profiles for each toon.

Logon
Wait
Idle (1 min)- Have this.
Start HBRelog Profile
Stop HBrelog Profile



HB should auto close after 20 seconds of the window it is attached to closing.
 
Hi there... is there any way to set this up to run a profile-->finish the profile-->log on to next toon->run the same profile--> and so on ?
 
When was this last updated? I've been having better luck with the Highvoltz original version than this one lately... :/
 
Anyway to make switch toons on both a WaitBotStop AND Wait Timer? for example:

Logon
WaitBotStop and/or Wait: (60 minutes, whichever comes first)
Logon

Reason being that some profiles may get stuck due to a meshing issue for example, but the Bot never "stops" thus running on forever. The Wait timer would help to ensure its only stuck for a maximum of 60 minutes in this example before moving on to the next task. Additionally, in some occasions that the Bot DOES stop, it does not correctly move on to the next task. Is this a known issue? It works about 90% of the time.
 
You must log in or register to reply here.
Back
Top