Honorbuddy Beta Builds

QFT! This needs fixing, as it renders the bot useless.

 

So true man, i've posted so many screenshots about bot-stucking on mountains...no official reply on this yet...

 

iam glad to hear you are release it today ! i will testing it at any time

 

So, do we need to redownload all Meshes or does Honorbuddy recognize the Changes and redownload needed Meshes?

 

Thank you.

 

when new beta version will be released?

 

Has the mesh been uploaded? My toon is still running up hills begging to be banned.

 

Just noticed that both the Beta version and the .515 version doesnt use ground mounts in BC, LK and Cata when running the quest bot. It does go on the ground but with the flying mount. This creates problems on some quests as flying mount cannot be used in some zones. Ground mount does though work in MoP and Classic (EK, Kalimdor ) zones. Im not sure but this could have something to do with Native flying. FYI iv tried turning it off and on and it does not have any effect on this issue.

Thanks,
/Mupp

 

It should update automatically, but you can check your settings.xml file for the location of your meshes, go delete them and they will be redownloaded automatically.

 

The newest beta will not run any profiles. After I click start (GB2, BGBuddy, Grind, Quest... etc) nothing happens.

Two things I should have added:
1) I know this is a beta build but I wan t to help out
2) I also deleted everything HB related and reinstalled. same issues.

big edit 3) i bet it has to do with the patch this morning. duh.

 

Patch day today, things need to be updated to work with the new build of the game.

 

Ok, Testing new BETA.

Seems to be a movement bugg.. I have attached my log.

well i snip.

[23:41:47.102 D] Activity: Loading Tile/s
[23:41:47.102 D] Loading HawaiiMainLand_30_28
[23:41:47.231 D] Loading HawaiiMainLand_30_29
[23:41:47.372 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[23:41:47.372 N] [Profile Message]: Golden Lotus Daily Quests Profile Loaded
[23:41:47.372 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[23:41:47.382 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[23:41:47.382 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[23:41:47.382 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[23:41:47.382 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[23:41:47.382 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[23:41:47.395 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[23:41:47.396 D] Goal: Flying to <1217.194, 1049.704, 425.9666>
[23:41:47.396 D] [FlyTo-v241(debug) @line 622]: Flying to '<1217.194, 1049.704, 425.9666>': <1217.194, 1049.704, 425.9666>.
[23:41:47.465 D] [LuaEvents] Getting argument values for event COMBAT_LOG_EVENT_UNFILTERED
[23:42:48.168 D] [Flightor]: Unstuck attempt 1
[23:42:59.548 D] Inserting Golden Civet [PetBattle] into the database!
[23:43:21.448 N] Stopping the bot!
[23:43:21.448 D] Stop called!
[23:43:21.448 Q] Bot Stopped! Reason: User pressed the stop button
[23:43:21.455 D] Activity: Honorbuddy Stopped

 

start GB2 and it just mounts and nothing else, says its going for node then blacklists without moving.
[Singular] Your Level 90 Orc Arms Warrior Build is
[Singular] ... running the Gatherbuddy2 bot Solo in Mount Hyjal
[Singular] Context changed, re-creating behaviors
[Gatherbuddy2]: Approaching "Stormvine" at X="4999.991" Y="-2596.585" Z="1423.878"
Mounting: Swift Yellow Wind Rider
[Gatherbuddy2]: Approaching "Stormvine" at X="4999.991" Y="-2596.585" Z="1423.878"
[Gatherbuddy2]: Blacklisting current node after 20 seconds
Stopping the bot!

 

I'm having a similar problem it is the same in bgs and in gatherbuddy that it starts and says moving to next hotspot but it doesnt do anything it just stands there.... an answer would be greatly appericated on this matter.

 

My guy jumps up, walks sideways and backwards in the bg starting areas, and doesnt even start quests.

 

navigation isn't working, same as above posts here

 

Which Bot? (Grind, Quest, Archaeology Buddy, BGBuddy, etc): Questing.

Character Information (Class, Level, Race, Spec): Warlock, 31, Orc, Afflic.

What profile were you using? (if applicable. Please provide a link, or an attachment for the profile): Kick's Questing ( http://www.thebuddyforum.com/honorb...es/50549-kicks-mega-profile-packs-1-90-a.html)

Date the bug occured (please be as specific as possible, eg; Weds, 12th of October, at 5:36 AM EST): Tues, Nov. 27th, 7:51 est

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.
Please explain any steps to reproduce this bug. If the bug is not reproducible, we may not be able to fix it. : The questing bot seems to be functioning in a lmiited fashion, the combat routines take over fine and it seems it knows where it needs to go however there is no movement, it seems to go through its unstuck protocol all the time including mounting and dismounting.

Please list all plugins currently enabled (as well as links to any plugins not packaged with HB by default)
Which Custom Class are you using? Please include the version, and link if applicable. : Birthday(http://www.thebuddyforum.com/honorbuddy-forum/plugins/leveling/88018-birthday-present-user.html) SharpExit ( http://www.thebuddyforum.com/honorbuddy-forum/plugins/monitoring/69201-sharp-exit.html)

Please attach a log for this bug report.
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!) : View attachment 2656 2012-11-27 19.49.txt

 

Inb4 Please attach a log file or it did not happen.

Seriously thought, it has taken 6 odd weeks to get the bot to a it kind of works state some of the time, if you are lucky. This patch is going to throw everything back to the stone age, just like MoP did. Which is perhaps Blizzards new strategy for dealing with bots. Keep those changes coming thick and fast and because the bot makers have no staff resources, their bots will remain unusable for all eternity.

Which is to say, it is not like 5.1 has not been up on the PTR for weeks, so that most of these things could have been dealt with in preparation for its release, leaving just a matter of checking offsets on release day.