Focusless Targetless Leaderless Setup

From Dual-Boxing Wiki

Proloque

As the following thread describes the FTL technique for keyclone (where an ftl was first used), nowadays there are some other softwares you can implement an FTL with:

1. FTL with HotKeyNet

Anemo was so kind to implement the focusless targetless leaderless Setup with HotkeyNet! Although the following text was written with keyclone in mind, the general idea and all macros presented here can be used, only the setup of the keymapping is diffrent!

For more Information how to do it with Hotkeynet instead of Keyclone see:

Implementing an FTL quite simple with Templates

Leaderless setup with HotKeyNet

2. FTL with AutoHotKey

Wowphreak was so kind, to post his script he is using to implement an ftl in AutoHotKey, for more information see: Leaderless setup with AutoHotKey

3. FTL with Innerspace/ISBoxer

With ISBoxer Lax introduced a quite simple Method how you could use an FTL in Innerspace, for more Information see: Setting up Focus or FTL in minutes with ISBoxer

Introduction / Aim

In the following article a focusless, targetless and leaderless (ftl) software-multiboxing setup is described.

This means:

Focusless/Targetless:

The ‘focus’/’target’ of each toon is neither used for specifying the group leader nor the dps-target, so it can be freely used for other needs, like setting cc-targets.

Leaderless:

There is no predefined leader/main of the group. The leader of your group will automatically be the toon you're currently controlling.

Pros:

Free use of focus and target on each toon
Simple leader-switching without the need of using focus/target or dying of the former leader
Solo-playability of each toon
Easy recovery of half-group-deaths

Cons:

Quite complex setup
Need of Keyclone for using the hotstring/keymap feature (perhaps it is possible with AHK or Octopus also)
Needs a lot of macros with a lot of chars, so a macro-char-extender (like trinitybars) is recommend

Credits:

All credits for the idea and posting on the forum of this system goes to Deceased and Pocalypse, also nearly all informations given here can be found in: Focusless Targetless Leaderless Setup - Forumthread

Basics

Hotstrings / Keymaps

Normally with a keyboardmultiplexer what happens when you press a key is that the same key is broadcasted to all other hosts/windows. Like a simple press of ‘2’ would result in all hosts receiving a ‘2’-keystroke.

With hotstrings and keymaps you can alter this behavior to broadcast a different key than you pressed to your toons. For example you could have a paladin, mage and warlock and setup hotstrings that you could press ‘1’ on the paladin, the mage receives a ‘2’ and the warlock a ‘3’.

To describe a hotstring I will use the following syntax:

‘key-to-press’ ---> ‘hotstring-name’

A keymap is the composition of all hotstrings for one toon. In Keyclone you can define hotstrings in the keymap-editor and setup in the command-editor which toon should use which keymap.

To setup the example above you could define the following keymaps for each toon:

Keymap - Paladin:         ‘1’ ---> ‘test’
Keymap – Mage:            ‘2’ ---> ‘test’
Keymap – Warlock:         ‘3’ ---> ‘test’

Terminology

In this section I shortly define what I mean if I speak of the following terms:

Main/Leader: This means the active played toon, for example the toon which defines the target and whom the other toons follow.

Slave: The not active played toon (the followers)

master-key: This is the keybinding which you would use in solo-play, like normally 1 to 9 for the first actionbar.; On this keybindings you could drag your normal Spells, like for example Lightning Bolt

slave-key: This keybinding is only used in multiboxed-play, if the toon is a slave.; Typically a macro which tells you whom to assist/follow would be used here.

Setup

Principal idea

The principal idea of the ftl-system is to use the possibilities of keymaps and hotstring to get a system where the leader is defined by if it’s the actively played toon, using hotstrings to tell the slave whom they should assist/follow instead of using focus or target.

How can this be achieved?

This can be achieved by using modifiers (like shift,alt …) in your macros to identify which toon is the leader.

So first thing you do is define a unique modifier combination for each of your toons, like:

Ctrl + Shift + key = ToonA is leader
Ctrl + Alt + key = ToonB is leader
Alt + Shift + key= ToonC is leader
Ctrl + Alt + Shift + key = ToonD is leader
Ctrl + key = ToonE is leader

With this you could use the following macro bind on for ex. ‘2’ to do a Lightning Bolt:

/assist 
[mod:ctrl,mod:shift,nomod:alt]ToonA;
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;
[mod:ctrl,nomod:alt,nomod:shift]ToonE
/cast [harm] Lightning Bolt
/targetlasttarget

(these are only two lines, split here for better visualization)

“Great, but now I have to press wired combinations like alt+shift+2 to tell my toons, that ToonC is the leader and they should throw a Lightning Bolt on his target. Forget it!” you say.

“Of course not! Let hotstrings handle the hassle for you!” I say.

This can be achieved by defining a keymap for each toon which corresponds to the defined modifier-combination above.

The generic keymap for the above combination would be:

‘Ctrl + Shift + key’ ---> ‘command.ToonA’
‘Ctrl + Alt + key’ ---> ‘command.ToonB’
‘Alt + Shift + key’---> ‘command.ToonC’
‘Ctrl + Alt + Shift + key’ ---> ‘command.ToonD’
‘Ctrl + key’ ---> ‘command.ToonE’

If you would use this keymap on all your toons and press ‘key’ nothing would happen because none of the hotstrings reacts on a simple keypress.

Remember:

what you want to achieve is, that you press a simple key on your active toon (master) and then Keyclone sends the corresponding modifier-combination plus a key to all the slaves, telling them that your active toon is the master.

So what you do is:

Substitute for ‘ToonX’:

‘modifiers + key’ ---> ‘command.ToonX’ with ‘master-key’ ---> ‘commandToonX’.

(The ‘master-key’ can be the same as the ‘key’ (slavekey) but doesn't need to be.)

In fact, if you want to use modifiers for different abilities (like ‘2’ = Lightning Bolt, ‘shift+2’ = Chain Lightning’), you need to use different keys for the master-key and slave-key.

Sidenote: Don’t use F1-F12 for your ‘slave-keys’ cause some modifiers aren’t available for them. And Alt+F4 is never a good idea ;)

5 Shaman Lightning Bolt Example

Example of the keybindings/macros for 5 shaman, with ‘2’ as the master-key and ‘i’ as the slave-key, which casts Lightning Bolt on the target of the active toon:

Generic-Keymap (like above):

Ctrl + Shift + i = ToonA is leader
Ctrl + Alt + i = ToonB is leader
Alt + Shift + i = ToonC is leader
Ctrl + Alt + Shift + key = ToonD is leader
Ctrl + key = ToonE is leader

Key-Map for ToonA:

‘2’ ---> ‘lightningbold.on.ToonA.target’
‘Ctrl + Alt + i’ ---> ‘lightningbold.on.ToonB.target’
‘Alt + Shift + i’---> ‘lightningbold.on.ToonC.target’
‘Ctrl + Alt + Shift + i’ ---> ‘lightningbold.on.ToonD.target’
‘Ctrl + i’ ---> ‘lightningbold.on.ToonE.target’

Key-Map for ToonB:

‘Ctrl + Shift + i’ ---> ‘lightningbold.on.ToonA.target’
‘2’ ---> ‘lightningbold.on.ToonB.target’
‘Alt + Shift + i’---> ‘lightningbold.on.ToonC.target’
‘Ctrl + Alt + Shift + i’ ---> ‘lightningbold.on.ToonD.target’
‘Ctrl + i’ ---> ‘lightningbold.on.ToonE.target’

Key-Map for ToonC:

‘Ctrl + Shift + i’ ---> ‘lightningbold.on.ToonA.target’
‘Ctrl + Alt + i’ ---> ‘lightningbold.on.ToonB.target’
‘2’---> ‘lightningbold.on.ToonC.target’
‘Ctrl + Alt + Shift + i’ ---> ‘lightningbold.on.ToonD.target’
‘Ctrl + i’ ---> ‘lightningbold.on.ToonE.target’

Key-Map for ToonD:

‘Ctrl + Shift + i’ ---> ‘lightningbold.on.ToonA.target’
‘Ctrl + Alt + i’ ---> ‘lightningbold.on.ToonB.target’
‘Alt + Shift + i’---> ‘lightningbold.on.ToonC.target’
‘2’ ---> ‘lightningbold.on.ToonD.target’
‘Ctrl + i’ ---> ‘lightningbold.on.ToonE.target’

Key-Map for ToonE:

‘Ctrl + Shift + i’ ---> ‘lightningbold.on.ToonA.target’
‘Ctrl + Alt + i’ ---> ‘lightningbold.on.ToonB.target’
‘Alt + Shift + i’---> ‘lightningbold.on.ToonC.target’
‘Ctrl + Alt + Shift + i’ ---> ‘lightningbold.on.ToonD.target’
‘2’ ---> ‘lightningbold.on.ToonE.target’

Macros:

Bind this Macro on each toon to ‘i’ :

/assist 
[mod:ctrl,mod:shift,nomod:alt]ToonA; 
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;
[mod:ctrl,nomod:alt,nomod:shift]ToonE
/cast [harm] Lightning Bolt
/targetlasttarget

Drag the Lightning Bolt spell from your spellbook to the button bound to ‚2‘ if you want, that your active toon also casts Lightning Bolt.

What will this do?

- Imagine you’re master is ToonA and you pressing ‘2’ the following will happen:

Keyclone receives ‘2’ from ToonA.
The keymap of ToonA contains the line: ‘2 ---> ‘lightningbold.on.ToonA.target’ so as a hotstring keyclone chooses ‘lightningbold.on.ToonA.target’
Keyclone looks up the keymaps of all the slaves and finds that the key-combination ‘Ctrl + Shift + i’ corresponds to the hotstring ‘lightningbold.on.ToonA.target’
Keyclone send the key-combination ‘Ctrl + Shift + i’ to all the slaves
because on all slaves the ‘/assist …’-macro from above is bound to ‘i’ and is activated with the modifiers ‘shift’ and ‘ctrl’ the following commands are executed:
```
/assist ToonA
/cast [harm] Lightning Bolt
```
all toons cast Lightning Bolt on the target of toonA

The beauty of the system is, that when toonB would be your active toon and you press ‘2’, keyclone would get the hotstring ‘lightningbold.on.ToonB.target’ , translate it to ‘Ctrl + Alt + i’ key-press which corresponds in:

/assist ToonB
/cast [harm] Lightning Bolt

And fires of an Lightning Bolt on ToonBs target.

Solo-Playability

One reason why a master/solo-key (‘2’) and a slave-key(‘i’) is used in the above example is that you can gain solo-playability by doing so.

This is because on the buttons you need to use in solo-play no special ‘multi-boxing-macros’ are bound, but simple spells or ‘normal -macros’.

Idealy you would use keys that you normally don’t press for your ‘slave-key’, not a simple ‘i’ as mentioned above.

To get a overview of the possible bindings see: Available Keys in World of Warcraft

Modifiers

One problem with the ftl-setup is, that the use of modifiers in your normal macros isn’t so intuitive as in a normal focus or assist based approach.

Example:

If you want to do a makro which in your focus-based approach was bound to ‘2’ and like:

/assist focus
/cast [harm,mod:shift]Chain Lightning;[harm]Lightning Bolt

You can’t simply bind the following to your ‘slave-keys’:

/assist 
[mod:ctrl,mod:shift,nomod:alt]ToonA;
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;
[mod:ctrl,nomod:alt,nomod:shift]ToonE
/cast [harm,mod:shift]Chain Lightning;[harm]Lightning Bolt

Because, if for example ToonC is the active toon and you press the master-key on him (‘2’), the key combination ‘alt + shift + slave-key’(alt + shift + i) would be send to all the slaves and all cast Chain Lightning (because of shift) instead of Lightning Bolt as you wished.

There is a workaround which enables you to use modifiers with the ftl-approach, with one condition:

You have to use different keys for the ‘master-key’ and the ‘slave-key’.

If you do so, the solution for the modifier problem is:

For every modifier-combination you wish to use with your ‘master-key’ create a different keymap and macro on a ‘slave-key’.

To show it for the above example:

First set up the Lightningbolt Keymaps, as in the “5 Shaman Lightning Bolt Example” above.

By doing so you get the functionality of pressing ‘2’ on the master and all slaves cast Lightning Bolt on the masters target.

To get them to cast Chain Lightning if you press ‘shift+2’ on the master create the following keybindings for each toon:

Key-Map for ToonA:

‘shift+2’ ---> ‘chainlightning.on.ToonA.target’
‘Ctrl + Alt + k’ ---> ‘chainlightning.on.ToonB.target’
‘Alt + Shift + k’---> ‘chainlightning.on.ToonC.target’
‘Ctrl + Alt + Shift + k’ ---> ‘chainlightning.on.ToonD.target’
‘Ctrl + k’ ---> ‘chainlightning.on.ToonE.target’

Key-Map for ToonB:

‘Ctrl + Shift + k’ ---> ‘chainlightning.on.ToonA.target’
‘shift+2’ ---> ‘chainlightning.on.ToonB.target’
‘Alt + Shift + k’---> ‘chainlightning.on.ToonC.target’
‘Ctrl + Alt + Shift + k’ ---> ‘chainlightning.on.ToonD.target’
‘Ctrl + k’ ---> ‘chainlightning.on.ToonE.target’

Key-Map for ToonC:

‘Ctrl + Shift + k’ ---> ‘chainlightning.on.ToonA.target’
‘Ctrl + Alt + k’ ---> ‘chainlightning.on.ToonB.target’
‘shift + 2’---> ‘chainlightning.on.ToonC.target’
‘Ctrl + Alt + Shift + k’ ---> ‘chainlightning.on.ToonD.target’
‘Ctrl + k’ ---> ‘chainlightning.on.ToonE.target’

…. (I think you get it for the other two ;) )

And bind the following macro on the slave-key ‘k’ to each:

/assist 
[mod:ctrl,mod:shift,nomod:alt]ToonA;
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;
[mod:ctrl,nomod:alt,nomod:shift]ToonE
/cast [harm]Chain Lightning

Examples / Other sources

In this section i like to point to some examples / explanations / discussions which are mainly burried in the long ftl-thread. This examples are in no real order!

Good example from Araketh: [1]

Example how the keymapping might actualy look in keyclone: [2]

Example for 2/3-Boxing (but also helpfull for understanding the steps and concept): [3] [4]

Troubleshooting

As the setup of the system is quite complex, i like to give some basic ideas of the common problems and some solutions in this paragraph.

Some simple reminders:

Not all modifiers are available for all keys (for ex. there is no ALT + F1).
Make sure you not simple copy the macros whithout changing ToonA - ToonE to the names of your chars
Don't forget to actualy load the keymaps (manualy or with the command option)!
You need a seperate keymap for all of your Toons!

Some more complex questions (with possible answers):

When I use the macro my Toons only say someting wierd like '[mod:ctrl,mod:shift,nomod:alt]ToonA;[mod:ctrl,mod:alt,nomod:shift]ToonB;[mod:alt,mod:shift,nomod:ctrl]ToonC;[mod:ctrl,mod:alt,mod:shift]ToonD;[mod:ctrl,nomod:alt,nomod:shift]ToonE' in the chat

This is, because for better readability of the macros the modifier combinations in the '/assist'-command are wirten on more than one line, to get it work, you have to erase the line-breaks, so that the '/assist' (or /cast ...) is only one line.

When I press the master-key on my 'main' the 'slaves' do nothing

This can have many reasons, but the most common is, that you have variations of your 'slave-key' bound to other things. Example: if you use 'u' as your 'slave-key' make sure, that every modifier combination of 'u' you use to identify your toons is unbound (like 'alt-u' ...), and only 'u' is bound to the button with the macro on each toon.

To check if your toons respond to the keybindings at all, you could first bind a realy simple '/say' macro to the button, or use a complex one like:

/target [mod:ctrl,mod:shift,nomod:alt,target=ToonA][mod:ctrl,mod:alt,nomod:shift,target=ToonB][mod:alt,mod:shift,nomod:ctrl,target=ToonC][mod:ctrl,mod:alt,mod:shift,target=ToonD][mod:ctrl,nomod:alt,nomod:shift,target=ToonE]
/say %t is leading

I used the same key as 'master-key' and 'slave-key' and following and assisting doesn't work right

This might be, because when you use the same key, you have to make sure, that the main toon does the correct thing. For example, if you use a macro like this:

/target 
[mod:ctrl,mod:shift,nomod:alt,target=ToonA]
[mod:ctrl,mod:alt,nomod:shift,target=ToonB]
[mod:alt,mod:shift,nomod:ctrl,target=ToonC]
[mod:ctrl,mod:alt,mod:shift,target=ToonD]
[mod:ctrl,nomod:alt,nomod:shift,target=ToonE]
/cast [target=targettarget] Lightning Bolt

and you have the same master and slave key,two wired things could happen:

1. The master Tagets himself and looses the actual DMG-Target

2. The master trys to cast a LB on the target of his target, which wouldn't work

to fix this you could instert [nomod] conditions like:

/target
[nomod,target=target]
[mod:ctrl,mod:shift,nomod:alt,target=ToonA]
[mod:ctrl,mod:alt,nomod:shift,target=ToonB]
[mod:alt,mod:shift,nomod:ctrl,target=ToonC]
[mod:ctrl,mod:alt,mod:shift,target=ToonD]
[mod:ctrl,nomod:alt,nomod:shift,target=ToonE]
/cast [nomod,target=target][target=targettarget] Lightning Bolt

Special Techniques

In this section some special techniques are shown for the ftl.

Follow

In the above examples only macros for casts are shown, if you want to setup a follow-key for your toons, do the keymapping like you would do for a cast (with a key you would press when you want the clones to follow you as the ‘master-key’) and bind the following macro for on the assigned slave-key:

/target [mod:ctrl,mod:shift,nomod:alt,target=ToonA] 
[mod:ctrl,mod:alt,nomod:shift,target=ToonB] 
[mod:alt,mod:shift,nomod:ctrl,target=ToonC] 
[mod:ctrl,mod:alt,mod:shift,target=ToonD] 
[mod:ctrl,nomod:alt,nomod:shift,target=ToonE] 
/follow 
/targetlasttarget

Sidenote: If you use the same key for your master-key and slave-key use a /stopmacro [nomod] before the first line.

Using /castsequences

You can use the most /castsequences with the ftl-System like you would do in your normal system. So for example if you want to do a 3x Lightningbolt, 1x Chain Lightning the correspondig macro would look like this:

/assist 
[mod:ctrl,mod:shift,nomod:alt]ToonA; 
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;
[mod:ctrl,nomod:alt,nomod:shift]ToonE
/castsequence Lightning Bolt,Lightning Bolt,Lightning Bolt,Chain Lightning
/targetlasttarget

A problem with using castsequences exists, when you use 'reset=' with conditions which are depending on the actual target or modifiers, namely:

reset=target

reset=alt

reset=shift

reset=ctrl

Some conditions which would work fine with the system are:

reset=3 (time conditions)

reset=combat

for the 'reset=modifier' there is, in the basic ftl setup no real workaround known, because the modifiers are used to identify who the leader is.

The 'reset=target' can be used, if you don't depend on the 'targetless', then you can get rid of the '/targetlasttarget'. Because a simple assist shouldn't change the target of your slave when the leader doesn'T change it.

Using modifiers direct in '/cast' to avoid assist

one modification you might want to do, is to include the targeting direct into your cast and not use /assist and /targetlasttarget.

If your normal Lightningbolt macro would be:

/assist 
[mod:ctrl,mod:shift,nomod:alt]ToonA;
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;
[mod:ctrl,nomod:alt,nomod:shift]ToonE
/cast [harm] Lightning Bolt
/targetlasttarget

you could get the same effect by using:

/cast
[mod:ctrl,mod:shift,nomod:alt,target=ToonA-target]
[mod:ctrl,mod:alt,nomod:shift,target=ToonA-target]
[mod:alt,mod:shift,nomod:ctrl,target=ToonA-target]
[mod:ctrl,mod:alt,mod:shift,target=ToonA-target]
[mod:ctrl,nomod:alt,nomod:shift,target=ToonA-target]
Lightning Bolt

If you want to do this, you should be aware that if you use a /castsequence with a reset=target this method doesn't work, cause your slaves never actualy target the mob they are casting on.

Shorten macrospace / simplify group changes

To shorten macros and to be able to switch in/out members in your team, without having to rewrite every spellmacro you can use the following method.

If your cast macro looks like

/assist

[mod:ctrl,mod:shift,nomod:alt]ToonA;

[mod:ctrl,mod:alt,nomod:shift]ToonB;

[mod:alt,mod:shift,nomod:ctrl]ToonC;

[mod:ctrl,mod:alt,mod:shift]ToonD;

[mod:ctrl,nomod:alt,nomod:shift]ToonE

/cast [harm] Lightning Bolt

/targetlasttarget

The blue-text would be the same in all your leaderbased macros, so what you want to do, is 'outsource' the part which defines whom the slave should assist.

This can be achieved by defining the '/assist ...'-part itself as a macro, binding it to an ActionButtonX and calling it via '/click ActionButtonX'

To do this for the above example:

1. create the macro

/assist
[mod:ctrl,mod:shift,nomod:alt]ToonA;
[mod:ctrl,mod:alt,nomod:shift]ToonB;
[mod:alt,mod:shift,nomod:ctrl]ToonC;
[mod:ctrl,mod:alt,mod:shift]ToonD;

2. drag the '/assist..'-macro to a bar you want to use (for example, if you want it to 'fire of' the 12th button on bar1, drag the macro to the corresponding button) 3. change all your 'cast/heal..' buttons, which depend on the assist to:

/click ActionButton12
/cast NameOfTheCast_or_theCastsequence  (/cast Lightning Bolt for the above example)
/targetlasttarget  (if wanted)

This has the advantage that it shortens the macrochars used in your dmg-makros drastical and that, if you change your group composition you only have to change one macro not all.

Formations

If you have a leaderless setup, you can do formations which are based on your (changing) leader.

This is a cool thing, that would not be possible in a focus/assist based approach.

Here is one quick example how you could do a line formation of your slaves (master doesn’t move):

Prerequisite:

The arrow-keys on each toon are bound to the 4 movement directions. Meaning left arrow (LEFT) is bound to ‘strafe left’.
bind the command ‘/walk’ to ‘p’ (for this example)

The basic line to do should look like:

   A
B C D E

(If ToonA is the leader. If not the leader swaps his place with ToonA.)

To make a line: two things are necessary to do with keypresses:

‘shift+f’ will only pressed once to tell the toons which toon has to walk.
The command syntax for this is: line.setWalk.XY.leaderZ,
which turns on walk on ToonX and ToonY when the leader is Z
‘f’ will make them walk left or right, depending on the leader

To set it up, do the following keybindings in keyclone:

ToonA:

‘f’ ---> line.ToonA.is.leader
‘LEFT’ ---> line.ToonB.is.leader
‘shift+LEFT’---> line.ToonC.is.leader
‘RIGHT’ ---> line.ToonD.is.leader
‘shift+RIGHT’---> line.ToonE.is.leader
‘shift+f’ ---> line.setWalk.CD.leader.A
‘alt+p’ ---> line.setWalk.AD.leader.C
‘ctrl+p’ ---> line.setWalk.AC.leader.D

ToonB:

‘LEFT’---> line.ToonA.is.leader
‘f’ ---> line.ToonB.is.leader
‘shift+LEFT’---> line.ToonC.is.leader
‘alt+LEFT’---> line.ToonD.is.leader
‘ctrl+LEFT’---> line.ToonE.is.leader
‘shift+f’ ---> line.setWalk.CD.leader.B

ToonC:

‘LEFT’---> line.ToonA.is.leader
‘shift+LEFT’---> line.ToonB.is.leader
‘f’ ---> line.ToonC.is.leader
‘alt+LEFT’---> line.ToonD.is.leader
‘ctrl+LEFT’---> line.ToonE.is.leader
‘shift+f’ ---> line.setWalk.AD.leader.C
‘p’ --> line.setWalk.CD.leader.A
‘shift+p’ --> line.setWalk.CD.leader.B
‘ctrl+p’ --> line.setWalk.AC.leader.D
‘alt+p’ --> line.setWalk.CD.leader.E

ToonD:

‘RIGHT’ ---> line.ToonA.is.leader
‘shift + RIGHT’---> line.ToonB.is.leader
‘alt + RIGHT’ ---> line.ToonC.is.leader
‘f’---> line.ToonD.is.leader
‘ctrl + RIGHT’ ---> line.ToonE.is.leader
‘shift+f’ ---> line.setWalk.AC.leader.D
‘p’ --> line.setWalk.CD.leader.A
‘shift+p’ --> line.setWalk.CD.leader.B
‘alt + p’ ---> line.setWalk.AD.leader.C
‘ctrl + p’ ---> line.setWalk.CD.leader.E

ToonE:

‘RIGHT’---> line.ToonA.is.leader
‘shift +RIGHT’ ---> line.ToonB.is.leader
‘alt + RIGHT’ ---> line.ToonC.is.leader
‘ctrl + RIGHT’ ---> line.ToonD.is.leader
‘f’ ---> line.ToonE.is.leader
‘shift+f’ ---> line.setWalk.CD.leader.E

Sidenote: the modifiers (shift,alt,ctrl) are used for LEFT and RIGHT, because keyclone doesn’t allow two different hotstrings for one key (which is absolutely logical, if you don’t differentiate between ingoing and outgoing hotstrings).

Variations

In this section variations of the original ftl-setup are described, which suited the special needs of some users better.

Leaderless, Focusless PVE orientated Setup

This setup is a variant of the ftl-system, which doesn't use the 'targetless'-option and is more suited for a pve-team.

Idea:

setup only 'follow' and 'assist' with keybindings like you would do with the ftl system.
use the target of the slaves as the dps-target