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!
Darknight1, Thanks for the post! The description doesn't match the results of my testing however, so as with all problems/questions you will need to follow the steps in Reporting Bugs [CLICK HERE] so I have the details necessary to troubleshoot for you. Before running, be sure to do the following:
Chardril, Welcome to HonorBuddy! When posting a question or issue, you will always want to follow the steps in Reporting Bugs [CLICK HERE] so the information to research and reply to your issue is available. In this case another member had reported the issue and a fix is already pending in the next release. In the mean time you can prevent Ascendance from being cast by not targeting the Boss until you are within range. Thanks for the post and good luck with your Shaman, Bobby53
Ilja, Thanks for the log file! When you encounter an issue, I also need to know a specific moment where it should have healed in your opinion but didn't so I can focus on that. From what I can see, the Heal settings seem to mostly be set to 70%:
so if nobody drops below 70% there won't be any healing taking place. There were a few points in the log where it was casting heals on players whose health had dropped below this starting at: [20:43:04.206 N]. Also some where it cast heals on players out of combat (such as topping off the tank.) It looks like the updated default health %'s for Resto Druid didn't make it into the last release, so you will need to click Class Config / Group Healing tab and set the Health %'s appropriately for your botting context (in this case it was Instances.) Thanks for the post and look for improved defaults next release, Bobby53
the problem was, it didn't heal at all, except some rejuvenation, so the group wipes. going to set %s now and will try again
Ilja, Please be sure to do the following:ah ok, thanks for explanation
ok here is a log with logmark.
Ilja, Thanks for the post. Fixed in the next release, -Bobby53
Bobby53's Standard Request for More Information [CLICK HERE]
15outland, There is not a setting that turns Hex of adds on / off. In general I am not in favor of settings that have to be turned on or off and prefer the character automatically react to the combat scenario it is in appropriately. If you can post as described in Reporting Bugs [CLICK HERE] your situation and why you felt it wasn't appropriate to cast Hex on an add I will be happy to look at that and have it automatically avoiding casting Hex in that situation if appropriate or adding a setting to allow user control if necessary. Thanks for the post and good luck with your Shaman, Bobby53Anyone able to help me with Shaman Singular? I want it to stop hexing, but I have no clue how to go about that
// Andys Schield
behavs.AddBehavior(HealthToPriority(50) + PriHighBase, "Test @ " + "Power Word: Shield - Tank", "Power Word: Shield",
new Decorator(
req => ((WoWUnit)req).HealthPercent < 50 && !((WoWUnit)req).HasAura("Weakened Soul"),
new PrioritySelector(
Spell.Cast("Power Word: Shield",
mov => true,
on => (WoWUnit)on,
req => true,
cancel => false
)
)
)
);
// Ende Andys Schieldephantasie22, Thanks for the post! A change was already made in the next release for PW:S based upon your prior post similar to what you shared, but using a higher priority and providing a user setting for the health % it is cast at. The log was needed for PW:B. Unfortunately, the one attached doesn't have Debug Logging and Debug Spell.CanCast set to true so the info needed isn't present. However, in reviewing the code there is a bug in which setting is referenced which is preventing it from being cast. Look for a fix in the next release as well as a few other improvements to Disc Healing. Thanks for the post and good luck with your Priest, Bobby53
Sin702, Thanks for the post with log file. Something is definitely wrong based upon the repeated targeting failures appearing in the log. Unfortunately I can't tell from the log provided what is occurring as its not a debug log. For steps on creating a log that contains debug (diagnostic) information, please see the Reporting Bugs [CLICK HERE]post. I'll take a quick run with my Guardian and see if I encounter that issue, but if you receive this and don't see a follow up from me go ahead and generate a debug log of that scenario to be sure I'm resolving your issue. Thanks for the post and good luck with your Druid, Bobby53
[19:15:26.937 V] [Singular] TrivialHealth: 222763