Post
by fantum409 » Sat Jul 03, 2004 12:22 pm
It would be possible to make a "watchdog" approach to timing the heals, but it isn't my goal with this macro to do that, mainly because I suspect there will be more tendency to kill tanks. I would rather chance wasting mana and healing a little early than chance the macro waiting longer to initiate a cast, and then have an add kill the tank. The macro would need more supervision using the "watchdog" approach, I think.
The present logic addresses it a little bit in the tankwatch part, because if the tank drops below ${Math.Calc[${healpoint}*0.7]} it will patch heal instead of CH. Or similar syntax... What was intended there was to say if the tank drops in HP so fast that you couldn't initiate CH on time, use a faster heal. Perhaps if I added a check of tank HP during the CH cast, in my CheckHP sub, such that if I'm casting CH and it has more then 5 secs to go and TankHP is less than a given percentage, interrupt cast and cast patchheal instead.
Will think it over, as several variables are involved and CheckHP needs to be kept small and efficient. (if you think of a better way to code it, feel free to post it or /msg me, I like to take hints whenever I can get them)
And yes, DumbStruck, please fill in the details as much as you can, and I'll try to ferret out the problem. Did the cleric spam the group with alternating messages about healing one tank then the other? Did it initiate casting then interrupt and switch, did it just alternate targets and never initiate casting? Did you change any of the parameters in the beginning of the macro? What were the Tank HP percentages when it was doing that?
The more specific you can be, the easier it is for me to find my error. And if at any point you saw errors in the MQ2 chat window, please take note of those as well.
I don't have 2 tank-types to group with to troubleshoot that, but will be interested to follow up on that problem you describe.
Thanks for the feedback guys.