Hey guys, Tony closed the thread, so I'm reposting over here. Having an issue and want to see if it's shared by anyone else and if there is a simple fix I'm missing. When I run GatherBuddy or GrindBuddy ... (regardless of the profile I choose or the CC I run) after a period of time the CC stops working (Singular as well) ... it reverts to only AutoAttacking the mobs ... which takes quite a while and if there are multiple mobs will lead to a quick death. It seems to keep healing itself, but stops attacking. ... running a log now where it paused like this and then restarted attacking a couple of mobs later. I noticed it started a few weeks ago and has been happening ever since. If I close HB and reload/restart it will go back to running full-force ... but eventually will go back to auto-attacking only. Not sure what is causing the CC to break? - if that's what it is. Has anyone else had this issue? I'd like to be able to leave my bot running unattended with trusted profiles ... but, unfortunately, if I want any progress I have to monitor and continually restart the bot. Let me know guys, could just be a simple issue, but I'm not sure ... thanks in advance! View attachment 16260 2015-01-20 03.51.txt Attached log is from a moment ago ... paused once near the beginning and only autoattacked, eventually killed the mobs and resumed attacking a few mobs later. Ended after it stopped attacking all together and just healed for 4 minutes. Let me know if you can see what's going on.
Fresh Installation ... ran tonight, eventually stopped attacking and just started spamming heals ... View attachment 63480 2015-01-22 04.16.zip
Spec for those logs was Retribution. Here is another log from my Shaman instead ... about half way through it stops pulling multiple mobs and stops using Lightning Bolt as an attack. Using Singular. ... this seemed to happen after proximity pulling 4 mobs at once. View attachment 121176 2015-01-22 04.39.txt
No addons ... only plugins are Tidybags. Ran it for 10 hours today ... profile for Boars in FFR ... ended up in Nagrand following Talbuks around, not attacking ... just following and healing.
Alright ... ran a new log ... farmed for a while and eventually just stopped and spammed Sacred Shield ... wouldn't attack. No addons, fresh install ... only Plugin is TidyBags. First log is running bot like normal and it stopping ... then starting and same issue : View attachment 2152 2015-01-27 04.53.zip This is a complete close and restart of HB ... working as normal : View attachment 11656 2015-01-27 05.03.txt
and one more where it stops and continues to spam heals ... no movement, attacking, etc. View attachment 13116 2015-01-27 05.19.txt
update Singular plz https://www.thebuddyforum.com/honor...ar-community-driven-cc-plain-version-3-a.html
Singular updated ... ran less than an hour ... same issue. New log attached. View attachment 31504 2015-01-27 05.17.zip
Hi, Chasetruth, and thanks for all those logs. Let's see if a Buddy Store product is interfering with target selection. It is possible for a product to do this, even if it is disabled or unused on the HBclient-side. Would you be so kind as to disable the streaming of all non-profile Buddy Store products, and show us a fresh log. How to disable streaming of Buddy Store products cheers, chinajade
All BuddyStore products disabled. Same issue, looks like it might be something with moving from mounted to dismounted ... seems like the bot has problem targeting when mounted and moving through hotspots ... when it dismounted and engaged it just stood there and spammed Sacred Shield. Just something to think about. Log attached: View attachment 9880 2015-01-27 05.14.zip
Hi, Chasetruth, We see you've updated Singular to the latest version—kudos for doing this. And, very sorry you're still having issues. This appear to be a bug in Singular that affects the Retribution Paladin (and perhaps other classes). Singular appears to be getting hung up in BuffGroup processing for no apparent reason. We've opened HB-1887 ("Singular perma-stuck in BuffGroup processing on Retribution Paladin missing Mastery") against this issue. At the moment, the only work-around we can think of are to change specs and see if that will abate the problem. Even though we've opened a bug report, you may also want to report this to the Singular thread, and which may move it higher on the priority list. cheers, chinajade
Thanks for the log. The log was very useful in providing the details needed to identify a bug in the Singular buffing logic where it is attempting to decide upon Blessing of Kings or Blessing of Might being needed. This bug generates a lot of log messages. The overhead of this could be interfering with the normal operation of the bot, although what I am seeing is just really large log files for Paladins. This will be fixed in the next release of Singular. To work around this issue now, do the following: - Click Class Config - Click the Paladin tab - Change Blessings from Auto to any other value The bug is in the Auto selection logic, so choosing a specific Blessing will work around the problem for now. Note: you mentioned your character sitting still doing nothing. The bug identified above does not cause a stoppage of HonorBuddy. At worst it would slow things down. More typically it just results in large log files for Paladins. If you follow the workaround steps I provided and still encounter the issue of your character stopping and not moving, you will need to do the following: - Close HonorBuddy and reopen HonorBuddy (Do Not Press Start yet...) - Click Class Config - Click Debugging tab - Click Trace Behavior Calls - Click Save & Close - Click Start in HonorBuddy Let this run until the point where you are stuck, allow to run for another minute or so, then press Stop. This will create a log file for you to provide so we can look into the stoppage further, as it is a separate issue. Note: the Trace Behavior Calls option outputs a tremendous amount of information. After posting the log be sure to uncheck that option in HonorBuddy and click Save & Close. Thanks and good luck with your Paladin, -Bobby53
Thanks guys, I'll work in the new log now. Could all this be avoided if I just used a Class Routine other than Singular?
