HonorBuddy Error Spam in BG's

[swiftzoom]

I use HonorBuddy(HB) for the PVP setting to autoqueue into BattleGrounds(BG) and on occasions after being left on for a while, it'll enter the BG and sit there doing nothing in spawn spamming something like this in the Debug Log(I don't know if this is exactly what it spams in the beginning of the error, but the following repetition part is the same I do believe):

[1:14:44 PM:755] System.NullReferenceException: Object reference not set to an instance of an object.
at Cimmerian.Deathknight.AutoAttack() in c:\Users\Administrator\Desktop\SF Folders\Honorbuddy 2.0.0.3740\CustomClasses\Default Death Knight\Cimmerian.cs:line 5503
at Cimmerian.Deathknight.Combat() in c:\Users\Administrator\Desktop\SF Folders\Honorbuddy 2.0.0.3740\CustomClasses\Default Death Knight\Cimmerian.cs:line 2143
at Bots.Grind.LevelBot.ad(Object A_0)
at TreeSharp.Action.RunAction(Object context)
at TreeSharp.Action.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Sequence.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.b()

When I try to stop the bot and start it again, it states in the normal Log that "Object reference not set to an instance of an object." or something, I haven't had it happen yet this morning, but it's happened multiple times after being on for a while. I'm not entirely sure why it does this, also on other occasions, it's queue never pops so it sits there waiting for the queue for hours on end and it never pops. However, I'm guessing that has something to do with Blizz's end of the spectrum, or is it something to do with HB? Thanks for your time and assistance.

 

[Scottymc]

I get this too!