Help with Pet Attack Control
Quote:
Originally Posted by 'Vyndree',index.php?page=Thread&postID=81219#post8 1219
If you want pets to be going to different targets I find that having a /focus button for each character and then doing a simple /petattack [target=focus,harm,nodead] (you can even put that at the top of my macros above) works brilliantly. Setting up the focus'es can take prep time, or you can integrate it into your dps buttons...
Okay, so I have a /focus button set up for each of my warlocks (4 distinct buttons on the action bar for each of my locks). After setting the focus for each mob I want the lock's pet to attack, I then issue a global button for all locks that sends their pets off to the assigned focus:
Code:
/pet attack [target=focus,harm,nodead]/stopmacro [target=focus,harm,nodead]
This works well. Each of the warlock's voids go after the focus I've assigned. Brilliant. However, the issue I am running into is that when the pet is finished with the mob they have been assigned (due to the fact that my locks have obliterated it), they run back with nothing to do. How can I create a sequence that will allow them to pick up the next mob that is still alive and the target of one of the other lock's pets?
It would be really nice if I could make a global pet attack macro that would initiate with the assigned focus then once done move on to the next available. I'm thinking of something like:
Code:
/pet attack [target=focus,harm,nodead]
/stopmacro [target=focus,harm,nodead]
/pet attack [target=PETNAME1target,harm,nodead]
/stopmacro [target=PETNAME1target,harm,nodead]
/pet attack [target=PETNAME2target,harm,nodead]
/stopmacro [target=PETNAME2target,harm,nodead]
/pet attack [target=PETNAME3target,harm,nodead]
/stopmacro [target=PETNAME3target,harm,nodead]
/pet attack [target=PETNAME4target,harm,nodead]
/stopmacro [target=PETNAME4target,harm,nodead]
I assume this would work they way I want it to. Basically, the lock's pet that is free'd up would pick up the next target thats alive that another lock's pet is current engaged with. However, I can't test this due to macro space .. is this even correct? (If so, how do I shorten to get around macro size contraints?) If not, Is there a better way?
Thanks!!