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

Honorbuddy 2.0.0.4317 Discussion Thread

Status
Not open for further replies.
This release is crashing my WOW on HB login, with a stack overflow on EIP 0x45454545! Damn nice to locally exploit, for those Who knows what it means <evil grin> ;)
 
Smoogel said:
Is it just me or am I the only one with the error:
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid WoW instance to use Honorbuddy.

Even though im on retail and fully patched?
Click to expand...


Says this to me, from time to time.
I just click it like 6 times and it starts working. xD
 
Can one of the Devs please answer the WOW critical error crash with HB?

I thought this issue had been fixed a few releases back but the last 3 releases have all had it!

Also will we finally see AV fully updated to follow the actual path most players take. Rather than my healer running down to Balinda (as alliance) and getting stomped by a bunch of horde as he tries to solo them. Why is it only AV where the bot stands around for ages after the gate opens?
 
Last edited:
Lockwood said:
Can one of the Devs please answer the WOW critical error crash with HB overnight but not during the day?

I thought this issue had been fixed a few releases back but the last 3 releases have all had it!

Also will we finally see AV fully updated to follow the actual path most players take. Rather than my healer running down to Balinda (as alliance) and getting stomped by a bunch of horde as he tries to solo them. Why is it only AV where the bot stands around for ages after the gate opens?
Click to expand...
As horde I do not stand around for ages, im out with everyone the second the gate opens. However I do take the most retarded path, was hoping for an updated profile sometime.
 
Changelog:

It should properly gather rich mineral veins now.

GB2 in Sholazar Basin while approaching a rich saronite node:

Doing crazy unstuck moves while trying to get down to the node (no, there were NO obstacles between the bot and the node) but never succeeds.

Thanks for bringing another quality release...

[Gatherbuddy v2.0.0.603]:Approaching "Rich Saronite Deposit" at X="4988.196" Y="5373.052" Z="-94.59074"
[Gatherbuddy v2.0.0.603]:Blacklisting current node after 20 seconds
Stopping the bot!
Click to expand...

[14:45:23:568] Activity: Moving to node
[14:45:44:631] Activity: Moving to next hotspot
[14:45:47:829] Start/Stop button pressed.
[14:45:47:833] Stop called!
Click to expand...
 
Where can i bind my Hearthstone when using GB2? I want to farm in Uldum and Im bound to SW.
 
Getting this at startup. Only problem I've had so far. On a Dk btw.

Could not compile CC from C:\Users\David\Bots\HB 2.0.0.4317\CustomClasses\Singular!
File: Hunter.BasicRotation.cs Line: 29 Error: Type 'Singular.SingularRoutine' already defines a member called 'CreateBeastMasterCombat' with the same parameter types
File: Survival.cs Line: 28 Error: Type 'Singular.SingularRoutine' already defines a member called 'CreateSurvivalCombat' with the same parameter types
 
Delete HB and redownload it in an fresh Folder, we had an bug in Singular
 
Did you change around gatherbuddy2? Right now my druid flys always up and down if there is a mob, until it dies ..
 
Bossland said:
or you just read my comment on page 3
Click to expand...

Honestly, I feel slightly bitter with your reply to my comment.

I checked this thread, and this issue was not known at the time (and neither there was a fix or workaround for it). Then I went to create the bugzilla ticket, which took me a while, as I didn't have an account on HB's Bugzilla - I also made sure I added a bit of relevant information, and a workaround for those in the same situation as me (just in case it took you some time to fix it).

In the meantime, the bug was fixed, and the release re-uploaded (which is great). I came back to this thread, just briefly mentioning the bugzilla id, trying to be helpful. (admitedly, I didn't reload the whole thread before doing so)

TL;DR: I tried to be helpful to the developers and the HB community, and would have appreciated a non-smartass reply to my comment.
 
rodarvus said:
Honestly, I feel slightly bitter with your reply to my comment.

I checked this thread, and this issue was not known at the time (and neither there was a fix or workaround for it). Then I went to create the bugzilla ticket, which took me a while, as I didn't have an account on HB's Bugzilla - I also made sure I added a bit of relevant information, and a workaround for those in the same situation as me (just in case it took you some time to fix it).

In the meantime, the bug was fixed, and the release re-uploaded (which is great). I came back to this thread, just briefly mentioning the bugzilla id, trying to be helpful. (admitedly, I didn't reload the whole thread before doing so)

TL;DR: I tried to be helpful to the developers and the HB community, and would have appreciated a non-smartass reply to my comment.
Click to expand...

I hope you don't feel offended; proper bug reports are just what we want! The last couple of days have just been very frustrating for reasons I will not mention, and because of a bunch of annoying bugs.
I hope you will continue to report bugs like you just did!
 
rodarvus said:
Honestly, I feel slightly bitter with your reply to my comment.

I checked this thread, and this issue was not known at the time (and neither there was a fix or workaround for it). Then I went to create the bugzilla ticket, which took me a while, as I didn't have an account on HB's Bugzilla - I also made sure I added a bit of relevant information, and a workaround for those in the same situation as me (just in case it took you some time to fix it).

In the meantime, the bug was fixed, and the release re-uploaded (which is great). I came back to this thread, just briefly mentioning the bugzilla id, trying to be helpful. (admitedly, I didn't reload the whole thread before doing so)

TL;DR: I tried to be helpful to the developers and the HB community, and would have appreciated a non-smartass reply to my comment.
Click to expand...

I also would like to say thank you for taking the time and effort you did in reporting the bug and a workaround for the community. This does not happen enough and is very much appreciated. Bossland owes you an apology and a thank you also.
 
Status
Not open for further replies.
Back
Top