Honorbuddy 2.0.0.3626 Discussion Thread

The PvP logic seems to be near perfect, however HB is essentially non-functional me. I've only been able to run it twice, and each time shortly after the second BG it entered, both WoW and HB would crash. A WoW bug submitter would pop up stating a critical error/unhandled exception had occurred and HB would plain just shut down.

Now the two times since I've tried to run HB, right after I hit the start button my system hangs and ctrl alt delete won't work, nothing can be done but rebooting the system. About 5 minutes ago the system hung again, and HB/WoW wasn't even open which makes me think it could be something entirely different, but at the same time this problem has occurred at the exact same time of trying this new release of HB. I'm scanning for viruses now to make sure I didn't pick anything up but I'm quite careful with my PC so I doubt that's the issue.

Regardless, HB really isn't working at all for me. I tried to submit this to you via bug tracker, but when I select a log in the bug tracker window I get an unhandled thread exception which I am going to post here in the form of a screenshot. I hope this information helps you figure out what is causing me all these problems. If it helps I am running 64 bit vista home. If you need anymore information lmk.


Note: because the log is too large to post (1.9mb), I am going to try to run HB again and see if I can replicate the error in a shorter log, and then I'll just post that.

 

Is there anyway we could add Rogue's Draught (Rogue's Draught - Item - World of Warcraft) to the potion list? I have a bunch from grinding/pickpocketing and wouldnt mind using them up for BGs or Grinding, since they do about 12k heals.

 

Put in two bug reports, Twin Peaks horde (flag side) GY couldnt get out of it, running into wall..

Also beware botters of EOTS horde side, jumps off main rock at start trying to get to second rock, misses though and sits there trying to get back up.

 

Just used IB for the first time in ages, it runs like crap on the old version, not targeting mobs when you are standing in 6 of them , hope this fixes it so I stop getting whispers, I'll run a few and upload logs when I get a chance.

G

 

You sure their priority is to elimate bugs, I thought it was to add more bugs since all the releases for the 4.0* patches have been getting more unstable and with more bugs and nothing seems to be getting fixed just things added with newer/same bugs.

 

They have been adding new functions to be able to complete the new quests that the bot cannot accomplish without custom behaviors, the <If> tag, and <UseItem>. They have even started with flight paths and is one step closer to zoning which will open up for 1-85 profiles!

I'm sorry do you have a better bot that you can pull out of your ass . No? Didn't think so..

 

before they worry about getting the questing perfect they should get the other stuff like grinding and pvp stable before worrying about questing.

 

I'm sorry if I don't understand how this all works, but I wanted to see how the bug tracker worked and when I clicked there I see it's somehow connected to Facebook. I thought I was anonymous here, but apparently not there. Isn't that a reason to be a bit concerned?

 

Don't know whats wrong with your HB but I have been in mixed mode for about 10 hours now and about to move it to the newer HB. Looks pretty fine to me. Small errors aren't a huge priority, questing without those 3 things wouldn't be functional right now. Perfect Grinding and PVP < At least working Questorder system. They aren't making it perfect, it broke when Cata hit because of new quests. They are simply adapting on what needs more attention

 

No he is right, there are some serious problems with HB right now, although I'm too lazy to do a log, "I know, i'm sad..."

I get crashes around the clock while grinding, and mixed mode is lucky to get in 1 bg, then crash when trying to grind again...

Although, I have noticed the crashes are far less often with different profiles, so try that wrath and see if you get any results.

Also, take a few hours and just watch it, why did it crash? Was it stuck? retarded? or w/e

And if you really want a fix send in a log with a good explination so we can go forward




The whole cata thing was going to make problems if we liked it or not, it's a real shame, things will get better but m8, it's gonna take time. Trust me, coming back from the gym or a run and seeing a crash every time makes my eyes bleed, but things take time to get better

In my opinion, buy playstation move, i am DESTROYING that thing right now, even I feel fatigued after a couple hours of it, it's really fillin in the gap <3

 

the new version 3626 is awsome didnt crashed for me no logout anymore lol now other people have issues Xd

 

well if every1 else can be happy ill survive

 

2.0.0.3626 not usable for me at all
It crashes after killing the first mob (exception in debug log) - posted it in the bugtracker (#410).
Funny: System.NullReferenceException occurs in CustomClasses\Default Mage\Frost.cs:line 44
If I use Amplify cc, the exception occurs in \CustomClasses\Amplify\Frost.cs

 

just inb4 sleeptime

- in bg he's not waiting anymore until the door is open and the bg begins
he is senseless running against the door totally obvious

- not gilneas the other new bg has much mesh issues

 

uses 3626 for 2mins relises it fucking shit and full of even more bugs and goes back to 3582 that is more stable that this shit..

bugtracker didn't work for me(surprise surprise), so here's the logs that you always ask for and never look at or do anything with.

 

Delete your mesh folder, grow up, try again.

 

Doesn't seem to work for me either, mesh folder deleted but nothing was downloaded.
Edit: It's downloading mesh now after I restarted wow and honorbuddy (both).

 

Why are we hearing so many of the "Oops I forgot X, sorry" or "X forgot to include Y, sorry", etc. ? I mean, don't you guys do any internal testing before you release it to us? Just a quick run of each feature to ensure nothing got broken? This seems especially egregious when the element that is broken is the #*)($&# bug tracker! Come on!