Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
MaxMuster, Good point. Will add in the next release. Since its clear you experienced this, please be sure to attach your complete debug log with future issue/change request posts so it is clear what versions you are using, what options are in effect, which spec you are running, etc. etc. etc. Thanks again and good luck with your Rogue, Bobby53
Yeah, I know I should have added a log. I'm a regular around here and failed to do so, which is a mistake on my part, lol. I appreciate you trying to help out without diagnostic information. In your edit I believe you answered what may be the problem. I am using Cava's questing profiles with my Shaman, and it may be the InteractWith behavior you're talking about that's causing my shaman to run into melee range instead of casting ranged attacks. It's makes a lot of sense. I'm going to be leveling my shaman some more today, so I'll put up a log in a little while once I get it up and going for a bit. Thank you again for trying to assist me, even though I failed to meet the assistance requirements.
unclejesse999, Thanks for taking the time to post. Unfortunately the log file attache is for your:
For your Hunter, please click Class Config and set the Debug Logging option to true, then run your Hunter as you did before and post the log created in that session. It will "extremely" helpful if you can look at the local computer time when you notice the problem occurring and include that with your post. If you have any questions about how to do that or what info is needed, just take a look at the Reporting Bugs [CLICK HERE] post which will walk you through it. Thanks again for posting and good luck with your Hunter, Bobby53
jacks, Thanks for your post. Typically I will need you to provide the information present in the Reporting Bugs [CLICK HERE] post to be able to research a problem for you. In this case, it is because support for cleansing is currently in the process of being restored. Look for it in the next major release of Singular (saying major only because there may be a quick bug fix posted this weekend, but the support for what you requested won't be present for a few days later.) Thanks for your post and good luck with your Druid, Bobby53
Zeldrak, Thanks for your help. I am always glad to see a post with your name on it because even in this case your description was so spot on I could associate the behavior with research I had done for another users full bug post. I know you are aware, so am writing this for other readers benefits. Normally I couldn't reply with anything meaningful to a problem report about Pull behavior and its relationship to Pull Distance without the detail needed. Including a log file is not an arbitrary requirement I made up to discourage people from posting. It's the information I need to be able to focus my efforts on understanding what went wrong for you and to have the best chance possible of improving your experience. In fact, the only reason I was able to pontificate on what might be going on for Zeldrak was because someone had posted a couple weeks ago on this very same issue with a low-level caster using Cava's profiles. At any rate, I appreciate all members taking the time to post, but I can only act on posts that contain the details necessary to duplicate the issue as it occurred for them. Thanks again to all that post regarding their Singular experience, since that is the primary means of ensuring it meets your needs! -Bobby53
I understand bobby, and thanks for understanding me. I've been with this community long enough to know that the log files (unedited, full, complete logs) are necessary diagnostic tools that aid in the troubleshooting process. Sometimes I find myself in a rush to post something, and I forget to add the additional information needed to fix my problem.
Not spending a lot of time on this one but a few quick points while I work on your forum ban:
artimithe, It is and thank you for posting. Just haven't had a chance to get to it yet but will shortly, -Bobby53
(in support terms you could say i found a workaround not a sollution)
ugly72, Welcome to the HonorBuddy Community and thank you for taking the time to post. Please see the Reporting Bugs [CLICK HERE] for details on the information to provide regarding any issues you experience. In this case, please provide a specific time for a specific instance of a problem with your Elemental Shaman along with the complete debug log file. Thanks again for the post and good luck with your DB Group, Bobby53
DrSalvation, Welcome to the HonorBuddy Community and thank you for taking the time to post. Please see the Reporting Bugs [CLICK HERE] for details on the information to provide regarding any issues you experience. The description you provided does not match the results I am getting during testing. Thanks again for the post and good luck with your Warrior, Bobb
Perseisam, Thanks for taking the time to post. I looked quickly and did see the issue in the Fury code causing the behavior you indicated. Fix in the next release. Please see the Reporting Bugs [CLICK HERE] for details on the information to provide regarding any issues you experience. It is a rare occurrence that I can identify an issue without a log file. HonorBuddy with Singular is a complex environment with multiple versions of each component, variance in character setup, settings, combat scenario, operating environment, botbase, plugins, profile, etc. Thanks again and good luck with your Fury Warrior, Bobby53Hello! I changed the settings on the warrior commanding shout, but the bot all the time uses a battle shout, ignoring changes in the settings.I use a Fury Warrior.