Printable View
Following Ualaa's closed thread about programing IWT for melee characters. He showed us how to activate IWT on the button press and turn off on the button lift. At the same time can you also program it for Casters to correct facing?
Button press: activate IWT
Button lift: press arrow back
would this work?
(sorry if it was posted earlier)
I have that set up on mine. it IWT of the focus character, then on key up it will hit the down arrow. It has tested fine. The longer i hold the key in the closer they run to the mob before stopping.
This seems borderline to me. Everyone would agree that pushing one button and having your broadcast program push two buttons in sequence would be unacceptable. The solution proposed here seems to be in a grey area between the two.
Ya, I beat that horse to death in previous threads and if I remember right the concensus was it is ok.
How do you get it to IWT of the focustarget?Quote:
Originally Posted by Slimjim19
I use FLT thru innerspace.
Blizzard, through their API, has determined what is ok for an addon to do and what is not.
If key state actions (up or down) are fine for addons (see Keyboard API), I don't have a problem using them.
That said, if you do have a problem...
Keep the mapped key, as two steps.
But set is to execute only on key release.
Press (and release) once to initiate the IWT.
Press (and release) a second time, to end the movement.
The speed between first and second press can be as quick as you like, there are no GCD restrictions.
Does anyone have a link to how to set that up properly? I can't seem to find it via the wonderful Search function :(
It is one of the last examples in my guide.
Either the last or the second from last.
In the same post as the Eclipse toggle mapped key.
I tried IWT for fun on a pally team, and set it up in two steps in ISboxer, with the box ticked in ISBoxer to both register push and release.
Step 1: IWT
Step 2: Attack
I just spam that one button for melee attack.
the disadvantage for me with this setup is, I don't want my toons to keep running about in some stationary fights, so I might have to key in a "normal" attack button without IWT so my toons will stand still while attacking.
Anyway, I haven't played the Pallys much, just wanted to tryout the concept.
Here's some good news for you.Quote:
the disadvantage for me with this setup is, I don't want my toons to keep running about in some stationary fights, so I might have to key in a "normal" attack button without IWT so my toons will stand still while attacking.
If you use a Do Mapped Key Action for the IWT (as in you can make a Mapped Key with no Hotkey that does what you have set up in Step 1, then replace Step 1 with the Do Mapped Key Action), then you can set up a Toggle key. The toggle key would use a Mapped Key State Action to change the state of the new IWT Mapped Key (the one used by the Do Mapped Key Action).
If you do it right, you can also make this a per-window toggle if you like (as in, stop one window from interacting -- say you don't want your healer to move in some fights but do in others). That would depend entirely on the Target of the stuff in the new IWT Mapped Key -- recommend current window aka "self" -- and the Target of the Do Mapped Key Action -- e.g. all other. This way the Target of the Do Mapped Key Action says who actually does it, AND you have the option of disabling it on the receiving end by disabling the IWT Mapped Key on the windows you do not want it on (e.g. Mapped Key State Action with Target set to the healer could make your healer stop or start doing the IWT part)
Hope that made sense to you, it might have been hard to follow. I've been trying to drive this home a bit on the isboxer.com forums, and it'll probably end up in some sort of Tips and Tricks guide :)
I've been using a two step toggle.
0 = off
1 = on
/console AutoInteract 0
/console AutoInteract 1
I like having IWT built into the default DPS.
But when you do, you need a method to disable it.
We cannot disable the wow keybinding.
But we can easily disable the CTM, via the console command.
Or alternatively, through 'Mapped Key State Actions', choose to push or not push the IWT keybind.