[Release] Honorbuddy 2.0.0.5104

[Komonek]

how come the bot shuts down every time? So i havent been for a month or so, ive seen theres new bot so this one, the one had 3 login spaces and this one has 2, 1 username, pass and last for passes but no need for me as i have the lifetime, ok so i login and it runs for like 10 min shuts down and the login window pops up again wtf is wrong?:s

 

[Zacharybinx34]

how come the bot shuts down every time? So i havent been for a month or so, ive seen theres new bot so this one, the one had 3 login spaces and this one has 2, 1 username, pass and last for passes but no need for me as i have the lifetime, ok so i login and it runs for like 10 min shuts down and the login window pops up again wtf is wrong?:s

happens to me all the time lately.

 

[Komonek]

ye every 10 min ... cant bot :s

 

[Lister]

appropriate steps to enable Ryftomate to be safe from it. We have 2 additional developers working on Ryftomate now looking for the next changes in anti-*****.

fresh from the other Bot Forum...

Does that Mean we can still again wait more than a Month for Updates here?

 

[Zacharybinx34]

Do not take this the wrong way please! but I am sorry, but Honor Buddy's potential is being squandered by the lack of updates and key fixes needed.

Don't get me wrong, this program is awesome!

But please please please start listening to the reports and focus on them asap!

Thanks!

 

[Zacharybinx34]

Sometimes on bosses with larger hit boxes the bot won't attack (melee) when it's clearly close enough to do so. I have to stand literally on top of him (or just about) to get it to attack. Nef is this way. I'm using Combat Bot and tried Lazy Raider, both have this problem.

This is a MAJOR problem that needs fixed asap, as it makes using HB in raids nearly impossible for melee.

Any news on this fix?

This + the Singular CC needing some major love!!!!!

 

[webhond]

Do not take this the wrong way please! but I am sorry, but Honor Buddy's potential is being squandered by the lack of updates and key fixes needed.

Don't get me wrong, this program is awesome!

But please please please start listening to the reports and focus on them asap!

Thanks!

this ^^ exactly

how awesome this program is, start fixing the bg issues....

i see bots all around me now, getting stuck on same places...

dismounting on same places... its getting ridiculous...

as said, in multiple threads... you KNOW the errors and bugs

for months... start working on them... PLEASE !

 

[Zacharybinx34]

this ^^ exactly

how awesome this program is, start fixing the bg issues....

i see bots all around me now, getting stuck on same places...

dismounting on same places... its getting ridiculous...

as said, in multiple threads... you KNOW the errors and bugs

for months... start working on them... PLEASE !

I'd pay monthly premium's if that's what it took for the Dev team to actually work on HB's current problems.

Instead, we get a new ui...
Don't get me wrong, it's lovely and all. But these bugs are not being fixed between releases, and they are REALLY starting to add up.

 

[milkyway12]

Please fix the BG Bot Beta. Its really broken , completely un AFKable , and you have to manipulate it some times because its severly bot looking. I much rather it camp a single Flag than running around atm as it gets stuck on things often , maybe focus on AV , and take everything else as its not being supported very much atm ... it seems , i could be completely wrong ... just the BG bot is SUPER botty looking.

 

[chinajade]

as said, in multiple threads... you KNOW the errors and bugs

for months... start working on them... PLEASE !

Please point out the BugTracker's that have yet to be addressed. BugTracker is the formal bug reporting mechanism--not the forums. Although HBcore developers pop in occasionally, they don't spend a whole lot of time in the forum.

The HB developers will spend their time on issues have actually been submitted. Its just a matter of limited developer time, and they're going to go with the issues that actually follow the reporting mechanisms they've established.

If you're not willing to write or supplement BugTrackers, don't expect your issue to be addressed. And no, they don't "know the errors and bugs", if you don't report them properly.


cheers,
chinajade

 

[idx3]

Bot flies to the NCP repair, but not repair, have to manually click repair then press Stop and then start the bot only if it will fly. This problem is only in Hyjal? how to fix it


[9:38:06 PM:213] System.NullReferenceException: Object reference not set to an instance of an object.
at Bots.Gatherbuddy.GatherbuddyBot.#Luc(Object ret)
at TreeSharp.Action.RunAction(Object context)
at TreeSharp.Action.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Sequence.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.Tick()
[9:38:06 PM:213] Cleared POI - Reason Exception in Root.Tick()
[9:38:06 PM:213] Cleared POI

 

[Alandra]

Could you implement thing that HB uses heartstone before going to trainer? I saw that very often he flies to a capital city from far and wasting sometimes 10 mins one way trip. Till 60 (very fast leveling period) he have to run to a trainer very often so it is a lot of wasteing of time.

 

[kayes]

Please point out the BugTracker's that have yet to be addressed. BugTracker is the formal bug reporting mechanism--not the forums. Although HBcore developers pop in occasionally, they don't spend a whole lot of time in the forum.

The HB developers will spend their time on issues have actually been submitted. Its just a matter of limited developer time, and they're going to go with the issues that actually follow the reporting mechanisms they've established.

If you're not willing to write or supplement BugTrackers, don't expect your issue to be addressed. And no, they don't "know the errors and bugs", if you don't report them properly.


cheers,
chinajade

I'm sorry Chinajada, but the bugtracker is useless.

1. There is too time consuming for the users.
2. It takes too much time to post all the bugs that we experience nowadays
3. HB have become too "big" so a regular user who use GB2, IB, Plugins, Different CC's, AB, BG bot, PB etc etc etc would have to spend litterally hours to use it properly.

We bought this, we pay for it, we don't want to spend TIME on something that was suppose to help us save time. If the team can't understand that they must rethink the whole situation.
People have been comlaining for Months! and we are sick and tired of posting logs and spend time on the bugtracker.

There are some serious bugs that alot of people give feedback on. Why the &%!"?# should we spend time on this when a dev can log on a toon, fire up the plugin, bot and CC and test it for them self?

 

[hi1674]

The issue when Bot crashes wow when you stop HB needs to be addressed with highest priority.

[20:37:46:690] Stopping the bot!
[20:37:46:690] Stop called!
[20:37:56:693] Exception in CGWorld__TraceLine:Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. -    at BlueMagic.ExecutorRand.Execute()
   at Styx.WoWInternals.World.GameWorld.#QJc(WoWPoint from, WoWPoint to, Single distance, CGWorldFrameHitFlags flags, WoWPoint& hitPoint) - Honorbuddy
[20:37:56:701] [LazyRaider] Version 1.1.1 Stopped
[20:37:56:705] Exception in CGWorld__TraceLine:Thread was being aborted. -    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
   at (Object , Int32 , Boolean )
   at BlueMagic.ExecutorRand.Execute()
   at Styx.WoWInternals.World.GameWorld.#QJc(WoWPoint from, WoWPoint to, Single distance, CGWorldFrameHitFlags flags, WoWPoint& hitPoint) - mscorlib
[20:37:56:779] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.Logic.BehaviorTree.TreeRoot.Tick()
   at Styx.Logic.BehaviorTree.TreeRoot.Run()
[20:37:56:779] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.Logic.BehaviorTree.TreeRoot.Run()

And baaaaaam wow crashes to desktop.

 

[chinajade]

We bought this, we pay for it, we don't want to spend TIME on something that was suppose to help us save time. If the team can't understand that they must rethink the whole situation.
People have been comlaining for Months! and we are sick and tired of posting logs and spend time on the bugtracker.

I understand your points, and it frustrates the heck out of me, too.

However, the only bugs I ever see addressed are those that are reported in BugTracker. If 'your bug' got fixed, and you didn't report it, its because someone else with the same problem bothered to report it.

Reporting your bug in the forum is as ineffective as looking for your dropped keys "under the light" because you can see there. Its easier to look for them there, but it doesn't get your keys back. Complaining in the forums without commensurate BugTrackers just causes frustration for the individual reporting and the Community.


Do as you will, but I've absolutely no sympathy for people that just like to complain and refuse to help corrective actions commence. It helps no one.

There are some serious bugs that alot of people give feedback on. Why the &%!"?# should we spend time on this when a dev can log on a toon, fire up the plugin, bot and CC and test it for them self?

Darn good question.

Look at it from an economics viewpoint. Developer time is a precious commodity. Do you think they are going to spend their time with sketchy details trying to replicate a problem? Or do you think they'd more likely go after the clearly-defined problems with log files that demonstrate it?

They can only repair a limited number of bugs for each drop. As such, a developer will go for the bugs that are clearly defined and documented. As this allows the most (and most visible) bugs to be addressed in a given drop. This maximizes the value of each drop. Sketchy details, poorly documented, and poorly visible bugs take a back burner. Again, BugTracker is what gets visibility to bugs for a developer--not the forums.

If this were a bigger (or more commercial) company, there would be customer-service representative doing this on your behalf. However, for the prices that are charged for Honorbuddy, that is not possible.


cheers,
chinajade

 

[chinajade]

The issue when Bot crashes wow when you stop HB needs to be addressed with highest priority.

And baaaaaam wow crashes to desktop.

Indeed it is a pain--especially for those poor profile writers.

Raphus has looked at it without success so far. The problem is unpredictable, and intermittent. For me, it almost always happens when Honorbuddy gets confused about quest state (i.e., thinks it needs to do a quest that has already been completed).

This issue is BugTracker #1064, if you've a log you can attach to further help chase the problem.


cheers,
chinajade

 

[kayes]

I understand your points, and it frustrates the heck out of me, too.

However, the only bugs I ever see addressed are those that are reported in BugTracker. If 'your bug' got fixed, and you didn't report it, its because someone else with the same problem bothered to report it.

Reporting your bug in the forum is as ineffective as looking for your dropped keys "under the light" because you can see there. Its easier to look for them there, but it doesn't get your keys back. Complaining in the forums without commensurate BugTrackers just causes frustration for the individual reporting and the Community.


Do as you will, but I've absolutely no sympathy for people that just like to complain and refuse to help corrective actions commence. It helps no one.


cheers,
chinajade

I refuse to spend more of my time posting screenshots, logs and whatnot. Maybe add a line or two before you click "buy" that you have to help out fixing bugs for the devs? Right now nothing of the parts of the bot's I use frequently work poroperly. Absolutely nothing.

 

[hi1674]

i just left an instance and was casting a buff when it happened.(I stopped the bot at that point)

blessing of kings i think.

The crash is more frequent when using an ability/casting a spell

this is the complete scenario from bot-start to crash.

Me personally i think it's the old zoning bug that's not completely fixed.

Bot looses sync when zoning and the injection goes south on us.

My second thought about it is that if HB has a target that generates a targeticon next to your own frame and you stop the bot you're often toast and wow crashes to desktop.

[20:37:42:330] Starting the bot!
[20:37:43:243] Downloaded tilemap Kalimdor
[20:37:43:376] Changed tilemap to Kalimdor, Tiled: True
[20:37:43:380] Changing current profile to level 0 - 86
[20:37:43:439] [LazyRaider] Version 1.1.1 Started 
[20:37:43:536] Cleared POI - Reason Starting up
[20:37:43:536] Cleared POI
[20:37:43:674] Context changed. New context: Solo. Rebuilding behaviors.
[20:37:43:674] All green! building behaviours now!
[20:37:43:674] Solo
[20:37:43:698] sono dentro composite selector
[20:37:43:703] _Inf_of_light_wanna_DL True
[20:37:43:703] _wanna_AW True
[20:37:43:703] _wanna_buff True
[20:37:43:703] _wanna_cleanse True
[20:37:43:703] _wanna_crusader False
[20:37:43:703] _wanna_CS True
[20:37:43:703] _wanna_DF True
[20:37:43:703] _wanna_DP True
[20:37:43:703] _wanna_DS True
[20:37:43:703] _wanna_everymanforhimself False
[20:37:43:703] _wanna_face True
[20:37:43:703] _wanna_gift False
[20:37:43:703] _wanna_GotAK True
[20:37:43:703] _wanna_HoJ True
[20:37:43:703] _wanna_HoP True
[20:37:43:703] _wanna_HoS True
[20:37:43:703] _wanna_HoW True
[20:37:43:703] _wanna_HR True
[20:37:43:703] _wanna_Judge True
[20:37:43:703] _wanna_LoH True
[20:37:43:703] _wanna_mana_potion True
[20:37:43:703] _wanna_mount False
[20:37:43:703] _wanna_move_to_heal False
[20:37:43:703] _wanna_move_to_HoJ False
[20:37:43:703] _wanna_rebuke True
[20:37:43:703] _wanna_stoneform False
[20:37:43:703] _wanna_target True
[20:37:43:703] _wanna_torrent True
[20:37:43:703] _wanna_urgent_cleanse True
[20:37:43:703] _aura_type 0
[20:37:43:703] _do_not_heal_above 95
[20:37:43:703] _HR_how_far 12
[20:37:43:703] _HR_how_much_health 70
[20:37:43:703] _mana_judge 100
[20:37:43:703] _max_healing_distance 40
[20:37:43:703] _min_Divine_Plea_mana 70
[20:37:43:703] _min_DL_hp 70
[20:37:43:703] _min_DP_hp 85
[20:37:43:703] _min_DS_hp 35
[20:37:43:703] _min_FoL_hp 35
[20:37:43:703] _min_gift_hp 40
[20:37:43:703] _min_HL_hp 85
[20:37:43:703] _min_HoP_hp 25
[20:37:43:703] _min_HoS_hp 65
[20:37:43:703] _min_Inf_of_light_DL_hp 70
[20:37:43:703] _min_LoH_hp 15
[20:37:43:703] _min_mana_potion 20
[20:37:43:703] _min_mana_rec_trinket 40
[20:37:43:703] _min_ohshitbutton_activator 40
[20:37:43:703] _min_player_inside_HR 3
[20:37:43:703] _min_stoneform 80
[20:37:43:703] _min_torrent_mana_perc 80
[20:37:43:703] _rest_if_mana_below 60
[20:37:43:703] _use_mana_rec_trinket_every 60
[20:37:43:703] _wanna_move False
[20:37:43:703] _wanna_taunt False
[20:37:43:703] _wanna_HoF False
[20:37:43:703] _wanna_lifeblood True
[20:37:43:703] _do_not_dismount_ooc False
[20:37:43:703] _do_not_dismount_EVER True
[20:37:43:703] _selective_healing False
[20:37:43:703] _get_tank_from_focus True
[20:37:43:703] _ignore_beacon False
[20:37:43:703] _get_tank_from_lua False
[20:37:43:703] _stop_DL_if_above 85
[20:37:43:703] _bless_type 0
[20:37:43:703] _healing_tank_priority 60
[20:37:43:703] Solo
[20:37:43:929] Missing Beacon of light: casting Beacon of Light on Myself at distance 0 with type Buff at hp 100
[20:37:43:930] Spell_C::CastSpell(53563, 0, 0x40000000395CC0F, 0) [158]
[20:37:45:393] no tar found
[20:37:46:690] Stopping the bot!
[20:37:46:690] Stop called!
[20:37:56:693] Exception in CGWorld__TraceLine:Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. -    at BlueMagic.ExecutorRand.Execute()
   at Styx.WoWInternals.World.GameWorld.#QJc(WoWPoint from, WoWPoint to, Single distance, CGWorldFrameHitFlags flags, WoWPoint& hitPoint) - Honorbuddy
[20:37:56:701] [LazyRaider] Version 1.1.1 Stopped
[20:37:56:705] Exception in CGWorld__TraceLine:Thread was being aborted. -    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
   at (Object , Int32 , Boolean )
   at BlueMagic.ExecutorRand.Execute()
   at Styx.WoWInternals.World.GameWorld.#QJc(WoWPoint from, WoWPoint to, Single distance, CGWorldFrameHitFlags flags, WoWPoint& hitPoint) - mscorlib
[20:37:56:779] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.Logic.BehaviorTree.TreeRoot.Tick()
   at Styx.Logic.BehaviorTree.TreeRoot.Run()
[20:37:56:779] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.Logic.BehaviorTree.TreeRoot.Run()

 

[kayes]

Darn good question.

Look at it from an economics viewpoint. Developer time is a precious commodity. Do you think they are going to spend their time with sketchy details trying to replicate a problem? Or do you think they'd more likely go after the clearly-defined problems with log files that demonstrate it?

They can only repair a limited number of bugs for each drop. As such, a developer will go for the bugs that are clearly defined and documented. As this allows the most (and most visible) bugs to be addressed in a given drop. This maximizes the value of each drop. Sketchy details, poorly documented, and poorly visible bugs take a back burner. Again, BugTracker is what gets visibility to bugs for a developer--not the forums.

If this were a bigger (or more commercial) company, there would be customer-service representative doing this on your behalf. However, for the prices that are charged for Honorbuddy, that is not possible.


cheers,
chinajade

Well, the bugs I report, and many others is not what you describe in the bold. It is bugs that go on for release after release.

pathing and instability.

When another release is avaiable and I still see my toons run into walls and run back and forth like a bad bot it pisses me off. Also when I find something that works to a certain degree, I mostly find my toons logged off when I return from work. (crash) Thank god for the releases of reloggers that we also have been requested for maybe a year now.

I do understand your points with BT, but you guys also have to understand that users like myself who don't have much time to use BT would like clearly critical bugs adressed! I don't care about small bugs, im talking about issues that makes the bot useless.

 

[greaterdeath]

I do understand your points with BT, but you guys also have to understand that users like myself who don't have much time to use BT would like clearly critical bugs adressed...

Idk why you feel it takes so much time to use BT; you set it up once (or more if you forget the email address...) and after that its just like posting your problem + full log.

Actually another good thing about BT is you don't have to advertise all the current bugs the bot is experiencing on the public forums. Ie. "When herbing bot always kills mob, harvests herb, mounts up, dismounts, loots mob, mounts & flies away" <-- who really wants potential botcatchers to read stuff like that?