Honorbuddy 2.0.0.3626 Discussion Thread

maybe you should implement a anti afk in the bot.. my chars went afk but they kill mobs..

 

please fix this:
on twin peacks BG my bot just stay on mount, after ress on graveyard on Horde Spirit Healer

 

Can you please have HB not dismount flying mounts ?

Will dismount in mid air.

Might wanna fly somewhere in between "jobs"

 

I just wanted to say that the latest release of Hb has been the most stable while running on my different systems. Now, that may be because I only use grind mode and the CC's that come with the program and just buy AH gear every eight to ten levels or so. however, I do run afk alot and the bot has run stable and does not look overly bottish. In my opinion, I dont care how my toons get to 85 so long as they get there and are not detected by Blizz and their Warden program. So far, even with a few bugs to be worked out, this is by far the best bot I have found for leveling and avoiding detection. Keep up the great work Devs and I look forward to even greater bot stability in the new year after the busy Christmas season is over. : )

 

nvm

 

nvm

 

Will we get full working battlegrounds as Christmas gift?

 

remember that he has payed for it.. custumers in first hand

 

Can we PLEASE see some HB support for AT LEAST ghost flying mounts.

Seriously this shit is getting old on corpse runs in certain zones when u die.

I have people who can farm volatile fire or earth or w/e because the mount hits some air and then HB goes spastic.

 

since you're new, i will take it easy on you.

1) you should read previous posts
2) if you truly have discovered a bug, report it to the bugtracker, this is strictly a discussion forum
3) in a previous post, it was said by a dev that twin peaks and gilneas have not been meshed over yet, aka they are not usable YET.

you're welcome

 

You're friggin high as hell, the latest release of HB has been the buggiest and most unstable release yet.

 

You guys seriously need to friggin fix this damn error, it's the most annoying bug in HB right now and it makes it so it's unstable and unafkable and those who say it is you're an idiot. So here's an idea, stop worrying about getting the new features perfect and the paid plugin system and all that worthless junk added to the bot and focus on making the basics of the bot friggin stable, it's sad when the simple grinding bot is buggy and is really unstable.

Code:

[6:32:44 PM:558] Unstuck attempt 5
[6:32:45 PM:903] Unstuck attempt 1
[6:32:45 PM:903] Unstuck attempt 2
[6:32:47 PM:496] Unstuck attempt 3
[6:32:49 PM:426] Unstuck attempt 4
[6:32:49 PM:428] Unstuck attempt 5
[6:32:50 PM:928] Unstuck attempt 1
[6:32:50 PM:928] Unstuck attempt 2
[6:32:52 PM:482] Unstuck attempt 3
[6:32:54 PM:508] Unstuck attempt 4
[6:32:54 PM:511] Unstuck attempt 5
[6:32:56 PM:28] Unstuck attempt 1
[6:32:56 PM:28] Unstuck attempt 2
[6:32:57 PM:856] Unstuck attempt 3
[6:32:58 PM:790] Spell_C::CastSpell(32223, 0, 0x0, 0)
[6:32:58 PM:874] Unstuck attempt 4
[6:32:58 PM:877] Unstuck attempt 5
[6:33:00 PM:782] Unstuck attempt 1
[6:33:00 PM:782] Unstuck attempt 2
[6:33:01 PM:612] Spell_C::CastSpell(7294, 0, 0x0, 0)
[6:33:02 PM:835] Unstuck attempt 3
[6:33:05 PM:164] Unstuck attempt 4
[6:33:05 PM:166] Unstuck attempt 5
[6:33:06 PM:615] Unstuck attempt 1
[6:33:06 PM:615] Unstuck attempt 2
[6:33:08 PM:269] Unstuck attempt 3
[6:33:08 PM:874] Start/Stop button pressed.
[6:33:08 PM:927] Stop called!
[6:33:09 PM:60] System.Threading.ThreadAbortException: Thread was being aborted.
   at n.i()
   at Styx.Helpers.InfoPanel.b()
   at Styx.WoWPulsator.Pulse(PulseFlags flags)
   at Styx.Logic.BehaviorTree.TreeRoot.b()
   at Styx.Logic.BehaviorTree.TreeRoot.a()
[6:33:09 PM:62] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.Logic.BehaviorTree.TreeRoot.a()

 

Its beyond sad, they don't care anymore about how their support is because they have built up a big userbase and are making bank off this bot so they will just keep sending out bugging/crappy releases because they know people still buy it because people are lazy and don't watn to play the game themself.

 

The latest release is working great for me and loving the imporvements ithw questing with the ability to add scripting. Cant wait for flying HB and better PVP support, but great work on a very stable release!

 

I guess you're confused about what the word stable means.

 

I hope you people know it was called [Test] Honorbuddy 2.0.0.3626 for a reason. The [Test] in front of it means it hasn't been deemed worthy of a stable title.

Since you all don't seem to agree on what stable is.. I hope you know thats irrelevant information.. heres the definition of test.

Grow up some please and stop arguing over a program

 

Well if they are releasing it as test right now then they need to stop charging for it while it's in test because charging someone for a program that's in testing faze is bs and it's kinda ripping someone off for their money.

 

You're an idiot.

 

Yep I am high on the 3x85's that I have leveled since the Cata release on this "unstable" HB. Been running 3 HB's between 2 computers and letting them run in grinding mode afk during the day and again over night. Have had 1 crash since the newest test release and that was a wow server issue not a HB issue as far as I can tell. I can understand that it is not perfect but I will say again, I only care about not being detected and getting my little army of toons to 85. This has been the best bot program I have used so far, hands down, even with a few bugs. I tip my hat to the developers and hope for even better coding in the fututre. Keep up the great work and keep solving those problems, one at a time, and know that there are still people out there that know what the word "test" means. : )

 

Honorbuddy is an unfinished program what you are paying for is the right to use the program and if people decide to purchase the program while it is still in testing thats there choice.