Honorbuddy ignoring body pulled mobs (video/log included)

Hey, I've been experiencing an issue with Honorbuddy for around a week or so now which has made the bot considerably less efficient and more bot like.

Whenever the bot body pulls a mob while trying to engage another, it seems that the target list goes blank until no longer in combat with the body pulled mob. The bot will switch off the combat routine and run through the hotspots of the profile without ever attempting to engage a mob until the body pulled mob has de-aggroed. At that point, the bot chases the now de-aggroed mob until it has reset and then kills it. During all of this, the bot will not loot either.

I don't believe this is an issue with Singular, as I've had the same issue with TuanHA's Rogue routine. While investigating, I noticed that the target list in Singular goes completely blank until the body pulled mob has disengaged.

Steps I've taken so far to attempt to fix this to no avail:

• Disable all addons
• Disable all plugins
• Run different combat routines
• Disabled/enabled multi-pulling in Singular
• Disabled/enabled kill between hotspots
• Ran Singular with(out) Framelock
• Fresh install of Honorbuddy
• Cleared Cache and CompiledAssemblies folders

I'm at my wit's end and have no other ideas about fixing it. Here is a video of the bug in action:

[video=youtube;HjeDQ8CN-qo]https://www.youtube.com/watch?v=HjeDQ8CN-qo[/video]

The video shows two instances of this problem occurring, the first at around 20 seconds in and the second at 52 seconds in. I've also included the log of the footage shown in the video.

Any help resolving this would be greatly appreciated.

 

we need the entire log. not just part of it.

 

That was all that was included in the logs folder. I'll run it again but the log won't match with the video.

 

Here is a full log of it, the bug occurred twice during this, once near the beginning of it and again at the end.

 

Hi, Razzie123, and MANY thanks for that video and log.

The things you've tried to correct the problem is QUITE impressive. Thanks for trying all those, and relaying the results!

We've opened HB-1472 ("Ignoring mobs that have been body pulled") against this issue.

But, we also need to rule out the profile as a potential source of errors. Would you be so kind as to attach it here, so we can make it available to the bug report?

thanks!
chinajade

 

Hey chinajade, no problem!

It's from Kick's collection of profiles on the public SVN. I've attached the copy I'm using.

 

Any News to this? Have the same Problem!

 

no, its been submitted to the devs.

 

This Problem is very old and i dont think this will be fixed soon.
any idea to workarround this problem?