[Release] Honorbuddy 2.0.0.5462

disable flight paths in the bot

if it's my questing profiles ... search for 'flightpath' and change true to false

cheers

 

View attachment 04.12.2011_14_11 1456 Log.txt

 

Gah. That's it Kick, thanks. But that doesn't explain why updating offsets for the patch breaks the entire fucking bot.. it's just a little fishy that shit breaks and nobody knows what broke it or how to fix it..... Oh well. Thanks Kick.

 

Well that sounds....... promising?

 

Here's an idea: Take the code from the last WORKING HB (5387, which works FLAWLESSLY) and just UPDATE THE OFFSETS there, and do NOTHING ELSE. 5387 was working perfectly for me right up until the servers went down for the patch.

 

why do people think the only thing that's needed after a patch is updating offsets? there are a load of things that have changed, many of them not reported in the patch notes, every one of those changes can have knock on effects which can in turn effect other things, which gives you the clusterfuck you have now.

 

Well then, since you have this amazing inside scoop on the behind-the-scenes operation of WoW and HB, why don't you humor us, and lay out just a few of the "loads" of things that have changed? (that the HB core has to worry about, not class changes). Thanks.

 

here's a short piece of my log to the Facing problem:

// it happens for me more often if i'm having an add to attack... he then autoattacks but doesn't use any skills.
// log attached below

PHP:

[13:54:26:828] Cleared POI
[13:54:27:873] InteractDebug:785801480
[13:54:27:889] Interact Done:785801480
[13:54:30:025] Spell_C::CastSpell(774, 0, 0xF330101F0002F952, 0) [929]
[13:54:31:562] Spell_C::CastSpell(8936, 0, 0x480000003BCE7DE, 0) [930]
[13:54:31:583] InteractDebug:785801480
[13:54:31:592] Interact Done:785801480
[13:54:33:579] Spell_C::CastSpell(768, 0, 0xF330101F0002F952, 0) [931]
[13:54:34:007] InteractDebug:785801480
[13:54:34:010] Interact Done:785801480
[13:54:53:185] System.ArgumentNullException: Value cannot be null.
Parameter name: obj
   at Styx.WoWInternals.WoWObjects.WoWObject.IsSafelyFacing(WoWObject obj)
   at Hera.Fpsware.ClawOrMangle.Run(Object context) in c:\Users\HOME\Desktop\Nikolai\bots\domihebro\CustomClasses\Fpsware Druid\Class Specific\Behaviours\Combat.cs:line 1053
   at TreeSharp.Action.RunAction(Object context)
   at TreeSharp.Action.#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.Switch`1.#h.#TF.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 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 TreeSharp.PrioritySelector.#h.#nF.MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at Styx.Logic.BehaviorTree.TreeRoot.Tick()


 

ok, i will try. : ).

 

OMG, you have no idea!

Imagine an electrical junction box with over 1000 connections. Then imagine having to rewire it completely, from scratch, without any reference or instructions (each connection requires testing and retesting). Then add into that if you get it wrong everyone gets banned. Then add that the system is designed to catch you out if you make to smallest of mistakes. This is just an analogy, but I hope it gives you the jist of what is required when each patch comes out.

The HB team are nothing short of geniuses, far beyond you or I. I suggest we all cut them some slack and let them do what they have to without constant complaining.

 

WTB Dev's attention on dramatically increased CPU usage =\

 

Me.IsSafelyFacing (not sure about normal facing) is heavily bugged in this HB version.
Most (saw at least 3 including fpsware paladin and couple singular modes) CCs don't pass Facing check and just do nothing.

To HB Team:
changing Me.IsSafelyFacing(Me.CurrentTarget) to !Me.CurrentTarget.IsBehind(Me) fix the issue and neither me on hunter/druid nor my friend on paladin noticed it bugging out for couple hours.

For example my singular kitty was never ever fighting back (when i left it for hour it died to 30 level mob at mine 83) unless i applied that fix.

 

Cleared out the meshes folder, still happens, this time at 8:28:48. Used Icy Touch then ran into melee range and just auto attacked. Singular CC.

 

Is it working or not because its not for me...

 

You sir, sound like the fucking expert here. What do you even need HB for? Why don't you go develop your own bot since you seem to know so much about it.
Or better yet, why don't YOU take revision 5418 of HB and "just go change the offsets since that is all that is needed"??
Let me know how that works out for you.