HB ARCHIVES: HBRelog--DO NOT DELETE

[jswow]

I keep getting this error "Could not find a HBRelog profile named". It flashes red every second. It doesn't appear to be preventing anything from working properly as of now so I am assuming I just have something typed wrong or something? like I said,, wow opens up fine as does HB, and the profile that I am currently running seems to be running fine also. I just don't want this to become an issue in the future because im sure its not suppose to be happening....any help would be appreciated, thanks!!!

 

[tyrael]

Any1 know if there is any way to use HBrelog with Buddy Store profiles?
Any way to make it load buddy store profiles?
_______________________________________________________________________

*EDIT

Found a way to do it - "Honorbuddy is now able to load store profiles via the -loadprofile command-line argument. Additionally, the store profile browser will now display the full path of selected profile at the bottom, making it easy to copy it for use in a relogger. Also users can now copy the store profile path into clipboard by right-clicking a profile and selecting the 'Copy Path' menu item."

My bad I didn't notice that, just copy the full path displayed whem u r selecting the profile from store and put it on profile path in HBrelog.
Hope this helps some1 with the same question.

 

[Hardcore15]

Maybe the inactivity trigger built into HB itself triggers, which makes HBrelog stop the HBrelog profile with the error code 12.

Next time post a log and someone can say for sure.

I have active HBreloghelper and honorbuddy responsiveness... need changue that? for automatic restar when the honorbuddy stop for fail quest, etc etc?

 

[Abyssion]

Question: is it possible for HB relog to never stop? I get the code 12 pretty often saying HB should be stopped without relogging. How do I turn that off?

 

[Hardcore15]

Help, WHY my HBRelog dont detect when the honorbuddy stop, (Stop, not crash or frozen only STOP)

 

[Abyssion]

Question: Whats a HB Relog Profile in the task manager?

 

[Tiebiex]

If you configure hb relog ( i. e. Farming in nagrand) you have a profile.

With that task you can start and stop other hb relog profiles.

 

[umshakalaka]

This seems to be a major issue now: HBRelog seems to wait without doing anythign else if even only one acc is waiting in realm queue (obviously doesyn't wait in queue for more than one accoutn at the same time either), is there any way to maybe adjust it in settings? ("check realms status" doesyn't do anything), there's only "waiting on profile 17 ro release lock", Im not albe to use HBRelog anymore right now, since almsot every acc have to wait in 1h long queue, and they can't even wait at the same time...

 

[Angelus]

I never noticed it before, but now that my chars get DCs a lot, there are some major issues since the last build (not sure if al came after the last build)

#1: Since you worked your way around the "Closing Honorbuddy because it took too long to attach" HBRelog seems to have trouble in closing HB clients, doesn't happen all the time, but it happens fairly often. Especially when using the "Change HB profile" function.

#2: When the HB client crashes, HBRelog doesn't shut it down anymore. Check HB's responsiveness has been checked. I believe has got something to do with the previous one?

#3: I sometimes get the problem that HB wants to login to the WoW client just as the WoW client is finished with the loading screen. BUT then the WoW client has a loading screen again right after it is finished with the other one or before HB is done with initializing, which results in HB not able to login and HBRelog doesn't shut the HB client down. "We couldn't find a free WoW process to attach. Please make certain your toon is standing in game world and you are running latest version of Honorbuddy" I guess this one also has something to do with the previous ones?

#4: Since the last build I have found another huge gamebreaking bug. When the WoW client gets a dc LogMeOut or HBRelog shuts it down, HBRelog boots my clients up one for one. Except once in a while the profile for, example, WoW2 doesn't login to WoW2 but logs in to WoW1, etc. The relogger now stops doing anything for the WoW.exe in question because it cannot find the character name.

I believe this bug happened here and to this char, but can't say for 100%: [11/14/2014 17:40:40] B: Character name not found. Double check spelling

The attached pictures are showing problem #4, problem #2 and problem #3

[11/14/2014 17:04:41] E: Starting C:\Program Files (x86)\World of Warcraft second\Wow.exe
[11/14/2014 17:04:41] E: Honorbuddy process was terminated. Restarting
[11/14/2014 17:04:42] E: Wow is ready to login.
[11/14/2014 17:04:42] E: starting C:\Honorbuddy\New\Honorbuddy.exe
[11/14/2014 17:04:44] E: Login sequence complete

Now that I look at it again, the whole login process seems odd. Perhaps it is a problem #5 Perhaps it completely skipped the WoW client login process? This is how the normal login process takes place:

[11/14/2014 16:53:15] E: Starting C:\Program Files (x86)\World of Warcraft second\Wow.exe
[11/14/2014 16:53:16] E: Successfully closed Honorbuddy
[11/14/2014 16:53:16] E: Waiting for Wow to start
[11/14/2014 16:53:20] E: Wow is ready to login.
[11/14/2014 16:53:21] E: Setting Window location to X:2966, Y:532 and Size to Width 300, Height:200
[11/14/2014 16:53:23] E: Sending letters to AccountLoginPasswordEdit
[11/14/2014 16:53:45] E: Login sequence complete
[11/14/2014 16:53:45] E: starting C:\Honorbuddy\New\Honorbuddy.exe

[11/14/2014 17:06:43] E: Closing Honorbuddy because it took too long to attach
[11/14/2014 17:06:43] E: Attempting to close Honorbuddy
[11/14/2014 17:06:44] E: Honorbuddy process was terminated. Restarting
[11/14/2014 17:06:44] E: Successfully closed Honorbuddy
[11/14/2014 17:06:45] E: starting C:\Honorbuddy\New\Honorbuddy.exe
[11/14/2014 17:08:45] E: Closing Honorbuddy because it took too long to attach
[11/14/2014 17:08:45] E: Attempting to close Honorbuddy
[11/14/2014 17:08:46] E: Closing Honorbuddy because it took too long to attach

And in the screenshot attached that shows the map you can see that there is a gap between those, yet HBRelog shows that activity at 17:06:43, but HB itself does not. Which leads me to believe that this is problem #2 and problem #3

Now that the other chars are standing still, LogMeOut kicks them out after a while, HBRelog restarts them twice, but the second time something goes wrong and HBRelog logs into the wrong account leading to problem #4.

Also this is just purely speculating by now, but if you look at the following timeframe. You can see that the WoW client for E was up at the time HBRelog logged into the wrong account for B, perhaps this is the connection between problem #3 and 4#, but I doubt it.

[11/14/2014 17:43:34] B: Attempting to close Wow
[11/14/2014 17:43:34] E: Attempting to close Wow
[11/14/2014 17:43:35] B: Successfully closed Wow
[11/14/2014 17:43:35] E: Successfully closed Wow

It was I btw who stopped and started the clients at that timeframe.

HBRelog, HB and both WoW clients are configured to always run as an administrator and I have these problems on two computers. Of which one has been completely formatted yesterday.

Anyways, good luck and I hope I was clear enough. Please lmk if you need anything else.


Okok, it just happened again. Make that problem #5

[11/15/2014 13:32:52] [11/15/2014 13:32:41] A: Wow is ready to login.
[11/15/2014 13:32:42] A: Setting Window location to X:2623, Y:532 and Size to Width 300, Height:200
[11/15/2014 13:32:44] A: Sending letters to AccountLoginPasswordEdit
[11/15/2014 13:32:50] B: Login sequence complete
[11/15/2014 13:32:52] B: starting C:\Honorbuddy\New\Honorbuddy.exe
[I][B][11/15/2014 13:32:52] C: Starting C:\Program Files (x86)\World of Warcraft\Wow.exe
[11/15/2014 13:32:53] C: Wow is ready to login.
[11/15/2014 13:32:54] C: Login sequence complete[/B][/I]
[11/15/2014 13:33:06] A: Login sequence complete
[11/15/2014 13:33:07] B:  WoW and HB startup sequence complete
[11/15/2014 13:33:07] B: Opened communication with HBRelogHelper
[11/15/2014 13:33:07] B: Waiting for 1441 minutes before executing next task
[11/15/2014 13:33:08] A: starting C:\Honorbuddy\New\Honorbuddy.exe
[11/15/2014 13:33:08] D: Starting C:\Program Files (x86)\World of Warcraft second\Wow.exe
[11/15/2014 13:33:09] D: Waiting for Wow to start
[11/15/2014 13:33:12] A:  WoW and HB startup sequence complete
[11/15/2014 13:33:12] A: Opened communication with HBRelogHelper
[11/15/2014 13:33:13] A: Waiting for 1441 minutes before executing next task
[11/15/2014 13:33:13] D: Wow is ready to login.
[11/15/2014 13:33:14] D: Setting Window location to X:2966, Y:532 and Size to Width 300, Height:200
[11/15/2014 13:33:16] D: Sending letters to AccountLoginPasswordEdit
[I][B][11/15/2014 13:33:23] C: starting C:\Honorbuddy\New\Honorbuddy.exe[/B][/I]

Completely skipping login procedure and giving the "We couldn't find a free WoW process to attach. Please make certain your toon is standing in game world and you are running latest version of Honorbuddy"

Lmk if you need the log to this one.

Oke, I just pressed stop on the HBRelog profile that had this error and a whole another HBRelog profile got shut down. I'm guessing this has something to do with me booting from two different WoW clients at the same time.

Or HBRelog recognising the wrong WoW client.

Edit-

Also if it helps, every time before the new build when I stopped the HB client while HBRelog was still running, HBRelog would shut down the HB client because it knew it wasn't running anymore and reboot it.

It stopped doing that.

 

[frames]

Why HBrelog is always choosing the wrong realm and get into a queue?

 

[Angelus]

Why HBrelog is always choosing the wrong realm and get into a queue?

Sounds like you raffed yourself with a char from another server?("the server that HBRelog chooses") The WoW client makes you login into the server from the RAF recruiter.

 

[ressurrectin]

How often is it supposed to check for Realm status if the realm is currently offline?

 

[HB7149I36]

Anyway to increase the "waiting to connect" timer? Lik now when the servers are so slow and laggy, HBRelog closes wow as it took to long to connect, but realy it's of server lag and i did get a "succes" satus..
Als, i'm using a CC, "Richie's Discipline Priest PvP Combat Routine [Public Edition]" but when i try to specify that as a CC, it does nto get recognised? :/

 

[Adrimofo]

Hey!

First time trying HBRelog, but during setup I followed the instructions from A - Z..
What HBRelog does now is start WoW with email already typed in, but not typing password.
In HBR it says "Waiting for WoW to start" or something like that..

It did work earlier, but that was only for a brief moment where it logged in on the correct character and started HB. When HB had loaded it closed WoW and started the cycle, back to "waiting for wow to start" and no password.

Anyone know what this might be?
Attached log, as we're supposed to.
View attachment Log[2014-11-15_06-39-18].txt


Thanks in advance,
Adrimofo

 

[nebus]

mine doesnt type in password anymore.

 

[y2krazy]

Is <CustomAction Code="HBRelog.SkipCurrentTask(HBRelog.CurrentProfileName);" /> still viable? Doesn't seem to work for me.

 

[bindy]

Hi. I'm using HBRelog since 5 days. Till yesterday everything worked fine. But since yesterday "Change HB Profile" dosen't work any more.
The Log says:

[18:59:32] Framing_Profile: Wait complete
[18:59:33] Framing_Profile: Closing Honorbuddy because it took too long to attach
[18:59:33] Framing_Profile: Loading Honorbuddy profile: Framing_Profile and C:\Users\Me\Downloads\Honorbuddy\Profiles\Me\MoP\ProfileXYZ.xml
[18:59:34] Framing_Profile: Closing Honorbuddy because it took too long to attach
[18:59:34] Framing_Profile: Waiting for 67 minutes before executing next task
[18:59:35] Framing_Profile: Closing Honorbuddy because it took too long to attach

But Honorbuddy neither changes Profile or Closes.

Do you have any suggestion?

Thanks,
Alex

 

[xperiadudu]

often times when using this program i get the error "we couldn't find a free WoW process to attach to" when starting up multiple clients and bots. any solutions to this? doesn't happen always, but often enough for it to be annoying.

 

[vboom]

Could I request a feature? Could you create an option for Anti-AFK. I use your program with Windows Task Scheduler to automatically run every morning after rolling restarts to ensure I maintain my position on my super-high pop realm. Rather than running HB I'd love it if you could just have my character jump every 1-5 minutes to prevent being kicked back into the queue. Would this be possible?

 

[Tiebiex]

You can use the anti afk botbase for that or just go in an instance and let a lvl 15 enemy attack you