FTL-like setup for HKN

[olipcs]

Hi Fuzzy,

jeah, I know the FTL-Macros can be a little anoying, and that was the original reason, why I tried to 'simplfy' things as much as I could by:

1. Creating templates for HKN, which could be (if adapted once' simply be copy and pasted, so that setup in HKN is quite simple
2. Created the Jamba-FTL-Module, to create the correct FTL-Macros for Assist/Followbuttons, and to react to teamchanges. So that setup in WoW is quite simple.

I see the beauty in your system, and it was also one thing which came into my mind, but since its 1 keypress -> 2 keys, it was a no-go for me.

but to achieve what you want:

1) Not configure using lalt, ralt, lctrl etc.
2) Not have to create a macro for each spell cast but simply to drop it on the action bar and at the same time
3) Not needing to modify for solo play

Lets see where the problem for a normal FTL is:

1) Is not doable in an FTL, but with HKN-Templates and FTL-Jamba-Module you realy only need to configure it once, and since HKN can use ralt,rctrl,rshift, you can use lshift,lalt,lctrl for modifiers.

2) At the moment you need to create a macro for each spell, the only way to change this, that I can see, is to wirte an 'Actionbar-Addon' specific for an an FTL with an 'assist' bar, where you can drop spells on. This might be doable as a Jamba-Module, and if i find some time, I might have a look into it.

3) The normal FTL is designed to use it for soloplay and multiboxing, so no need to do something here.

I think the only way to do it with your style is, as you said with round robin and to spam the keys, but somehow for me this is not something I like.
Hm, maybe its time to get my coding-gloves on and look into a jamba-action bar mod for this...

[Fuzzyboy]

I think the only way to do it with your style is, as you said with round robin and to spam the keys, but somehow for me this is not something I like.
Hm, maybe its time to get my coding-gloves on and look into a jamba-action bar mod for this...

I don't like it either to be honest, but I still prefer it to the "real" FTL way. One way to make it a bit more convenient is to build in a functionality in HKN (/wave Freddie) which would allow a WoW-type reset for toggle, i.e:

<Toggle>
   <Key A>
<Toggle 100>
   <Key B>

Where the toggle would only reach the second statement if it was pressed within 100ms (or whatever specified) of the first keypress (i.e. button spam). Since there is no GCD to worry about with assist, this should work pretty much perfectly :-)

[Bettysue]

<hotkey F1>
        <Toggle>
              <SendLabel Stuff>
              <Key A>
              <Wait 500>
              <SetToggle 1 Hotkey F1>
        <Toggle>
              <SendLabel Stuff>
              <Key B>
              <Cancel>

That little bit of code will make the toggle reset after 500 milliseconds, but pressing it twice in the short amount of time will result in both being pressed and it going back to the first. Obviously you would have to adjust the time and super fast spamming may lead to overlaps. ---Overlap fixed with cancel

[Fuzzyboy]

<hotkey F1>
<SendLabel Stuff>
        <Toggle>
              <Key A>
              <Wait 500>
              <SetToggle 1 Hotkey F1>
        <Toggle>
              <Key B>

That little bit of code will make the toggle reset after 500 milliseconds, but pressing it twice in the short amount of time will result in both being pressed and it going back to the first. Obviously you would have to adjust the time and super fast spamming may lead to overlaps.

Yes, and more importantly it'll pause HKN while waiting, meaning I can't press other buttons (like movement keys) while the wait command is in progress, so unfortunately that isn't an option.

[Bettysue]

Yes, and more importantly it'll pause HKN while waiting, meaning I can't press other buttons (like movement keys) while the wait command is in progress, so unfortunately that isn't an option.

Bah movement didn't think about that...then again I play ele shaman and everyone knows turrets can't run :P The cancel sorta helped but you would still have to spam the movement key I think...there has to be a way.

[Freddie]

The new program will allow two hotkeys to execute simultaneously, but that doesn't help right now.

Cancel and DoToggles (new in a recent build) are the closest that HKN1 comes to concurrent hotkeys.

[Bettysue]

<Label Joe local SendWin WoW1>

<KeyList TTL 1-9>

<Template PFTL>
<hotkey %1%>
<Toggle>
<SendFocusWin>
<Key %2%>
<Wait 500>
<SetToggle 1 Hotkey %Trigger%>
<Toggle>
<SendFocusWin>
<Key %Trigger%>
<Cancel>
<EndTemplate>

<ApplyTemplate PFTL TTL B>

<MovementHotKey Left, Right, Up, Down>
<SendLabel Joe>
<Key %Trigger%>

Using the above code i am able to get the rapid alternating b1b1b1b2b2b2b2b3 etc, while moving without issue. It has a 500ms timeout and will always start with the assist key first after the timeout.
This should get you closer, if it doesn't work for you let me know what's happening, I'll try to work something out.
I just wrote the template to quickly make the number row work that way...

[Fuzzyboy]

<Label Joe local SendWin WoW1>

<KeyList TTL 1-9>

<Template PFTL>
<hotkey %1%>
<Toggle>
<SendFocusWin>
<Key %2%>
<Wait 500>
<SetToggle 1 Hotkey %Trigger%>
<Toggle>
<SendFocusWin>
<Key %Trigger%>
<Cancel>
<EndTemplate>

<ApplyTemplate PFTL TTL B>

<MovementHotKey Left, Right, Up, Down>
<SendLabel Joe>
<Key %Trigger%>

Using the above code i am able to get the rapid alternating b1b1b1b2b2b2b2b3 etc, while moving without issue. It has a 500ms timeout and will always start with the assist key first after the timeout.
This should get you closer, if it doesn't work for you let me know what's happening, I'll try to work something out.
I just wrote the template to quickly make the number row work that way...

I have my movement keys set up differently, so that wouldn't work. Also, I'm a bit averse to <wait> commands because of the lock-up and eula-stuff. It's not just the movement keys, it's also stuff like my /stopcasting macro etc. When spamming a <wait> command, nasty things will happen - believe me :-) I tend to keyspam really hard and I don't like my stuff to lock up.

Also, it's probably not a problem in practice, but I wan't to stay on the safe side of the EULA. Basically I see the "<wait>" method as a work-around with more disadvantages than advantages. If I'm going to play in the grey-area of the EULA, I might as well just have two keypresses in one hotkey (which is what /click macros do anyway), but I'm staying away from that for now :-)

[Bettysue]

Ya true probably a lot safer I'm kinda thinking the waits are a bad idea considering they are choosing for you which button to press rather than a predetermined order.

I agree with you though...really fast mashing of keys would cause some problems, just got my guy to stick while running forward, so it has flaws. Oh well was fun trying something new

I've always thought of /click in WoW as being more like templates in HKN than pressing 2 keys at once. Or am i failing to realize you can't have 2 castsequence lines in the same macro???

for example does the following work in 1 macro:

/castsequence reset=target Flame Shock,,,,,,,,,,,,,
/castsequence reset=target Lava Burst,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/cast Lightning Bolt

I thought the only reason for the /click was to get around the 255 char limitation...

[Fuzzyboy]

Yeah, for sure - and I appreciate the effort to help :-D