The (Mostly) Complete Raiding Druid Package v7.23

A_Druid_00 · Post by **A_Druid_00** » Mon Jan 10, 2005 1:08 pm

If you'd like to throw together a plugin that will work with RD and make string parsing a little less time consuming, provide me with a demo of it's proper usage and syntax, and I'll do my best to integrate it anywhere it makes sense. There are already places where it could stand to be used in my macro right now.

The not going OOM thing I can't help obviously. I much prefer the cancelpct and healpct setup though. In all honestly, client updates are very close to, if not instant when it comes to target data, if you aren't cycling targets. As long as you have your heal recipient targetted, the HP updates are as close to instant as you can get. You have to count on the fact that there are other people out there spam healing when you duck a heal because the tank's at 100%. I suppose I could improve a bit on the heal cancelling logic, but it seems pretty sound as is.

Spam healing without prejudice, no matter how you look at it, isn't mana efficient. Puzzle over this: What if the unlikely event occurs that every healer in your raid was using this macro to spam heal the tank? My guess is that every one of them would get below the HP vs Mana condition you presented at very close to the same time, and the tank would end up exploding. While I would laugh my ass of if this ever occured, I don't think the raid leaders would find the humor in it.

OTOH, every class has different casting times, not counting different casting times within each class due to focus items, etc. So if every healer was cancelling at 95-99% and starting at 90ish, there would be a near constant stream of heals landing on the tank, and he'd only die if he manages to get 1 rounded, which no amount of spam healing can save.

But, now that you've gotten me thinking, I may have an equitable solution for both of us in regards to this. Instead of cancelling any time the tank goes over HealPct; I'll evaluate the castEndTime set within Spell_Routines, and only cancel if the recipient is over the cancelpct AND there's less than 1 second left on the castEndTime.

yendor · Post by **yendor** » Mon Jan 10, 2005 1:14 pm

A_Druid_00 · Post by **A_Druid_00** » Mon Jan 10, 2005 1:43 pm

I'll throw together a SpamHeal toggle sometime this week and see how it goes. I probably will never use it, so you'll have to let me know how it works. It'll cycle through your MA list and target the first one it finds and spam heal him. That way if MA1 dies, it will start spamming MA2, then MA3. I'll make a SpamTimer to handle timing too.

We spam heal the tanks on high DPS mobs too, but we still duck out if our heal's going to land on someone who's at 100%. The CancelPct change will make a big difference in my healing behavior as is.

Cr4zyb4rd · Post by **Cr4zyb4rd** » Mon Jan 10, 2005 1:58 pm

Nothing as you described it is going to be sped up by the addition of a plugin. The macro parsing here is fast enough. Adding another interface level isn't going to remove a bottleneck, only changing your logic will.

Limiting your mana output to the mob's HP is (to be blunt) stupid. If you could somehow guarentee that you have the highest remaining mana on your raid (you can't) I could maybe see some gross utility, but it'd wouldn't be much. Your MT exploding because you decided to be "efficient" at 68% mob health is going to cause a lot more deaths than a low-hp tank transition when the aggro table is as stable as it's likely to get, and the wiser of the high-dps/low-survivability people have already blown their discs and thrown their hammers at the mob.

yendor · Post by **yendor** » Mon Jan 10, 2005 2:24 pm

yendor · Post by **yendor** » Mon Jan 10, 2005 2:43 pm

yendor · Post by **yendor** » Mon Jan 10, 2005 3:40 pm

A_Druid_00 · Post by **A_Druid_00** » Mon Jan 10, 2005 6:14 pm

Yendor, wrong.

The array only stores the ID numbers of all the PCs in range. The server does not send you HP updates for every person in a zone. It only sends you the HP update when each PC gets targetted. Unlike my group checking sub, this sub actually NEEDS to target each person in the array, before it can make a decision whether or not to heal them. I toyed with the idea of machine gun targetting the entire raid, and then evaluating each person's HPs after the server sent the updates. But, that would look a little suspicious if someone were so inclined as to watch for it. As it is right now, the AE healing portion is pushing the envelope as to what I'd consider edgy. Even if you were to write a plugin that spoofed a server update for each array member, I'd have to say I'd be pretty hesitant to use it for the above reasons.

As it is right now, the only time the array could be considered out of date is when a person in it dies before I get to them, which is already accounted for.

Cr4zyb4rd · Post by **Cr4zyb4rd** » Mon Jan 10, 2005 6:33 pm

Sorry if I don't agree with you.

Grats.

But it would allow for a more complex set of healing rules on a raid, especially prioritizing them.

It won't "allow" for any such thing, insofar as nothing you've mentioned is verboten already by macros. The further elaborations and hand-waving on your part really aren't necessary. I'm sure we all know what prioritization is.

The aeheal routine now could be improved, it shouldn't be looping through pcs at the level it is.

At the level it is? o.O

If this isn't done I will be oom when the mob is half dead and have nothing left when defensive goes down or if there is a tank switch or an add suddenly comes in and I have to heal someone else.

Thanks for the expatiation, but I'm not the one demonstrating a lack of understanding of both game mechanics and resource maximization.

This macro isn't replacing me being at the controls on a difficult raid, its just automating some of it if i slack off.

I bet. Given that, why not press the "D" key when it's casting something you don't want it to cast?

I will be nailing the MA at the appropriate times.

Be sure to give him a reach-around.

When things settle i just sit back and let the macro take over and have it do so with some concern of mana expenditure.

So use settings appropriate to the situation, as the author of the macro advocates?

Play the way you want, but please don't call me stupid.

I didn't, I called a course of action that you were endorsing stupid. Your failure to discriminate between the two, however, isn't exactly indicative of great wit.

yendor · Post by **yendor** » Mon Jan 10, 2005 7:21 pm

a_druid,

I see, didnt realize the HP was only sent on targeting, its been a while since I looked a these. In which case I guess there isn't much to be gained. Still. Instead of/in addition to ae a watch list might be a nice addition. Cycle through a small list (half dozen) of people you want to watch outside your group.

bard,

whatever.

A_Druid_00 · Post by **A_Druid_00** » Thu Jan 13, 2005 4:23 pm

Any other suggestions as to what you guys want to see in RD next? I've added everything I could have possibly wanted, and I'm out of ideas. Maybe it's time to add my max crit heal and crit nuke after all!

Rondle · Post by **Rondle** » Thu Jan 13, 2005 7:40 pm

a simple command to change from fire to ice nukes would be nice. atm you have to edit the INI to do so. (either that or I suck at reading documentation.)

maybe even ini-based lists of which nuke to use on which mob? set by preference? IE: if I am fighting ptav m'sha, and manually use a cold nuke, in the future it will automagically use cold nukes on ptav -- even if I have it set to use fire in general.

I don't really know enough about coding to know if that is possible, though.

A_Druid_00 · Post by **A_Druid_00** » Thu Jan 13, 2005 7:49 pm

A mob list for which nuke to use where would be a nightmare. Have you seen the ini? Do you really want to make it even bigger?

You do suck at reading the doc though. /fire and /cold switches to fire and cold nukes respectively, and also updates the ini. There's also instructions in the doc on how to configure a keybind to toggle fire and ice nukes with a simple keystroke.

TheNewGuy · Post by **TheNewGuy** » Thu Jan 13, 2005 8:22 pm

Dude this thing is fucking schweet. Thanks A_Druid_00!

Now, for a question. I don't want the code to be put here, unless you do it yourself - but can you just tell me if this logic is correct, and would approximately be how I would accomplish it?

I am wanting the druid to return to the spot he was standing before he goes off and ninjaloots. So...

Code: Select all

EXP message comes in
Macro checks to see if it should loot - Option is turned on, so it continues
Place current X in a variable (MyCurrentX)
Place current Y in a variable (MyCurrentY)
Loot the bugger
Return to (MyCurrentX),(MyCurrentY)

I think that's how it would need to be done, right?

I ask becuase I use this as an almost AFk macro when duoing with my necro. 100% satisfied with the current setup except this, and as I said before I don't really want you to have to code it - I'd rather figure out how myself... Just wondering on the logic is all...

Thanks for the awesome mac again!

A_Druid_00 · Post by **A_Druid_00** » Thu Jan 13, 2005 8:26 pm

Essentially yes.

Now that you mention it, I think I'll probably use the new /moveto command in moveutils to do exactly that