Leaderless setup for dummies.

[Nafos]

So i'm being ganked by a rogue / priest . Both full epic i'm full blue. Killed me a couple of times because i fucked up with pressing pause and getting so fucking lucky you have no idea. I dont have a leaderless setup. So they kill my main and the priest runs out of range and the rogue downs them. its impossible to out dps the priests healing and so with no way of killing the priest they are 2 maning me since i only have 3,5k hp when i res.

I want to fucking understand this leaderless setup but i dont have time. Can someone please make a step by step guide to making one? . I've seen the guides and explenations it just takes ages to get into.

[Budkin]

Try this dont die lol

[Nafos]

What does that have to do wit ANYTHING that i just said...

[Ualaa]

Well, the FTL thread is probably the best leaderless setup. But its a fair bit of configuration and time invested.
It's probably worth it, long term. And posting in thread is probably the best support for it too.

A simpler method of assisting would be to either assist your focus or assist party1.
The focus is an easier method to implement, but you lose the focus ability for other aspects.

With focus, all of your toons would be:
/cast [target=focustarget] Ability

It does not matter which of your toons is the leader at a given time, as long as the leader macro makes them the focus target.
So you'd have a promote button per toon. Three toons would mean three promote buttons.
The buttons for making another toon the leader would also make that toon your current focus.
So if you switch to toon 2, you press button 2 on all toons, which makes toon 2 the focus of all toons, toon 2 included.

Each toon, toon 2 included, hits toon 2's target.
If you switch to toon 3, toon 3 becomes the focus on all toon's, and they all assist toon 3.
It makes no difference if one of your toons goes down, because any of the remaining toons is the focus and all remaining toons assist them as easily as the first.




I believe the assist party1 to be essentially the same system as far as mechanics go, except that you use paging instead of focus.
As in all toons have bar 1 as their assist macro's and bar 2 as their non-assist macro's.
The switch active toon macro then makes the new leader the party leader and switches their bar to the non-assist page.
At the same time, it switches the former leader to the assist page of buttons.
The leader's macro is something like... /switchactionbar 2.
The slaves macro is something like... /switchactionbar 1 -and- /script PromoteToLeader("New Leader Name")
This uses up an extra bar per toon, but free's up your focus for cc's (pve) or burning the focus target without targeting them (pvp).
*EDIT*
The bar1 macro's would be... /cast [target=party1target] Spellname... the bar2 macro's would be /cast Spellname.
You could use a castsequence too, however you normally have your spells set up.




The FTL system is superior in that you have all of the alts assist the current main, without using the Focus, Target or Assist a Leader options.
Essentially Keystrings (Keyclone) do the assist for you behind the scenes.
If you're willing to mess around with it, until it works, the FTL system will be the strongest of the three.




So depending on the amount of time/configuration you want to put into it, these are your basic options.
Hopefully something helps you out of this.

[Nafos]

Yeah thanks for a helpfull post! :)

[algol]

If you suk solo pvping more guys wont help
Try this dont die lol50 mages all spamming arcane explosion at the same time tends to make anyone attacking you die.

[Nafos]

GL trying to down 13k hp on a priest with pain subpression before he aoe fears you AND a rogue doesnt down 3,5k hp on you.

[Ualaa]

Once you're dead and they're camping you, you'd leave the computer and make a sandwich.
Enjoy your sandwich and beer.
Chances are they're gone.

A set up where any toon can lead as well as any other, results in not automatically losing if your initial leader goes down.
A castsequence for Tremor will help immensely against fear.

/castsequence Tremor Totem,,,
/castsequence ,Tremor Totem,,
/castsequence ,,Tremor Totem,
/castsequence ,,,Tremor Totem

One macro per shaman. Since tremor pulses every two seconds, and you'll have this same macro (well line 1, shaman 1, line 2 shaman 2 etc) on the same keybind for each shammy, you want to end up mashing this hotkey 4 times over 2 seconds. That way, when they fear-bomb you, you will run for a maximum of half a second, before the fear ends.

Once they're camping your corpses, its a lot harder, but if your set up is decent.. it will be a lot harder for them to have you in this position.

Another thing that will help you a lot, will be the ability to turn your alts independently of your main.
You can have WASD for keyboard movement on your main, and the arrow keys (up/down/left/right) for movement on your alts.. or whatever works for you.
So if the rogue decides to weave in and out of your toons, you can turn them without having to have them follow your main.
Not necessarily saying it will save you from a higher level and better geared toon in your midst, but you'll have a fighting chance at least.

My toons have this macro:

#show Lighting Bolt
/cast [harm]Lightning Bolt; [help] Lesser Healing Wave

The alts add /assist [target=party1] in between the #show and the /cast line.

If the rogue uses Cloak of Shadow to basically become immune to your damage for a few seconds, you can have them all heal whoever he goes against.
It doesn't hurt to have something like:

#show
/cast Chainheal [target=player]

Put that on the same keybind for every toon. Clicking it will have them all Chain Heal themselves. The second jump automatically goes to whoever is most injured within range. So they all get a primary C.Heal as well as whoever is being hit getting a second hit from the other shamans.

Aside from the ability to dump four Tremors in rapid succession, a grounding per shaman all at once is a very useful hotkey as well.
You don't even need a macro for that, just drag Grounding to the same hotkey for each shammy.
So if you're against a class which can charm, seduce or more likely fear-bomb, do the staggered Tremors.
If you're against a caster player or mob, the four groundings will serve you well.

In addition to your Groundings and Tremors, a cast sequence for Totems is helpful at times.
Ideally, if you know something is coming or are initiating something, you'd drop all totems as part of this sequence.
Then you'd re-drop the Earth totems (tremors) spaced a lot better (closer together) then a castsequence can do.

By this I mean.. if you put your castsequence on say hotkey BACKSPACE and mashed it four times, the best you could hope for would be a Tremor to pulse every second. So you'd probably want back to back Tremor Totems as part of this castsequence, but it would be even better if you were to drop the Tremors either before or after the sequence.

#1: /castsequence reset=12 Grounding Totem, Totem of Wrath, Healing Stream Totem
#2: /castsequence reset=12 Grounding Totem, Mana Spring Totem, Searing Totem
#3: /castsequence reset=12 Grounding Totem, Mana Spring Totem, Searing Totem
#4: /castsequence reset=12 Grounding Totem Mana Spring Totem, Searing Totem

That's just an example. You might want to put Poison Cleansing or Disease Cleansing in, in the place of a water totem (Disease will counteract Death Knight powers, Poison is useful against Hunters and Rogues). You could also include Earth Totems in the rotation.

*Edit* - Not even sure if your team is shammies, but you could adapt these idea's to your set up regardless.

[Zappy]

I use the FTL system, and yes - it's a huge headache to set up, but easy to use once you understand it. I'm also using Dominos.

I'll try to explain my setup the best I can.

First, is my "Assist" macro:



/stopmacro [nomod]
/assist [mod:ctrl,mod:shift,nomod:alt] Zappyzap; [mod:ctrl,mod:alt,nomod:shift] Zappityzap; [mod:alt,mod:shift,nomod:ctrl] Zappzapp; [mod:ctrl,mod:alt,mod:shift] Zappity; [mod:ctrl,nomod:alt,nomod:shift] Zapzappy;


Then all my targeting spells reference it:



#show Chain Lightning
/click MultiBarRightButton12
/cast [harm, exists] Chain Lightning
/stopmacro [nomod]
/targetlasttarget


The MultiBarRightButton12 is the dominos named button for my assist. If using dominos, you can hover over the button when in the "bind keys" mode, and it will tell you the name of the button.

On all 5 instances, I have button "1" setup to use the exact same chain lightning macro.

Here are my keymaps for each instance:

A:


k(49.0.0):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.4.4):hs(chainlightning.E.target)


B:


k(49.5.5):hs(chainlightning.A.target)
k(49.0.0):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.4.4):hs(chainlightning.E.target)


C:


k(49.5.5):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.0.0):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.4.4):hs(chainlightning.E.target)


D:


k(49.5.5):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.0.0):hs(chainlightning.D.target)
k(49.4.4):hs(chainlightning.E.target)


E:


k(49.5.5):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.0.0):hs(chainlightning.E.target)


So if you look closely at each one of them, the only difference between them is the current one which has no modifiers.

Now take a closer look at what happens when you press the number "1". say, instance "b" happens to be currently active, no modifiers get passed. Keyclone will see that "1" was pressed, and generate "chainlightning.B.target". Keyclone will then read the keymap associated to each instance, so that the other 4 instances all receive the keystroke k(49.20.20) -- ("1" with modifier Ctrl, Alt)

So all 5 instances will begin executing the chain lightning macro. When they call the assist macro, it will then tell all the clones to assist the toon that uses the modifiers "ctrl-alt", or else stop running the assist macro if has no modifiers (this will be the toon that is currently active). At this point, your active toon will be targeting your real target, and all 4 clones, should now be assisting that toon.

The rest is straight forward. It simply casts the chain lightning, and then targets your last target if you're not the active toon.

I chose using two macros for everything, as my 5th account has both a 70 shammy and a 70 paladin, so whenever I want to run the group with 4 shammys and a paladin, i can swap out the assist macro to the following and have everything else work the same way:



/stopmacro [nomod]
/assist [mod:ctrl,mod:shift,nomod:alt] Zappyzap; [mod:ctrl,mod:alt,nomod:shift] Zappityzap; [mod:alt,mod:shift,nomod:ctrl] Zappzapp; [mod:ctrl,mod:alt,mod:shift] Zappity; [mod:ctrl,nomod:alt,nomod:shift] Zappytank;


My suggestion would be to work with the basics and only focus on getting one spell working before trying to make lots of keymaps. Lesser Healing Wave is an ideal candidate as you can work on that anywhere and aren't required to be in combat. In addition, you can check the combat logs to ensure that they are all assisting properly. It may be useful to remove the /targetlasttarget so you can actually see what it's doing.

Good luck with it. Understanding the keymaps are by far the hardest part of all of this, and once you understand them, and get one spell working, the rest will slowly fall in place. I originally started with the /focus method for the leader, and after switching, it took me a few days before I felt like I was operating efficiently again.

[Dinkydau]

OMG, I'll just let my guys die in place. lol

[Dinkydau]

OMG Zappy, I'll just let my guys die in place. lol

[Gares]

Zappy I don't get your keystring modifiers..

k(49.5.5):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.0.0):hs(chainlightning.E.target)


What is the k(49.5.5):hs and so on for each target. I use the setup as well but I don't get what the modifiers are...

I don't use any addons so maybe that is why I am confused...

[Zappy]

Zappy I don't get your keystring modifiers..

k(49.5.5):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.0.0):hs(chainlightning.E.target)


What is the k(49.5.5):hs and so on for each target. I use the setup as well but I don't get what the modifiers are...

I don't use any addons so maybe that is why I am confused...

The modifiers are the keys like Ctrl, Alt, & Shift. The first number "49" is the ascii code for "1", and the 2nd one is for the modifiers. ie. k(49.5.5) equates to "Ctrl-Shift-1", k(49.20.20) = "Ctrl-Alt-1", etc.

I provided what was in each keymap file, so if you create a file for each one of them, you can load them into keyclone. For this example, name the file "e.kcl" then paste the following code:



Toon E
k(49.5.5):hs(chainlightning.A.target)
k(49.20.20):hs(chainlightning.B.target)
k(49.17.17):hs(chainlightning.C.target)
k(49.21.21):hs(chainlightning.D.target)
k(49.0.0):hs(chainlightning.E.target)


Now when you load the keymap into keyclone, you can see all the bindings.

Dinkydau, i don't blame you one bit. Like I said, it was a complete headache to get up and running, but that's the beauty of it. once it's up and running, it works awesome. From this example, i can press the number 1 having any one of the 5 instances active, and all 5 of them react to the active windows target and cast chain lightning. When your "leader" dies with this setup, it makes it extremely easy to continue on and come back from the dead. In bgs and arenas, there are many times where this has saved me and gave me plenty of time to res my dead.

[Gares]

ok I got it. I had to get home and look at my own keymaps to figure out what is going on.

My only difference is I don't call an assist or use focus in mine so I got to take a look again on yours about what your doing.

[Method]

Once you're dead and they're camping you, you'd leave the computer and make a sandwich.
Enjoy your sandwich and beer.
Chances are they're gone.

A set up where any toon can lead as well as any other, results in not automatically losing if your initial leader goes down.
A castsequence for Tremor will help immensely against fear.

/castsequence Tremor Totem,,,
/castsequence ,Tremor Totem,,
/castsequence ,,Tremor Totem,
/castsequence ,,,Tremor Totem

One macro per shaman. Since tremor pulses every two seconds, and you'll have this same macro (well line 1, shaman 1, line 2 shaman 2 etc) on the same keybind for each shammy, you want to end up mashing this hotkey 4 times over 2 seconds. That way, when they fear-bomb you, you will run for a maximum of half a second, before the fear ends.

Once they're camping your corpses, its a lot harder, but if your set up is decent.. it will be a lot harder for them to have you in this position.

Another thing that will help you a lot, will be the ability to turn your alts independently of your main.
You can have WASD for keyboard movement on your main, and the arrow keys (up/down/left/right) for movement on your alts.. or whatever works for you.
So if the rogue decides to weave in and out of your toons, you can turn them without having to have them follow your main.
Not necessarily saying it will save you from a higher level and better geared toon in your midst, but you'll have a fighting chance at least.

My toons have this macro:

#show Lighting Bolt
/cast [harm]Lightning Bolt; [help] Lesser Healing Wave

The alts add /assist [target=party1] in between the #show and the /cast line.

If the rogue uses Cloak of Shadow to basically become immune to your damage for a few seconds, you can have them all heal whoever he goes against.
It doesn't hurt to have something like:

#show
/cast Chainheal [target=player]

Put that on the same keybind for every toon. Clicking it will have them all Chain Heal themselves. The second jump automatically goes to whoever is most injured within range. So they all get a primary C.Heal as well as whoever is being hit getting a second hit from the other shamans.

Aside from the ability to dump four Tremors in rapid succession, a grounding per shaman all at once is a very useful hotkey as well.
You don't even need a macro for that, just drag Grounding to the same hotkey for each shammy.
So if you're against a class which can charm, seduce or more likely fear-bomb, do the staggered Tremors.
If you're against a caster player or mob, the four groundings will serve you well.

In addition to your Groundings and Tremors, a cast sequence for Totems is helpful at times.
Ideally, if you know something is coming or are initiating something, you'd drop all totems as part of this sequence.
Then you'd re-drop the Earth totems (tremors) spaced a lot better (closer together) then a castsequence can do.

By this I mean.. if you put your castsequence on say hotkey BACKSPACE and mashed it four times, the best you could hope for would be a Tremor to pulse every second. So you'd probably want back to back Tremor Totems as part of this castsequence, but it would be even better if you were to drop the Tremors either before or after the sequence.

#1: /castsequence reset=12 Grounding Totem, Totem of Wrath, Healing Stream Totem
#2: /castsequence reset=12 Grounding Totem, Mana Spring Totem, Searing Totem
#3: /castsequence reset=12 Grounding Totem, Mana Spring Totem, Searing Totem
#4: /castsequence reset=12 Grounding Totem Mana Spring Totem, Searing Totem

That's just an example. You might want to put Poison Cleansing or Disease Cleansing in, in the place of a water totem (Disease will counteract Death Knight powers, Poison is useful against Hunters and Rogues). You could also include Earth Totems in the rotation.

*Edit* - Not even sure if your team is shammies, but you could adapt these idea's to your set up regardless.A+++ post, you are the man sir.