I've got an odd one that has my bot absolutely stopped in its tracks. I'm doing the starting quests in Pandaria as horde and Singular appears to be blacklisting mobs in the middle of a fight. It'll cast several spells on the mob, but then out of the blue, stops fighting and targets another mob and then blacklists it after casting several spells. Looks like either HB or Singular aren't recognizing that the mobs are actually getting engaged. I'm at a complete standstill as there don't appear to be any viable alternative PVE/leveling CCs available for warlocks. Any ideas? View attachment 53632 2013-10-22 21.03 - Copy.txt
update to the lastest version of singular, you can get it from here . http://www.thebuddyforum.com/honorb...-all-one-cc-just-plain-works-version-3-a.html
Do a Clean install into a new folder using the latest beta build. you can grab the latest beta from here. http://updates.buddyauth.com/GetNewest?filter=HonorbuddyBETA
well at least now we know whats causing it. [04:29:16.306 V] Blacklisting F1310304001268EB for 00:03:00 [Type: Interact] - Reason : No reason specified. Caller: at Honorbuddy.QuestBehaviorCore.Extensions_WoWObject.BlacklistForInteracting(WoWObject wowObject, TimeSpan duration) in c:\Users\Tyler\Dropbox\Honorbuddy\bots\hbbeta\Quest Behaviors\QuestBehaviorCore\Extensions\Extensions_WoWObject.cs:line 51 make sure you grab the latest versions of kicks profiles from his svn, if its still an issue after that complete the current quest manually.
Updated to the latest profile and that still didn't work. Completed the quest manually so I'm no longer interacting with those infantrymen so that issue appears to be taken care of. But, now there seems to be a new issue. Now, when fighting multiple banishable mobs, he appears to be banishing one and then keeps trying to cast stuff on the banished mob until the banish wears off. He'll then down whatever mob was banished and continue on. Banishes aren't quite being handled right and there doesn't appear to be a way to disable banishing. Thanks for the help!
Aww shoot, I spoke too soon. He completed the sha quests and now it appears to be working on 'Prowler Problems' and they're getting blacklisted. It's moving to the center of the hunting ground and not targeting the prowlers. When I manually target one, it immediately gets untargeted. Log file is attached, but here's where I'm targeting and it's getting untargeted. 05:30:55.410 D] Activity: Moving to hunting ground waypoint 'hunting ground center' [05:31:02.551 N] (Singular) YourCurrentTarget: changed to: Sha-Infested Prowler.D013 h=100.0%, maxh=135552, d=41.8 yds, box=2.3, trivial=False, player=N, attackable=Y, neutral=N, hostile=Y, entry=66668, faction=14, loss=Y, facing=N, blacklist=N, combat=N [05:31:02.952 N] (Singular) YourCurrentTarget: changed to: (null) Is this now a profile issue that I should be posting somewhere else? I'm sure not having very good luck tonight!
The previous log file didn't have an instance of the prowler getting blacklisted. Here's one that does.
icurnvs, Thanks for the log file. The log file attached is a partial log file but appears to have been created with Log Level set to Diagnostic. Based upon the following line: it appears that the InteractWith quest behavior was the component that initiated the blacklist as CodenameG identified earlier. One of the HonorBuddy Dev's will need to look into this further. Thanks for the post and good luck with your Questing, Bobby53
In case it helps any here's a log file that has about a half hour's worth of activity in it - though there are several starts/stops in it.