HB ARCHIVES: Processed Issues from Honorbuddy Beta thread

Well they are trying to get it fix guys just its Blizzard is stepping up the game as well. Its HB devs compare to the blizzard army devs who are working trying to get all botters out of the game. Just give them time

 

IMO they aren't trying very hard. They probably do have an army of devs but their processes are probably so tight nit and complex they probably hire priests to bless the changes. If they wanted the bot gone I'm pretty sure they have the technical expertise to get rid of it, but just have better stuff to be doing I suppose.

 

Trust me Ive tried every BOT thats out there nothing come close to HB that's just my experienced

 

Massive FPS drop on 1 of 4 of my accounts, I can confirm that there seems to be a bug as my other accounts are working fine.

EDIT1: Seems to happen on ghost and on ressing, but after that it's fine.

 

thnx for the new beta its not lagging anymore in Vehicles Kakashi310 the bot is undetected for ages now.

 

update the new beta he just pushed one with the Vehicles lag fix

 

Latest BETA update gives this error. Tried to replace Quest Behaviors folder with an older version but nothing changed.

 

So many questions and hopes after these releases.... and so many no-answers...
CPU usage has gone through the roof with this latest release. The same PC that was running 6 WoW + 6 bots now can't run 1!!! Raiding is totally impossible. How do you raid using Tyrael when game is frozen for 1 sec every 5 sec?!
The next question is "Why do you pay for WoW bot when you can't use WoW with the bot running on it?"
Discuss..

 

I bough it in good faith of the advertising as a "EZ running universal bot".
Meanwhile however, I regret that. It's true... HB gets even worse with each new version.
Unfortunately I can't rescind the licence fees, but I went over to stop word-of-mouth advertising until something wonderful will happen on part of the developers.
New features, grafted on old bugs and nuisances... this can't go well (to give a clue: navigation, mesh, unstuck, flight behavior, etc.).

 

Completely fresh install of 7445.305 yields this error when trying to compile Talented:

[16:59:28.786 N] Compiler Error: c:\Users\poomba\Desktop\HonorbuddyBETA 2.5.7445.305\Plugins\Talented2\Forms\FormConfig.cs(24,43) : error CS1061: 'Talented.TalentedSettings' does not contain a definition for 'FirstUseAfterChange' and no extension method 'FirstUseAfterChange' accepting a first argument of type 'Talented.TalentedSettings' could be found (are you missing a using directive or an assembly reference?)

Log attached.

 

Still too much CPU usage on .307

 

New rev. 313.

 

Hi Guys,

Testing new beta for the quest turn-in/pickup issue and it still happens fairly regularly.

Which Bot? (Grind, Quest, Archaeology Buddy, BGBuddy, etc)
- Quest

Character Information (Class, Level, Race, Spec)
- 90 Human Windwalker Monk

What profile were you using? (if applicable. Please provide a link, or an attachment for the profile)
- Kick's and Brodie's questing profiles

Date the bug occured (please be as specific as possible, eg; Weds, 12th of October, at 5:36 AM EST)
- As of August 3rd, 2013 - roughly every hour

Please explain, in as much detail as possible, what the bug is. (The more detail, the better) If your report has no information, or we can't determine what you're talking about, the bug will be ignored. Please be concise with your report.
- Character will end up with it's back towards a quest NPC (either by flying through it, or by turning in a quest at an NPC next to it that requires it to face the wrong direction). It will then open and close the quest NPC window infinitely until the character is turned around to face the quest NPC.

Please explain any steps to reproduce this bug. If the bug is not reproducible, we may not be able to fix it.
- Run any quest profile that has quest givers near each other, or run any long-term questing profile for a few hours.

Please list all plugins currently enabled (as well as links to any plugins not packaged with HB by default)
- None

Which Custom Class are you using? Please include the version, and link if applicable.
- TuanHA Monk Special Edition
- TuanHA Hunter Public Edition
- Singular

Please attach a log for this bug report.
- Attached - see 15:24:38

Attach a screenshot, if applicable, to help us find the bug. (Note: ensure you do not use the built in WoW screenshot functionality, as it does include a watermark, unless you change the image quality!)
- Attached

 

^^
This. It's a *well* known issue. Do any Devs still actually play/bot wow? Seriously. I am not known for whinging or complaining but it seems like all that has been happening for the last few months is 'Code this, it should work and let the users test it to see'.

 

It is my understanding that this is fixed in a large release that is forthcoming - I'm reporting it for posterity's sake though

 

Hehhehheh,
Screenshotted and noted

 

Things have really slowed down around here. I'm just assuming it's because of many people being away on vacations, etc. Is it the norm for development to slow down in the summers?

 

I love this bot but it really hurts me to see how things are going lately. Too many problems that require us to do this and do that to fix. Seems that long gone are the days of a clean patch that works right out of the box.

 

No slower than it has been for a long time now. They are fast where needed normally.

 

New beta 314. It's now turning to face quest NPCs when it turns in and picks up. Looks like that issue may finally be nixed.

Running an all night test on it now.