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!
Shock18, Please visit the ShamWOW Frequently Asked Questions [CLICK HERE] for steps on providing the information I need for any question or issue you would like me to look into on your behalf. Good luck with your Shaman, Bobby53
reddewman, I looked at the first few Call of the Element calls in log file you mentioned and saw it being cast two times. The appearance is that the client or HB hasn't updated the list of objects showing the totems as being present, so when it checks after casting the first time and doesn't seem them it casts again. I'll look to incorporate a "hack" that will assume for some duration after a totem cast that it was successful and the totem exists which will prevent a successive recast. This should cover any lag occurring. I won't be able to get to this for several days though.
IvanRJ, Thanks for the post. The important part of the ShamWOW Frequently Asked Questions [CLICK HERE] in this case is:
MrWizard, Thanks for the post and for zipping the log file. That is exactly the handling requested in the FAQ. I checked and the log file only spans time until 12:13pm so I am not able to look at the specific instance you mentioned. I did scan through a number of the *Lava Burst casts in the file and didn't see a point where it stopped casting. If it did stop casting in your encounter, it wasn't to melee but was due to something else. Melee attacks are enable immediately upon engaging a target so for all specs so it doesn't need to check later should it enter a situation where all other attacks are unavailable. The messages are benign and should be ignored. However, if you stopped casting and weren't silenced, out of range, out of line of sight, out of mana, or targeting a nature immune mob then something else is occurring and I'd need that log file to look into. Thanks for the post and good luck with your Shaman, Bobby53
The Flame Shock DoT was already on the target and Lava Burst was on CD. All other attacks in the base rotation are Nature damage, so being detected as immune to Nature prevented it from casting anything else. I'll add a call to Frost Shock and Unleash Elements as a fallback which will only occur if you encounter the same situation.
Hi Techz, Thanks for the post but I can't do anything with posts that don't have the content/info specified in the FAQ. I'll keep an eye out for your update. Good luck with your Shaman, Bobby53
Selective healing support is already available by choosing one of the categories above. I will add individual selection to the list of possible changes for future releases.
No option for a user to disable is available. You should simply ignore the message. Alternatively, see the ShamWOW Frequently Asked Questions and make a detailed as described. Be sure to specific in addition to the details how seeing the message was negatively impacting your use of ShamWOW.
soussi, Please see the ShamWOW Frequently Asked Questions [CLICK HERE] for steps on posting the information needed for any question/issue you would like me to research on your behalf. If someone from an enemy faction is in range, attackable, in combat, and targeting you it will attack. So an enemy faction player that is in mid-fight with someone/something else and targets you will be attacked. Good luck with your Shaman, Bobby53While questing a pvp duud passed by and my toon started attacking it. Is there something in the options i need to check so it doesnt happen ? or? thx in advance
