View Full Version : The No Focus Manifesto v0.1
Zzyzxx71
06-06-2008, 10:26 AM
The No Focus Manifesto!!!
Disclaimer: I’m in no way attempting to take credit for the idea of non-focus failover. There are greater minds that have come before me and put this together. I’m attempting to consolidate some of these ideas and document how I believe I’ve successfully put them into use with using no focus in my gameplay to this point. Enjoy!
What we’re trying to accomplish here is:
1 Button follow with leadership failover built in
1 Button synchronous firing recognizing leadership failover
No use of focus (It can be used later for something even more fun!)
The Standard Stuff:
On your main:
A "group invite" macro:
/invite toon1name
/invite toon2name
/invite toon3name
/invite toon4name
/ffa
Click this twice – first time to invite, accept invites, and then again to set loot to Free For All
How to you accept on the remainder of your toons?
/script AcceptGroup();
/script AcceptQuest();
/script AcceptTrade();
/script RetrieveCorpse();
/script RepopMe();
/script AcceptBattlefieldPort(1, 1)
DISCLAIMER: From experience, I do NOT use /script RetrieveCorpse(); and /script RepopMe(); on my slaves (shamans) – main reason is AV. Should you lose possession of an asset during the fight, you’ll end up with your guys rezzed up all over the place.
This macro will accept the invite, it will also accept sharing quests, accept rezzes, accept releasing, accept trades, and accept battleground notifications.
The MONSTER macro (AKA The Big Button):
The first thing we’re going to need is a follow macro. We’re going to toss a lot of utility in this follow macro. It may not look like much but this is the main macro for making all this work.
/target [target=Brain, nodead, help, exists]; [target=Toon2, nodead, help, exists]; [target=Toon3, nodead, help, exists]; [target=Toon4, nodead, help, exists]; [target=Brain, exists]
/follow
Translated?
/target [target=Main guy if he's alive]; [target=#2 if he's alive]; [target=#3 if he's alive]; [target=#4 if he's alive]; [target=Main guy - YOUR ALL DEAD]
/follow
This does the following.
Follows your main guy, handles your failover to a non dead toon when your main dies (all you need to do is click on the next alive toons window, click whatever button you have assigned to follow, and the macro does the rest). It also will permit follow BACK to your main guy if you’re entire team is dead. Why isn’t the 5th guy listed in there? Because if the first 4 are dead – What’s the point in targeting yourself?
Casting Macros:
You’re going to need to dmg stuff eventually – lets get down to how to do that without using focus.
/cast [target=targettarget, harm] [] Lightning Bolt
Remember that all your slaves have YOU targeted. What this does is “if your targets target is harmful, cast this spell on it” – it does NOT untarget your leader. You should be able to go through entire instances having your slaves never targeting a mob.
If in the unlikely and unfortunate event your main dies, the [] modifier will permit the REMAINDER of the slaves to single target if necessary. Since there are no specified names involved, this is perfect for failover.
Healing:
Same setup as above, change 1 aspect:
/cast [target=targettarget, help] [] Lesser Healing Wave
[] permits your brain to single target, again facilitating failover.
In Summary
The functionality of these 4 macros with a little modification (add one for earth shock, frost shock, chain lightning) and you have:
1. Group invite
2. Accept
3. Follow
4. Assist and Pew Pew
Lets explore the following scenario:
Your Brain dies – “OH NO NOT THE BRAIN!!!” – You take control of slave #1, You click your follow macr, Slaves #2,3,4 target Slave #1 based on the way the big button macro is setup.
You start to pew pew with slave #1. Based on the way the casting macros are setup – he is allowed to free fire. The rest of the slaves, targeting slave #1, fire on slave #1’s target (targettarget) without UNTARGETING slave #1.
This might seem like a laborious process, but it’s rather fast.
Brain dies
Take control of slave #X
Press your follow macro
Continue killing.
2 actions and your failover is complete.
Extras:
Heal+PewPew in 1!!
/cast [harm] [target=targettarget, harm] Lightning Bolt; [target=targettarget, help] [] Lesser Healing Wave
This is a great 2 in 1 macro – if your brain (whoever your brain may be) has a player targeted, they all heal the player – if the brain has no one targeted, they heal the brain – if they have an enemy targeted, pew pew pew
Fast Rezzing!!
Well gee darn – you wiped. The scenario is that the T5 tank or healer you brought along would really appreciate it if you rezzed him/her first. But wouldn’t it also be nice to be able to just bang a button and autorez your guys without fumbling through the pile of corpses?
We need to have A: the ability to target and rez, and B: the ability to autotarget your team members and rez.
/target [dead] [target=Team1, dead]; [target=Team2, dead]; [target=Team3, dead]; [target=Team4, dead]; [target=Team5, dead]
/cast Ancestral Spirit
Yay!! Lazy Mans Rez Macro!
Drizzit
06-06-2008, 10:50 AM
The MONSTER macro (AKA The Big Button):
The first thing we’re going to need is a follow macro. We’re going to toss a lot of utility in this follow macro. It may not look like much but this is the main macro for making all this work.
/target [target=Brain, nodead]; [target=Toontwo, nodead]; [target=ToonThree, nodead]; [target=ToonFour, nodead]; [target=Brain]
/follow
Translated?
/target [target=Main guy if he's alive]; [target=#2 if he's alive]; [target=#3 if he's alive]; [target=#4 if he's alive]; [target=Main guy - YOUR ALL DEAD]
/follow
This does the following.
Follows your main guy, handles your failover to a non dead toon when your main dies (all you need to do is click on the next alive toons window, click whatever button you have assigned to follow, and the macro does the rest). It also will permit follow BACK to your main guy if you’re entire team is dead. Why isn’t the 5th guy listed in there? Because if the first 4 are dead – What’s the point in targeting yourself?Might want to do an "exists" there too:
/target [target=Brain, nodead, exists]; [target=Toontwo, nodead, exists]; [target=ToonThree, nodead, exists]; [target=ToonFour, nodead, exists]; [target=Brain, exists]
/follow
This way if you log on with only 3 instead of 4 you will not have a problem. I use my pally tank for my 2 team and they all have the same follow command (i use focus but same end idea). Without the exists it stops at that statement. So if toon Brain, three, and four are the ones you play with, if Brain dies, the follow command will not work because two is not there and that macro then throws up an error.
Zzyzxx71
06-06-2008, 11:16 AM
that's a good idea for those teams what aren't the typical 5 x shammy teams. Gonna add that later.
Might want to do an "exists" there too:
/target [target=Brain, nodead, exists]; [target=Toontwo, nodead, exists]; [target=ToonThree, nodead, exists]; [target=ToonFour, nodead, exists]; [target=Brain, exists]
/followAnd a "help", for when your current main gets mind controlled. Also, you might want to create a second follow macro that has a reverse target order in case your current main gets polymorphed or otherwise crowd controlled.
(Btw, I thought 'nodead' already implied 'exists'?)
Desible
06-06-2008, 01:06 PM
Sweet! Thanks for putting this all in one thread. I've made the switch to No Focus macros and love it, so it's always great to have a definite place I can look for new macros.
Drizzit
06-06-2008, 01:24 PM
Sweet! Thanks for putting this all in one thread. I've made the switch to No Focus macros and love it, so it's always great to have a definite place I can look for new macros.
The down side to this is if you are a tabber, as soon as your main tabs to switch targets your alts might be on different targets so you will have to hit the button to target your main again before you fire. This is one of the reasons i am using focus... at least for now.
Morganti
06-06-2008, 02:40 PM
I like the ideas behind this. What are your latency problems using target=targettarget? I know assisting focus sometimes has latency issues, sometimes not. I would assume targettarget has the same issues as assist. I actually have a lot of my pew pew macros that will /assist focus 3 times before i even cast...hehe. I'm happy with my shamans and priests using focus, but I can see a PVE group with mages (or even priests) wanting to hold focus for sheeps and shackles.
Trama
06-06-2008, 03:52 PM
Extras:
Heal+PewPew in 1!!
/cast [harm] [target=targettarget, harm] Lightning Bolt; [target=targettarget, help] [] Lesser Healing Wave
This is a great 2 in 1 macro – if your brain (whoever your brain may be) has a player targeted, they all heal the player – if the brain has no one targeted, they heal the brain – if they have an enemy targeted, pew pew pew
OK, I understand how this works, but I would like to find a way to throw a few heals around while continuing to dps. For example, my "Brain" has agro and is taking damage, I don't want every slave to heal him, just 2 of the three slaves (4 shaman team). I want the 3rd slave to continue dpsing. The only way I can see to do it, is to have a separate macro for this scenario on each slave. Using targettarget to dps and target (since they have him targeted already) to heal. Hmmm..maybe with a modifier? But then all slaves would do the same thing anyway, right? Either all dps or all heal.
Desible
06-07-2008, 01:20 PM
Just cut off the healing part of the macro for Slave 3. Slave 3 will never be able to heal but he won't ever stop DPS'ing either. OR add a modifier to Slave 3's macro for the OH S!%* times that he really does need to heal.
MoonD0G
06-08-2008, 01:32 AM
man, i love what you've done here! this is exactly what i was looking for. i was getting pretty frustrated w/ all the macros i was finding, if ur main dies they will all target ur secondary toons target but when i would switch to my secondary toon and tried to attack something it would automatically reselect itself as a target making it difficult to attack anything on that toon.
@KvdM
when u say add a help in there how exactly should it be done? can u just make it like this:
/target [help] [target=Party1, nodead, exists]; [target=Party2, nodead, exists]; [target=Party3, nodead, exists]; [target=Party4, nodead, exists]; [target=Brain, exists]
/follow
or does it need to have "help" in each set:
/target [target=Party1, nodead, help, exists]; [target=Party2, nodead, help, exists]; [target=Party3, nodead, help, exists]; [target=Party4, nodead, help, exists]; [target=Brain, exists]
/follow
hell for that matter could u just throw the "exists" part in the begining part of it too? or do those need to be in each section?
example:
/target [help, exists] [target=Party1, nodead]; [target=Party2, nodead]; [target=Party3, nodead]; [target=Party4, nodead]; [target=Brain]
/follow
just curious to save space for other possible macros if anyone knows.
Anyways, nice job man glad i checked it out
Zzyzxx71
06-08-2008, 11:30 AM
/target [target=Party1, nodead, help, exists]; [target=Party2, nodead, help, exists]; [target=Party3, nodead, help, exists]; [target=Party4, nodead, help, exists]; [target=Brain, exists]
/follow
is what he's referring to. I'm gonna impliment this in my setup once I get off my fatass and do it.. I"ve actually had the 3 slaves KILL the main before because he's now [harm]
Zzyzxx71
06-08-2008, 11:34 AM
Sweet! Thanks for putting this all in one thread. I've made the switch to No Focus macros and love it, so it's always great to have a definite place I can look for new macros.
The down side to this is if you are a tabber, as soon as your main tabs to switch targets your alts might be on different targets so you will have to hit the button to target your main again before you fire. This is one of the reasons i am using focus... at least for now.
False. Hitting the big button isn't a requirement to change targets. Remember - if using this method, your slaves don't have a mob targetted, they have the BRAIN targetted, and are using [target=targettarget]. They do NOT target mobs.
ThatIrishGuy
06-08-2008, 02:41 PM
on my multi class team, i have buffs, but i cant figure out a better way to do them
/target toon
/cast buff
i could use the targettarget, but well my brain has to click each toon ( have it set up to do so to buff passers by, for OMGBUFFS) but id like it to be more efifcient
Desible
06-08-2008, 03:57 PM
on my multi class team, i have buffs, but i cant figure out a better way to do them
/target toon
/cast buff
i could use the targettarget, but well my brain has to click each toon ( have it set up to do so to buff passers by, for OMGBUFFS) but id like it to be more efifcient
Smartbuff ('http://wow.curse.com/downloads/details/2071/'). When I first started I was using macros to buff everyone and it did require time, and wasn't very efficient. SmartBuff allows you just push (spam) one button and all the buffs you want will be thrown out.
Occam's Razor
06-08-2008, 08:05 PM
/target [target=Party1, nodead, help, exists]; [target=Party2, nodead, help, exists]; [target=Party3, nodead, help, exists]; [target=Party4, nodead, help, exists]; [target=Brain, exists]
/follow
is what he's referring to. I'm gonna impliment this in my setup once I get off my fatass and do it.. I"ve actually had the 3 slaves KILL the main before because he's now [harm]AH-HA!!! That's what was making my slave mage cast Arcane Missiles on my main and then start meleeing my main
The only problem that I'm running into so far is with the "reset=target" function for my castsequence macros. How do you get around that, or what do you use in it's place?
Zzyzxx71
06-09-2008, 01:26 PM
Does reset=targettaret not work? I haven't tried castsequences with this setup yet.
Trama
06-09-2008, 01:35 PM
Thanks for these macro's, it has changed my world, seriously.
The only issue that I am encountering is having to retarget the "Brain" when I skin with one of my slaves. I think I can macro skinning though, using a macro like this:
/cast [target=targettarget, dead] Skinning
That way he won't change targets, right?
Thanks for these macro's, it has changed my world, seriously.
The only issue that I am encountering is having to retarget the "Brain" when I skin with one of my slaves. I think I can macro skinning though, using a macro like this:
/cast [target=targettarget, dead] Skinning
That way he won't change targets, right?
Yes, that will work. That's what I use.
Littleburst
06-10-2008, 05:35 PM
I used this aswell from the start. I got a lot of start up help from my GM who's multiboxing aswell.The only problem is that if i sheep a target on my main and switch to an other mob to fast my clones attack the sheep. But further i love it. I can just switch to one of my 2 clones, let the other 2 follow him and just use the macro's, it doesn't matter.
So if i'm PVPing and Imbest(main) dies, i just alt tab to imbetter and continue fighting, since imgood copies imbetter now.
nogbog
06-10-2008, 07:20 PM
What about petattack?
I've been using /petattack [target=focustarget]
Edit: i'm just using /petattack [target=main-target, nodead, harm] []
kind screwed if he dies though
nogbog
06-11-2008, 08:09 AM
I've gave your no-focus macros a go
While questing its fine, but in instances where i'm chain killing mobs, its gets a little sketchy.
What happens is that for whatever reason, sometimes my slaves targets will change from the main, to the target, i couldn't work out why. Its not all the time, its just some of the time when i'm spamming my pew pew button, which is:
/cast [target=targettarget, harm] [] Shadow Bolt
Zzyzxx71
06-11-2008, 08:44 AM
Do you have TAB on do not pass? I had that happen for a while until I realized I had 1 clone that was selecting via tab/
nogbog
06-11-2008, 08:53 AM
Yeh i do have it on do not pass.
It happens even on just single targets, whats the possibility of it breaking down cuz i whack the button too much too fast?
Zzyzxx71
06-11-2008, 08:58 AM
doesn't happen to me and I mash the living hell out of LB/FS/CL, etc... now it DOES happen (on purpose) for when I have to melee something - do you have any lines that would initiate melee combat?
Trama
06-12-2008, 01:37 PM
Thanks for these macro's, it has changed my world, seriously.
The only issue that I am encountering is having to retarget the "Brain" when I skin with one of my slaves. I think I can macro skinning though, using a macro like this:
/cast [target=targettarget, dead] Skinning
That way he won't change targets, right?
Yes, that will work. That's what I use.Perhaps I am doing something wrong with my skinning macro, I can skin my main target with no problems, but when the skinner loots what he skins (auto loot turned on), he still loses his target.
I like these macros a lot, but I find that I am constantly resetting alts targets back to the main (skinning, quest item looting, mining, herbing, etc.) I think that I may cut over to /focus macros so I don't have to do quite as much target management. Anyone else have this issue?
Zzyzxx71
06-12-2008, 01:48 PM
If you're using the /follow macro listed at the beginning, regaining follow/target on your main shouldn't be an issue - then again I may not have a grasp on exactly what the problem is.
Trama
06-12-2008, 02:10 PM
I am using the follow macro at the beginning for sure. But the issue is I have to keep pressing it after almost every kill. The alts change targets when looting and skinning. I am in the Barrens still and so I am skinning after almost every kill, not to mention grinding through the collect quests.
Its not a huge deal, but I essentially have to retarget the "Brain" on one of them after each kill. The use of a /focus macro would fix this perhaps. If I set the focus on all alts to the "Brain" their target doesn't matter when dpsing and such, correct? So I could loot and skin and save myself a key press with each mob.
nogbog
06-13-2008, 02:06 AM
I've gave your no-focus macros a go
While questing its fine, but in instances where i'm chain killing mobs, its gets a little sketchy.
What happens is that for whatever reason, sometimes my slaves targets will change from the main, to the target, i couldn't work out why. Its not all the time, its just some of the time when i'm spamming my pew pew button, which is:
Found out the problem, /petattack, the petattacks the nearest target if i don't have something targeted and then that becomes my target.. if that makes sense.
Targets before petattack
Main: nothing
Slaves: main
Targets after petattack
Main: nearest mob
Slaves: nearest mob
It's actually really annoying, 1 because my pets are attacking something i didn't want to (even though i did press petattack) and 2 because all my no-focus macros break down when my main isnt' selected.
Negative1
06-13-2008, 05:22 AM
There is one thing that I don't find I understand is the point to not using the focus. Stay with me now i understand that the point is to use focus for CC and the like but let me try to explain how i see targeting:
In wow as multiboxers we basically have two target "slots" per character. Focus target and current target each of which with proper macros can function exactly like the other:
/cast [target=focustarget]
/cast [target=targettarget]
Thus if you have these two slots that work about the same lets consider the subtle differences... the big one is that focus remains more constant and can only be cleared with /clearfocus or by setting a new focus, thus none of the problems with accidentally tab targeting or losing target cause of looting or skinning or anything else that may cause your current target to be lost.
Now as for CC when using focus to designate main. You still have your other target "slot" which in this case is current target.
So when using focus:
button1: /cast [target=focustarget, harm] pewpew spell
button2: /cast polymorph
the dps spell lands on your mains target and the polymorph lands on your current target which can be aquired through an assist button prior to combat or during combat. If you have multiple characters that can CC, the use of round robin on your assist button will allow you to set different CC targets.
The reason I find this to be the better solution is because the CC targets are less permanent than you main...Therefore you should use the more permanent target "slot" (focus) to designate your main and the more volatile target "slot" (current target) to designate CC.
Zzyzxx71
06-13-2008, 03:28 PM
I am using the follow macro at the beginning for sure. But the issue is I have to keep pressing it after almost every kill. The alts change targets when looting and skinning. I am in the Barrens still and so I am skinning after almost every kill, not to mention grinding through the collect quests.
Its not a huge deal, but I essentially have to retarget the "Brain" on one of them after each kill. The use of a /focus macro would fix this perhaps. If I set the focus on all alts to the "Brain" their target doesn't matter when dpsing and such, correct? So I could loot and skin and save myself a key press with each mob.
Hate to dissapoint you but regardless of whether or not you use a focus or non focus method, if you "unstick" your main - either to skin or dance or /rude someone in particular, you're going to have to /follow in 1 way or the other, be it with focus or non focus - /follow still has to be in there somewhere.
Re read the layout of the big button listed above, you don't have to manually target your main again after each "un-follow" - just hit the big button again.
Get used to mashing that button about 900 times a minute. :)
Trama
06-13-2008, 03:51 PM
Obviously I am not explaining myself correctly. Thanks for being patient. ;(
Typical Fight:
All Slaves have the "Main" targeted and are ready to go. I target a mob with my Main, press my "PEW PEW" button and everyone unleashes a barrage of nature based damage at the Main's target. Now I have a dead mob that needs to be looted, skinned, kicked or spat upon by someone. If I do any of these things on any character but the main, I have to "release" that slave's target. Its no longer on the Main, its now on the dead mob. So now I have a empty/skinless mob laying on the ground and a slave with no target.
Off I go on the main (everyone is still on follow) and target another mob to kill. The slave with no target just sits there as the others dps. I have to mash the Big Button again after every kill essentially to get everyone to target the main again. Its not a follow problem, its a target problem. So, my question was, would the use of /focus and setting the Main to be /focused by all Slaves solve the requirement to keep mashing the Big Button simply for the purpose of having everyone target the main? They would dps their focus target's target always, regardless of what their actual target is at the time.
I think that I know the answer and its that if I want to use a Target of Target style macro set, then I will indeed have to hit the Big Button macro after every fight where looting by a slave is involved.
Zzyzxx71
06-13-2008, 04:20 PM
No, with focus you still have to
A: go back to your main after skinning, dancing, spitting, kicking
B: select another target with your main
C: assist with your slaves
D: /focus on the assist
E: /follow
Focus or no focus, the big button typically facilitates all these.
r0guenj
06-14-2008, 06:58 AM
i wanted to register and say thanks to everyone. the simple yet effective macros in this thread have let me jump right into multiboxing........and have gotten me hooked again on wow!
magwo
06-16-2008, 08:14 AM
Problem: meelee and autoshot (on hunters). You can't have your leader targeted if your are going to meelee or autoshoot.
Or?
Zzyzxx71
06-16-2008, 08:44 AM
Melee no,
/cast [target=targettarget] [] Auto Shot
?
Someone mind testing that?
magwo
06-16-2008, 08:56 AM
I'm fairly sure I tried and failed this with my twink hunters, which is why I switched to focus based stuff.
Knobley
06-17-2008, 10:52 AM
Zzyzxx,
I've been digesting this thread over the last couple of days and plan to give it a thorough try out tomorrow. I'm curious why you didn't respond to Negative1's comment above. It seems like a cogent objection to me (though I admit that i haven't given your no-focus philosophy a playtest yet.)
Knobley
Zzyzxx71
06-17-2008, 03:20 PM
Zzyzxx,
I've been digesting this thread over the last couple of days and plan to give it a thorough try out tomorrow. I'm curious why you didn't respond to Negative1's comment above. It seems like a cogent objection to me (though I admit that i haven't given your no-focus philosophy a playtest yet.)
Knobley
Currently I use no CC, since I haven't used focus as my main form of control - I don't really have a good reference, but from waht I've heard from others - the no focus method tends to have a public opinion of being a little faster regarding slave target switching and lag in general.
Again, I don't have any personal experience with this - just relaying what others have said.
Personally, I haven't had any (major) issues with inadvertantly popping the wrong target. From the way I've seen most all inclusive operate, I don't see how focus is "safer", but my opinion (notice - opinion) is from the outside looking in, and making assumptions.
No focus isn't for all uses - there are situations where it appears focus is required (as posted above, it appears that to successfully run a hunter team, you need focus due to autoshot).
zendarva
06-18-2008, 07:08 AM
I'm in the process of converting Cofused, cosumed, and codemned to using this style of macro, and from the little testing i've done so far, i'd say it works pretty well, especially with trinity bars, and the immense amount of macros it gives you access to. (Heh, finally dragged me away from bongos2)
However, as noted previously, i can confirm that this does not work with autoshot for hunters, nor does it work properly with Shoot for Mages, Priests, or Warlocks. For wands, it fires once, and then you have to mash your wand button again to get it to fire again. If your main is a wand user, they will of course keep firing.
I guess it doesn't completely kill the utility of wanding, just makes it more useful for a finishing touch than anything else. Annoying while grinding though.
Other than that, i'm loving the responsiveness of this sort of macro as compared to focus macros.
Fuzzyboy
06-18-2008, 07:40 AM
The No Focus Manifesto!!!
The functionality of these 4 macros with a little modification (add one for earth shock, frost shock, chain lightning) and you have:
1. Group invite
2. Accept
3. Follow
4. Assist and Pew Pew
Lets explore the following scenario:
Your Brain dies – “OH NO NOT THE BRAIN!!!” – You take control of slave #1, You click your follow macr, Slaves #2,3,4 target Slave #1 based on the way the big button macro is setup.
You start to pew pew with slave #1. Based on the way the casting macros are setup – he is allowed to free fire. The rest of the slaves, targeting slave #1, fire on slave #1’s target (targettarget) without UNTARGETING slave #1.
This might seem like a laborious process, but it’s rather fast.
Brain dies
Take control of slave #X
Press your follow macro
Continue killing.
2 actions and your failover is complete.
First of all: thanks for the work you put into this. I do have a few questions however. I've switched from the focus-style to the no-focus style using your macros, which I like. However!
On my main I have the ordinary dps spell (LB) mapped to my "Q" button and the /cast [target=targettarget] etc mapped to my slaves "Q" buttons. So now my main dies and I switch to slave #1, hit the big button, target a mob and start pewpew'ing, but oh noes, slave #1s pewbutton casts on "targettarget,harm" and since he has a mob targeted, the targettarget will be "help" and hes unable to shoot.
What am I doing wrong here? Do I need to make different keymappings, or?
zendarva
06-18-2008, 12:36 PM
First of all: thanks for the work you put into this. I do have a few questions however. I've switched from the focus-style to the no-focus style using your macros, which I like. However!
On my main I have the ordinary dps spell (LB) mapped to my "Q" button and the /cast [target=targettarget] etc mapped to my slaves "Q" buttons. So now my main dies and I switch to slave #1, hit the big button, target a mob and start pewpew'ing, but oh noes, slave #1s pewbutton casts on "targettarget,harm" and since he has a mob targeted, the targettarget will be "help" and hes unable to shoot.
What am I doing wrong here? Do I need to make different keymappings, or?I had the same problem at first. It needs to be /cast [harm] [target=targettarget, harm] [] Spell name.
The , harm, and the empty set of brackets are what allow it to "fall through" and target without your main after your main dies.
Zzyzxx71
06-18-2008, 01:14 PM
Correct, the [] needs to be there in case A: your slave is the brain and B: in case the slave HAPPENS to have the mob targetted instead of the brain.
I had the same problem at first. It needs to be /cast [harm] [target=targettarget, harm] [] Spell name.
I don't believe the first [harm] needs to be there - if condition 1 "[target=targettarget, harm] "=false, then it will go to condition 2"[]", which will always be true.
After putting some thought into it, here's what I got for autoshot and wanding
/target [target=Main, no dead, help, exists][target=Clone1, no dead, help, exists][target=Clone2, no dead, help, exists][target=Clone3, no dead, help, exists]
/assist
/cast Autoshot (or shoot I guess - whatever the command is for wanding)
Then as long as you have [] in the macros for the remainder of the slaves, they'll still do arcane shot, etc.
Not the most elegant solution immediately, but a workaround.
You'd still need to go through the big button to switch targets though, OR hit the autoshot button to re-assist your current brain.
zendarva
06-18-2008, 03:02 PM
Correct, the [] needs to be there in case A: your slave is the brain and B: in case the slave HAPPENS to have the mob targetted instead of the brain.
I had the same problem at first. It needs to be /cast [harm] [target=targettarget, harm] [] Spell name.
I don't believe the first [harm] needs to be there - if condition 1 "[target=targettarget, harm] "=false, then it will go to condition 2"[]", which will always be true.
After putting some thought into it, here's what I got for autoshot and wanding
/target [target=Main, no dead, help, exists][target=Clone1, no dead, help, exists][target=Clone2, no dead, help, exists][target=Clone3, no dead, help, exists]
/assist
/cast Autoshot (or shoot I guess - whatever the command is for wanding)
Then as long as you have [] in the macros for the remainder of the slaves, they'll still do arcane shot, etc.
Not the most elegant solution immediately, but a workaround.
You'd still need to go through the big button to switch targets though, OR hit the autoshot button to re-assist your current brain.While i know this is the No Focus Manefesto, would wanding/autoshoot work on a focused mob, while you were still targeted on your brain? Hmm. I'll have to try that out later when i'm not so burnt out on fiddling with my macros.
Zzyzxx71
06-23-2008, 09:56 AM
bumpping my own thread!!! omgzoorz!! flog me later.
Finges
06-27-2008, 01:57 AM
Haha.. thanks for bumping it... I was waiting for the manifesto to come out since your first post... and I somehow missed it. :D
Gonna go through and rework all my macros tonight.
-Finges
Caspian
07-15-2008, 03:48 PM
Ok I think I found a solution to the targeting issue with pets.
Basically if you use a pet attack, even if it is off of a /assist your target is switched from your Brain to the target. This is less the optimal. Resetting your target after solves the issue.
/assist target
/petattack
/target [target=Kuolemaa, nodead, help, exists]; [target=Kuolemaa, nodead, help, exists]; [target=Kuolemaa, nodead, help, exists]; [target=Jonika, nodead, help, exists]; [target=Kuolemaa, exists]
Space is an issue in this macro,I would have liked to use the "Big Button" logic for the assist but I ran out of room, so you assume your Brain is targeted hence the /assist target
Next is your /petattack, this could be any pet command
Last I do the full "big button" target on the off chance you brain has died while you are clicking this button. You could also do a /targetlasttarget here.
Finges
07-18-2008, 12:00 AM
Hiya!
I moved to this technique of controlling a while back.. something I noticed.
I'm using the following script...
/cast [target=targettarget, harm] [] Lightning Bolt
If your main has a enemy healer selected.... your main ends up shooting at whomever the enemy healer is healing... So essentially with a 4xshaman team...
1 LB goes to the healers target
3 LB goes to the brains target (Healer).
I'm at work now... but I'm thinking to solve this... I'm going to change the above to this:
/cast [target=target, harm][target=targettarget, harm] Lightning Bolt
If my understanding of macros is correct....
My Main/Brain will use the [target=target, harm] condition and shoot the healer.... and because my slaves are targeting the brain... and he's not "harm" they will move onto the [target=targettarget, harm] conditional.. and pew pew.
Anyone else run into this issue? I mainly noticed it because I was trying to interrupt a healer but for some reason the earth shocks never hit him. :D
-Finges
heyaz
07-18-2008, 07:31 PM
If the alts are listed in order, and my main dies and I have to switch, how does it know which alt to set as the new follow? Say if the main dies, do I need to make sure to switch to the alts in some specific order?
Caspian
07-19-2008, 12:44 AM
yes for me I have it in alphabetical order. It is how you set it up in the "big button"
RobinGBrown
07-19-2008, 07:21 PM
I'm finding that this works better for me, using a different /target line for each toon based on a 'chain of command' logic:
1IC: (blank)
2IC: /target [target=1IC, nodead, help, exists]
3IC: /target [target=1IC, nodead, help, exists]; [target=2IC, nodead, help, exists]
4IC : /target [target=1IC, nodead, help, exists]; [target=2IC, nodead, help, exists]; [target=3IC, nodead, help, exists]
Where 1IC is the main toon, 2IC is the second in command, 3IC is next and so on.
Thus the line above replaces the word TARGET in the follow macro, making each toons macro different:
TARGET
/follow
/stopcasting
This has one advantage over using 'target [target=Party1, nodead, help, exists]; [target=Party2, nodead, help, exists]; [target=Party3, nodead, help, exists]' or similar named macros because you will not get whoever is in command following the 1st remaining party member when the 1IC pops their clogs.
Frosty
07-21-2008, 09:27 AM
First, I have a button for /follow and a button for /assist.
Second, I like to use my /assist on friendly targets for random-run-by-buffing.
I've been having problems with /castseqeunce not resetting when using reset=#/target/combat.. And I also noticed that part of my problem was a slave would sometimes assist the actual target I wanted to kill...
So I played around with the way I had my assist set up and came up with this:
..[edit]..[deleted]....
Slave4 (aka party5)
/target [target=party1, nodead, exists]; [target=party2, nodead, exists]; [target=party3, nodead, exists]; [target=party4, nodead, exists];
/stopmacro [target=party4, dead];
/assist
edit -
Ok, I give up on my above assist method.. too much hassle. I just reverted back to my old method and will deal with the other issue another way.
Old method
Slave4 (aka party5)
/assist [target=party1, nodead, exists]; [target=party2, nodead, exists]; [target=party3, nodead, exists]; [target=party4, nodead, exists];
Elektric
08-11-2008, 11:46 AM
Hiya!
I moved to this technique of controlling a while back.. something I noticed.
I'm using the following script...
/cast [target=targettarget, harm] [] Lightning Bolt
If your main has a enemy healer selected.... your main ends up shooting at whomever the enemy healer is healing... So essentially with a 4xshaman team...
1 LB goes to the healers target
3 LB goes to the brains target (Healer).
I'm at work now... but I'm thinking to solve this... I'm going to change the above to this:
/cast [target=target, harm][target=targettarget, harm] Lightning Bolt
If my understanding of macros is correct....
My Main/Brain will use the [target=target, harm] condition and shoot the healer.... and because my slaves are targeting the brain... and he's not "harm" they will move onto the [target=targettarget, harm] conditional.. and pew pew.
Anyone else run into this issue? I mainly noticed it because I was trying to interrupt a healer but for some reason the earth shocks never hit him. :D
-Finges
This is the reason I moved back to /follow focus. Did this solve the problem?
Rerolled mages and now I need to get free my focus. Chain sheeping will be impossible without it.
Savage
08-21-2008, 01:31 PM
You....are....AWESOME! I was referred to this thread when I made my own asking for a non-focus system for targeting and whatnot and this is AWESOME! THANK YOU SO MUCH!
Melekal
09-12-2008, 01:26 PM
Hiya!
I moved to this technique of controlling a while back.. something I noticed.
I'm using the following script...
/cast [target=targettarget, harm] [] Lightning Bolt
If your main has a enemy healer selected.... your main ends up shooting at whomever the enemy healer is healing... So essentially with a 4xshaman team...
1 LB goes to the healers target
3 LB goes to the brains target (Healer).
I'm at work now... but I'm thinking to solve this... I'm going to change the above to this:
/cast [target=target, harm][target=targettarget, harm] Lightning Bolt
If my understanding of macros is correct....
My Main/Brain will use the [target=target, harm] condition and shoot the healer.... and because my slaves are targeting the brain... and he's not "harm" they will move onto the [target=targettarget, harm] conditional.. and pew pew.
Anyone else run into this issue? I mainly noticed it because I was trying to interrupt a healer but for some reason the earth shocks never hit him. :D
-FingesI like this train of thought here but wouldn't you run into a problem if your main is mind controlled? I would think in that case you would end up killing your own guys....
Jelatin
09-13-2008, 11:04 PM
I found something that might be really helpfull. Since this is a focus/leaderless type setup... it will work regardless of who is the current "main"
This is a healing macro to heal your mains attackers target. (hope that makes sense)
/cast [target=targettargettarget, help] [] Healing Wave
If you dont have a target, it heals the toon that casts it.
Zzyzxx71
12-24-2008, 11:16 AM
I need this back at the top because I'm BOXXIN AGAIN BABY!!!
I need this back at the top because I'm BOXXIN AGAIN BABY!!!YAY!!!
and a quick note, if you have and target state conditionals (nodead, harm, etc) you do not need exists in the conditional line as the others infer exists.
In other words: if it is nodead it has to exists as non-existent targets can be neither dead or nodead. So you can just remove that from the macro if you are having space issues.
Zzyzxx71
12-26-2008, 11:26 AM
Note to self - don't EVER EVER EVER delete your WOW directories even if you think you'll never play again - at least save your macros somewhere. Restarting from scratch sucks ASS!!!
Simulacra
05-29-2009, 04:12 AM
/bump - this has been lost in the mists of time for too long
Ualaa
06-24-2009, 10:02 PM
*Edit*
Figured out what I was doing wrong.
Too used to having the slaves target the Party Leader's target for their spells.
Pressing F1 to target the leader... has the slaves target themselves.
In a party leader system, it makes no difference who the slaves target...
The heal or nuke is determined by the leader's target.
Will either have to put F1 on the Do Not Pass list...
Or maybe train myself to mouse click, even though keybinds are faster.
The big button is an option possibly, if I don't mind the slaves running into melee with the tank.
Maxion
06-28-2009, 08:32 AM
Just unbind the default F1 binding in your keybindings.
vBulletin® v4.2.2, Copyright ©2000-2025, Jelsoft Enterprises Ltd.