Leaderless setup with HotKeyNet

Quote:

---

Originally Posted by 'olipcs',index.php?page=Thread&postID=138783#post1 38783

So, did some testing and here are the results:

Region-Switching

As Freddie suggested canceling the redraw before resizing/positioning and a better order of my commands results in a performance gain.
I optimized my script, so that the following is done if I want the Window of WoWX on my big main region (region1):
1. Resize and Reposition WoWX in region1, and give it the focus
2. Turn redraw off, for all other windows (without focusing them)
3. Resize and Reposition all windows that ar not WoWX (without focusing them)
4. Turn redraw on and update all windows that ar not WoWX (without focusing them)

Thie result of this order is, that the Window i want to play activ, which should be displayed in region1 is switched very fast (first), so you can move with the active toon leading, and after that the other 'slaves' are configured.

The result is, that it feels more like only a second, till you can play the active toon instead of the 2-3 seconds i mentioned before.

For the interrested here the hotkeynet code:

Code:

---

<Command ResizeAndPosition>
          <SendPC Local>
              <SendWin %1%>
                      <SetWinRedraw off>
                      <SetWinSize 1280 980>
                      <SetWinPos 0 0>
                      <SetWinRedraw on>
                      <UpdateWin>
              <SendWinM %2%><SetWinRedraw off>
              <SendWinM %3%><SetWinRedraw off>
              <SendWinM %4%><SetWinRedraw off>
              <SendWinM %5%><SetWinRedraw off>
                    <SetWinSize 640 512>
                    <SetWinPos 1920 512>
              <SendWinM %2%>
                    <SetWinSize 640 512>
                    <SetWinPos 1280 0>
              <SendWinM %3%>
                    <SetWinSize 640 512>
                    <SetWinPos 1280 512>
              <SendWinM %4%>
                    <SetWinSize 640 512>
                    <SetWinPos 1920 0>
                    <SetWinRedraw on>
                    <UpdateWin>
              <SendWinM %2%><SetWinRedraw on><UpdateWin>
              <SendWinM %3%><SetWinRedraw on><UpdateWin>
              <SendWinM %5%><SetWinRedraw on><UpdateWin>

<Hotkey F1><ResizeAndPosition WoW1 WoW2 WoW3 WoW4 WoW5>
<Hotkey F2><ResizeAndPosition WoW2 WoW1 WoW3 WoW4 WoW5>
<Hotkey F3><ResizeAndPosition WoW3 WoW2 WoW1 WoW4 WoW5>
<Hotkey F4><ResizeAndPosition WoW4 WoW2 WoW3 WoW1 WoW5>
<Hotkey F5><ResizeAndPosition WoW5 WoW2 WoW3 WoW4 WoW1>

---

---

Thats similar to what I was trying to do with 3 of my windows but I was trying to use If's so it would fullscreen the focus window and shrink the other 2.

Something like this:

Code:

---

<Hotkey x>
<If ActiveWinIs wow1><ResizeAndPosition WoW1 WoW2 WoW3 WoW4 WoW5>
<Else If ActiveWinIs wow2><ResizeAndPosition WoW2 WoW1 WoW3 WoW4 WoW5>
<Else If ActiveWinIs wow3><ResizeAndPosition WoW3 WoW2 WoW1 WoW4 WoW5>
<Else If ActiveWinIs wow4><ResizeAndPosition WoW4 WoW2 WoW3 WoW1 WoW5>
<Else If ActiveWinIs wow5><ResizeAndPosition WoW5 WoW2 WoW3 WoW4 WoW1>

---

Quote:

---

Originally Posted by David

Correct me if I`m wrong, but this setup is made to be able to use every one of your chars as a main right?

Because if that`s so, I think I did it with less work(script), haven't gone trough all your scripting yet so I`m not 100% sure. But the way I did it I can change to any char to set it as a main, just by one keyclick and I can still use the same follow and assist macro.

---

Please let me know if this is the case :) I'm waiting before updating any wiki pages since other people keep coming up with new and better ways of doing these things.

Ok, my brain hurts. I've been trying to follow what you all are saying and tossing around, but I cann't get it straight. Please, for those of us who don't know the first thing about what your throwing about, can you post or update the code that does this for us? I copied it and plunked it into my setup and nada. I even tried to figure out what went wrong, followed the logic path and stuff, but still nada.
Oh, thanx for figureing out this awsomn setup. I'm sure I'll love it if and when I get it working :D


EDIT: Ok I got it working, Sorta. it only works about 50% of the time though. I'm running 2 (atm, don't want to be trying to debug 4 or 5 yet) locks on the same machine. my first problem was the name of the windows. now...

/head explodes

Quote:

---

Originally Posted by 'Tanntyn',index.php?page=Thread&postID=139590#post 139590

Ok, my brain hurts. I've been trying to follow what you all are saying and tossing around, but I cann't get it straight. Please, for those of us who don't know the first thing about what your throwing about, can you post or update the code that does this for us? I copied it and plunked it into my setup and nada. I even tried to figure out what went wrong, followed the logic path and stuff, but still nada.
Oh, thanx for figureing out this awsomn setup. I'm sure I'll love it if and when I get it working :D


EDIT: Ok I got it working, Sorta. it only works about 50% of the time though. I'm running 2 (atm, don't want to be trying to debug 4 or 5 yet) locks on the same machine. my first problem was the name of the windows. now...

---

Hopefully two clients on same PC will be a bit easier. It should go something like this:

Code:

---

<command assist1>
        <SendPC Local>
                <SendwinM wow1>
                        <Key %1%>
                <SendWin wow2>
                        <Key ctrl shift %2%>

<command assist2>
        <SendPC local>
                <SendWinM wow1>
                        <Key ctrl alt %2%>
                <SendWinM wow2>
                        <Key %1%>

<Hotkey 1>
<If ActiveWinIs wow1> <Assist1 %trigger% t>
<Else If ActiveWinIs wow2> <Assist2 %trigger% t>

---

You would then need to put your normal skill on hotbar '1' and the corresponding macro on 't' on both clients.

For the macros you would want:

Code:

---

/assist [mod:ctrl,mod:shift,nomod:alt]Characternameforwow1;[mod:ctrl,mod:alt,nomod:shift]Characternameforwow2
/cast [harm] Lightning Bolt

---

My multi PC setup is what makes it look so complicated. When I get around to writing it all up correctly I will probably just use a single PC setup for all the examples.

Hi, did some more extensive testing today.

Modifiers

My goal with modifiers is, that i wanted to be able to create leaderless-hotstring like I suggested to Freedy here and revisioned here.
To cut it short, i wanted to be able to define not a single key as master- and slave-key, but a hole key-modifier combination.
To give an example, what is possibe :
Say your ModifierOrder, to identify a Toon, for TonnC is 'alt' + 'shift' .
I define 'shift + 2' as the master-key and 'ctrl + u' as the slave key.

What happens when I press 'shift +2' on ToonC is:
1. 'shift+2' is send to ToonC (the leader)
2. 'ctrl + alt + shift + u' is send to the slaves (ToonA,ToonB,ToonD,ToonE)

Why this is very usefull I will explain after I descriebed how it is done.

Basic Idea to make this possible is very simple:
- Instead of defining 1 command like 'assistX', which must have as parameter the master-key combination and the slave-key combination ..
- ...simply define 2 seperate command:
- one to assistX if you are the leader (assistXMaster), which only sends the master-key-combination to ToonX
- another to assistX if you are a slave (assistXSlave), which sends the slave-key-combination to all slvaes (all but ToonX)

This can be accomplished with HotKeyNet for example Toon3 with:

Code:

---

<command assist3Master>
        <SendPC Local>
                <SendWin WoW3>
                        <Key %all%>
<command assist3Slave>
        <SendPC Local>
                <SendWinM WoW1>
                        <Key alt shift %all%>
                <SendWinM WoW2>
                    <Key alt shift %all%>               
                <SendWinM WoW4>
                    <Key alt shift %all%>
                <SendWinM WoW5>
                      <Key alt shift %all%>

---

.. to make it work for all five, you have to add such a template for all 5 by changing the modifier-combination (here 'alt + shift) to the one of the corresponding Toon, and changing to which window the master and slave-keys are sent.

So, now i have defined all five <assistXMaster> and <assistXSlave>, how do i define a master-slvae-key-combination like mentioned above?
(Master-Key: 'shift + 2' / Slave-Key: 'ctrl + u')

like the following:

<Hotkey shift 2>
<If ActiveWinIs WoW1> <Assist1Master %trigger%><Assist1Slave ctrl u>
<Else If ActiveWinIs WoW2> <Assist2Master %trigger%><Assist2Slave ctrl u>
<Else If ActiveWinIs WoW3> <Assist3Master %trigger%><Assist3Slave ctrl u>
<Else If ActiveWinIs WoW4> <Assist4Master %trigger%><Assist4Slave ctrl u>
<Else If ActiveWinIs WoW5> <Assist5Master %trigger%><Assist5Slave ctrl u>

Yeah, quit 'simple' and jet so powerfull :)
So, the goal for modifiers are accomplished :thumbsup: .

Using modifiers directly in your /cast macro
or: Why the hassle, above?

One major problem/misunderstanding of the ftl-setup is that a macro, which should activate on '2', like:

Quote:

---

/cast [mod:alt,harm] Corruption; [harm] Shadowbolt

---

can normaly only be achived in a ftl setup, by seperatly define a hotkey for '2' and a hotkey for 'alt + 2' which lead to 2 different slavekeys.
For more information see: http://www.dual-boxing.com/wiki/inde...etup#Modifiers

This is only half of the truth, as it is possible to use the same slave-key as long as you are not using the modifier which is used in the macro (here: alt) as part of your modifier-order which defines your leading Toon.

Ok, in theory this is possible, but when i want to define a modifier-order for a 5-Toon-Team i have to use at leats 3 different modifiers.

You might ask: "So what are you telling me here? It is possible, but becasue i need 3 different modifiers for my order its inpractical! -So shut up, don't waste my time!"
You were right, if there are only 3 modifiers!
But I shortly realized, that there are indeed 6 (!) modifiers not only 3, if you differentiate between left + right shift,alt,ctrl :thumbsup:

So the basic idea:
Simply use ralt, rshift and rctrl to define the modifier-order and voila, lalt,lshift and lctrl can be used in your macros! jipi!

so instead of using:
‘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’

as your modifier combination, use:

‘rCtrl + rShift + key’ ---> ‘command.ToonA’
‘rCtrl + rAlt + key’ ---> ‘command.ToonB’
‘rAlt + rShift + key’---> ‘command.ToonC’
‘rCtrl + rAlt + rShift + key’ ---> ‘command.ToonD’
‘rCtrl + key’ ---> ‘command.ToonE’

and by doing so you can use a macro like the following on your slave key:

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

Horray :)

Wow, great thread, thanks for making me aware of this one.

I got a few questions though, as I understand it, you would have to have an alternative (hidden) macro for each button that you want to use.
Casting a lightning bolt on your main will hit the macro to assist whoever is your main and cast a lightning bolt at his target.

That's an awful lot of hidden macros to me. I'm used to (I started with ahk) hitting an assist button before casting the normal spell. Isn't it just easier to have an assist macro and call upon it for every button you use, this will leave you with only one hidden macro (or 2 if you want a follow one).

Something like what you suggested:

Code:

---

/assist
 [mod:rctrl,mod:rshift,nomod:ralt]ToonA;
 [mod:rctrl,mod:ralt,nomod:rshift]ToonB;
 [mod:ralt,mod:rshift,nomod:rctrl]ToonC;
 [mod:rctrl,mod:ralt,mod:rshift]ToonD;
 [mod:rctrl,nomod:ralt,nomod:rshift]ToonE

---

would be the 'assist macro' say you put this under T.

And then your hotkeynet file would look like this:

Code:

---

<Hotkey 1>
<Passthrough>
<If ActiveWinIs wow1>
  <SendLabel Alt1, Alt2, Alt3, Alt4>
        <Key %Trigger%><Key rctrl rshift T>
<Else If ActiveWinIs wow2>
  <SendLabel Main, Alt2, Alt3, Alt4>
        <Key %Trigger%><Key rctrl ralt T>
<Else If ActiveWinIs wow3>
  <SendLabel Main, Alt1, Alt3, Alt4>
        <Key %Trigger%><Key ralt rshift T>
<Else If ActiveWinIs wow4>
  <SendLabel Main, Alt1, Alt2, Alt4>
        <Key %Trigger%><Key rctrl ralt rshift T>
<Else If ActiveWinIs wow5>
  <SendLabel Main, Alt1, Alt2, Alt3>
        <Key %Trigger%><Key rctrl T>

---

Or maybe better would be to put an /assist toon1 under t, /assist toon2 under y, /assist toon3 under u etc.. you'd get this:

Code:

---

<Hotkey 1>
<Passthrough>
<If ActiveWinIs wow1>
  <SendLabel Alt1, Alt2, Alt3, Alt4>
        <Key %Trigger%><Key T>
<Else If ActiveWinIs wow2>
  <SendLabel Main, Alt2, Alt3, Alt4>
        <Key %Trigger%><Key Y>
<Else If ActiveWinIs wow3>
  <SendLabel Main, Alt1, Alt3, Alt4>
        <Key %Trigger%><Key U>
<Else If ActiveWinIs wow4>
  <SendLabel Main, Alt1, Alt2, Alt4>
        <Key %Trigger%><Key I>
<Else If ActiveWinIs wow5>
  <SendLabel Main, Alt1, Alt2, Alt3>
        <Key %Trigger%><Key O>

---

The last one will leave you open to use alt/shift/ctrl (one w/e side you want) as you please. But yea..it'll require 5 hidden macros (10 if you include follow).

Quote:

---

would be the 'assist macro' say you put this under T.

---

yes it would be. But you can't (or better shouldm't) use the way you did it, presented above.
Simple reason why:

Quote:

---

<Hotkey 1>
<Passthrough>
<If ActiveWinIs wow1>
<SendLabel Alt1, Alt2, Alt3, Alt4>
<Key %Trigger%><Key rctrl rshift T>

---

..this comes down to 1 userkeypressing resulting in 2 different client-keypresses, and this is seen as automation. So never ever do that!

What you can do instead, to simplify setup time is:
-use '/click ActionButton' in your macros instead of the hole '/asist [mod....]'-sequence and also the general setup uses different master and slave keys, this is not mandatory, you can use the same, so that you for every targetet spell only need one macro..

For me this comes down to round about 5-6 macros per toon, which is not so much :)

If you have any questions fell free to ask!
I think, Anemo (or perhaps I, if he doesn't want to) will in the future write the hole concept and variations up in the wiki, so take a look there (in some days).
Or if it helps, i could also send you my hkn-file, which you then can customize...

I'm beginning to wonder wether the hidden keys are even required. I had no experience with a leaderless setup before this so I'm learning a lot too but I gather the idea is so you can still use your main keys on any window. Something gives me a feeling this could be possible without using any hidden keys at all, I will have to look into it.

Is there a way to just include [nomod] into the macros for normal spell casts?

Anemo, you don't need to use 'hidden-keys' in an ftl at all, as long, as you make sure, that your macros on the (then only) one key, can handle, if the toon is the leading toon or a slave.

In fact, in the version of the ftl i'm using, i use the same key as master and slave key since 2 month...

and, yes [nomod] is the thing which makes it possible :)

Quote:

---

I got a few questions though, as I understand it, you would have to have an alternative (hidden) macro for each button that you want to use.
Casting a lightning bolt on your main will hit the macro to assist whoever is your main and cast a lightning bolt at his target.

---

Good description, basicly 'yes' this is how it works. (the 'true'-ftl from Deceased and Pocalypse)

Quote:

---

That's an awful lot of hidden macros to me. I'm used to (I started with ahk) hitting an assist button before casting the normal spell. Isn't it just easier to have an assist macro and call upon it for every button you use, this will leave you with only one hidden macro (or 2 if you want a follow one).

---

And again: Yes. If you are ok, with anouncing a targetchange by pressing an 'assist-button' and that the setup is not targetless, this is a very quick way to setup an leaderless sytem without using focus.If you do it this way, you only hab´ve to setup two keys in the ftl-way, one for follow one for assist.
It's quite funny you mentioned this miethod here, as its mainly the method i was using for the last two month and described here:
Focusless, targetless, 'leaderless' setup.

..let me say, it works perfectly, and if you running a setup where you want to be able to target different things with your main, as with your slave its also a simpler and better way to go..