Neither will give you more keys to bind, but they will both reduce the numbers of keys you need by allowing you to build bigger macros {SuperDuperMacro} or reduce the macro space you need {Jamba's FTL}.
You can also look into using steps where the first time you press a key it does one thing, the second time it does another thing and so on.
http://www.dual-boxing.com/threads/4...l=1#post367932
Or you can use priority casting
http://www.dual-boxing.com/threads/4...l=1#post367931
These methods will allow you to "use" keys that you can't physically or easily use by making them steps to keys that you do press. As to exactly how to work them into an FTL setup I'd really only be guessing since right now I don't even have active accounts to set up and test with. But I'd think you'd be able to tack it on to the SendMasterAndSlave template like this
Code:
//----------------------------------------------------------------
// BEGIN: FTL Engine(Focusless Leaderless Targetless engine)
//----------------------------------------------------------------
//Added FTL Templates
//%1% : Master Key
// %2% : Slave Key
// %3% : Modifier
// %4% : SlavesToSend
<Template SendMasterAndSlave>
<SendFocusWin>
<Key %1%>
<Sendlabel %4%>
<Key %3% %2%>
// PRIORITY VERSION
<DoHotkey Hotkey RAlt F9>
<DoHotkey Hotkey LAlt F9>
<DoHotkey Hotkey RCtrl F9>
// OR
// TOGGLE VERSION
<DoRandomToggle Hotkey RAlt F9>
<DoRandomToggle Hotkey LAlt F9>
<DoRandomToggle Hotkey RCTRL F9>
<EndTemplate>
And then adding the toggles
Code:
// PRIORITY VERSION
//* TANK TOGGLES
<Hotkey RAlt F9>
<SendLabel w1>
<Key Shift 1>
<Key Shift 2>
<Key Shift 3>
<Key 2>
<Key Shift 4>
<Key F9>
<Key Shift 6>
//* HEALER TOGGLES
<Hotkey LAlt F9>
<SendLabel w2>
<Key Shift 6>
<Key 2>
<Key Shift 1>
//* ENHANCEMENT TOGGLES
<Hotkey RCtrl F9>
<SendLabel w3>
<Key 2>
<Key Shift 1>
<Key Shift 2>
<Key Shift 3>
<Key Shift 4>
// OR
// TOGGLE VERSION
//* TANK TOGGLES
<Hotkey RAlt F9>
<Toggle>
<SendLabel w1>
<Key Shift 1>
<Toggle>
<SendLabel w1>
<Key Shift 2>
<Toggle>
<SendLabel w1>
<Key Shift 3>
<Toggle>
<SendLabel w1>
<Key 2>
<Toggle>
<SendLabel w1>
<Key Shift 4>
<Toggle>
<SendLabel w1>
<Key F9>
<Toggle>
<SendLabel w1>
<Key Shift 6>
//* HEALER TOGGLES
<Hotkey LAlt F9>
<Toggle>
<SendLabel w2>
<Key Shift 6>
<Toggle>
<SendLabel w2>
<Key 2>
<Toggle>
<SendLabel w2>
<Key Shift 1>
//* ENHANCEMENT TOGGLES
<Hotkey RCtrl F9>
<Toggle>
<SendLabel w3>
<Key 2>
<Toggle>
<SendLabel w3>
<Key Shift 1>
<Toggle>
<SendLabel w3>
<Key Shift 2>
<Toggle>
<SendLabel w3>
<Key Shift 3>
<Toggle>
<SendLabel w3>
<Key Shift 4>
Unless I'm totally wrong, which is always a possibility since I'm coding blind, this should make it so that you press your normal key, the FTL goes through for the assist and also triggers the DPS toggles.
But the point I'm trying to get around to, in my fuzzy "first thing in the morning" logic, is that you can reduce the number of keys you physically need to press by making HotKeyNet do the work behind the scenes.
You can also further the reduce the number of keys taken up by making HotKeyNet use keys that aren't even on your keyboard. While the game itself needs to be able to recognize the keys it receives, you can use other keys to call different actions within HotKeyNet for the DoHotkey or DoRandomToggle part. This post lists various different keys HotKeyNet can use. There is also a keylist here. So instead of using up your F9 key in the above code, you can use something you won't ever be able to physically use, like "Junja" for actions that take place wholly within HotKeyNet.
Finally, you also have the option of defining your own Modifiers to be used wholly within HotKeyNet. Again, while WoW won't recognize it as a modifier so you can't use it in a macro as one, you can still make use of it to extend your "easy to use" keys. You can already see how that works with the mouse passing key you have
Code:
<UseKeyAsModifier Oem5>
<Hotkey Oem5 LButton, MButton, RButton, Button4, Button5>
<SendLabel w1,w2>
<ClickMouse %TriggerMainKey%>
In this case, Oem5 becomes a modifier that allows your mouse actions to take place on multiple windows, instantly giving you several more buttons to use.
Or when we look at the default Two-On-One script you'll see the keys all defined as ScrollLockOn ***
Code:
<Hotkey ScrollLockOn A-Z, 0-9, Plus, Minus, F1-F12 except W, A, S, D, Q, E>
<SendLabel w1, w2>
<Key %Trigger%>
They can also be defined as ScrollLockOff, CapsLockOn, CapsLockOff, NumLockOn, NumLockOff and any combination of those states, vastly increasing the number of useable keys based on modified states. So 1 becomes ScrollLockOn 1, ScrollLockOff 1, CapsLockOn 1, CapsLockOff 1, etc - each one being able to be used differently.
A simple example of this that I have is CapsLock. When Capslock is off, I'm broadcasting using all my variable keys {priority casting and the like}. But when Capslock is on, it's straight broadcasting. This is useful for when I want to broadcast an emote, like /dance. Since normally the keys D, A and E are listed as exceptions, they wouldn't get sent to slave windows. But if I design a Keylist using CapsLockOn, I can then "re-purpose" my standard keys so that they act differently in this Modified state.
It's also useful for times when you're forced to use a modified bar in game, like when you're in a vehicle. Normally my 2 key would call my toggles or priorities, so the game isn't assured to get a keypress of 2 as you see above. But if I turn CapsLockOn, it will disable the toggles and just send 2.
A more complicated use I employ is for my slave movement in combat. Since I use melee toons, I rely heavily on Interact with Target, which I trigger with Tab. I also rely on something called "stutter movement" which is simply sending <KeyDown W> and <KeyUp W> when I'm not sending the Interact with Target command {Key 2}, which sends a brief movement command that cancels the running off you sometimes see by over-spamming Interact with Target. A problem I came across was that the "Stutter movement" interfered with any other movement, such as trying to run out of whirlwinds and the like while still spamming my DPS key.
Rather than duplicating my DPS setup again on another key and trying to remember to use that key, I simply made an automatic state toggle by copying the code for my 2 key, deleting the KeyDown/KeyUp W and defining it as <Hotkey ScrollLockOn 2>. I then configured my Up and Down Arrow keys to turn ScrollLock On when I hold down the key and turn it off again when I release it, effectively changing the action of Key 2 without my having to use up a whole new key.
So there's a lot of different ways to get creative to stretch your effective keys without having to use up a ton of physical keys.
Reply With Quote
Originally Posted by bluelol
Connect With Us