View Full Version : WoW Macros for power leveling characters (dual)
Jared_Nye
05-16-2007, 06:49 PM
I have a few 60s that I'd like to level up to 70. Luckily I already have a Druid at 70.
I'm thinking that if I group up the characters, the Druid will suck up some of the XP. So instead of grouping, I'd just have the Druid hang back and heal as needed. For example, say I've got a 70 Druid and a 60 Warrior.
I'd use some macros like:
/target WarriorCharacterName
/cast Regrowth
Nothing fancy. However, if I want to switch to another level 60 character, I need to go back edit the macro to
/target RogueCharacterName
/cast Regrowth
Since I'm not in a party, I can't use Party1 or Party1Target or the others. I'd hate to have a macro set for each character.
Would something like this work?
/target WarriorCharacterName or RogueCharacterName or PalyCharacterName
/cast Regrowth
:oops: I'm just not familiar with the syntax :oops:
Gallo
05-17-2007, 12:13 AM
I'm not sure if you can use "or" statements. Just make 3 seperate macros.
Also, I suggest making a
/assist WarriorCharacter
/cast Moonfire
or /cast Wrath Macro.
Even though they're out of group, if you wait until the mob is below 80% health and have the druid do some damage, the mob will go down faster and the warrior will get 100% xp.
Otlecs
05-17-2007, 02:28 AM
The only way I know of doing this is with separate macros for each. Or make sure all your new characters start with the same few letters and just /target that prefix ;)
ytrehod
05-17-2007, 12:31 PM
I'd think it'd be easiest and require less editing if you used [target:focus] in your macros. Then all you need to do is set your levelling character as your Druid's focus; just target the character and type "/focus target"
For example: "/cast [target:focus] Regrowth"
And if you want to set something up for assisting you can use "/cast [target:focustarget] Moonfire"
Yarddog
05-18-2007, 05:26 PM
Using Focus is probably your best bet for the easiest way.
Another method (the one I use) is to create some LUA code that adjusts your support character's macros to use your main character's name.
I need to create some LUA that changes state based on which character is alive. Sort of a jump list of names so that is X is alive then macros should refer to X but if X is dead then go to Y. If Y is dead then so on ans so forth.
Why would you need to use LUA to use your main characters name? Can you not just /assist Main and then /cast?
Is there less latency involved with the LUA code? Sometimes I need to spam /assist multiple times to make sure it gets the /assist off.
That might be a better way to do things.
Yarddog
05-21-2007, 11:28 AM
The LUA code I've written that I'm referring to is just something I execute ONCE at the beginning of a playing session to change some macros of my support characters to tell them who the main character is.
I'm often running the same support group (level 70 mage and priest) with a number of different lowbies on the main account and don't want the lowbie in the party since that would gimp his XP. So the LUA code just changes the support group's macros to refer to the main character by his name instead of a standard UnitID like "party1".
Otherwise I would have to manually go through a bunch of macros and change the name many times. The LUA code does it for me.
Latency is not an issue since this is not something called with every keystroke but just run once at the beginning of a playing session.
If there is a generic way of referring to another character that IS NOT in your party I wouldn't have to do this, but I don't know of any.
Can you not just /assist Xzin? or /target Xzin?
It does not work as well as I would like sometimes - sometimes it lags - but it is workable for most macros.
Gallo
05-22-2007, 07:14 AM
Xzin, you mentioned something about wanting to get some macros to switch targets based on who is alive or not... do you have problems when your main character dies? Right now I've been only 2 boxing, but my major problem is that I get so disoriented when my main character dies, that it's almost inevitable that the secondary is going to die. I can't imagine the mayhem with 5 characters heh :)
I guess that my macros and such aren't well setup.
Yarddog
05-22-2007, 10:05 AM
Xzin, yes, that's exactly what I do. I set /assist and /target to the name of the main character. Sorry I didn't explain it very well.
If I only had a macro or two to change it wouldn't be a big deal. But I have a dozen or so for each of the two support characters, most which need to be changed. So the LUA code does it automatically based on which main character I'm running around with.
Yarddog
05-22-2007, 10:19 AM
Gallo. I often play a warrior, mage and priest. If the warrior goes down its generally over for the mage and priest too, LOL.
Sometimes the mage can finish a fight or the priest can get away to rez, but too often they just go down fast after the tank is gone.
Xzin, you mentioned something about wanting to get some macros to switch targets based on who is alive or not... do you have problems when your main character dies? Right now I've been only 2 boxing, but my major problem is that I get so disoriented when my main character dies, that it's almost inevitable that the secondary is going to die. I can't imagine the mayhem with 5 characters heh :)
I guess that my macros and such aren't well setup.
Well, I updated my setup to include individual macros to handle changing viewpoints. Of course, I have separate screens and everything else..... I can also change /follows on the fly... if I REALLY need to, I *think* I can setup a simple 4 button macro to change my macros on the fly but I don't know if I will need to go that route.
Usually when Xzin dies, I am out of mana on all of the Zins and totally screwed anyway - so honestly in most BG situations it is easier to just die and rez with full mana and health.
Not sure about the warlocks though... hence the new macros and new setup to better allow for switching between the Zins.
If nothing else, have some macros set aside and ways to change /follow if you multibox.
vBulletin® v4.2.2, Copyright ©2000-2025, Jelsoft Enterprises Ltd.