Fixing the melee IWT runaway problem

[Jabberie]

https://i.imgur.com/0bpYujB.png

this works for me

[VetSgtSchaeffer]

Can someone walk me through setting this up I am new to this and my eyes are going cross eyed trying to grasp this.

[JohnGabriel]

Can someone walk me through setting this up I am new to this and my eyes are going cross eyed trying to grasp this.

I am not sure how familiar you are with isBoxer, you'll need an ATG for melee.
http://isboxer.com/wiki/ATG

More information about IWT itself can be found here
http://isboxer.com/wiki/WoW:Interact_with_Target

After you have that, any of the above posts will help. Jabberie's post right above yours has an image with the changes you'd need. Also Wizeowl's post describes the steps.

The theory behind it is the movement key resets all movement so any existing IWT/CTM is cancelled, thats why the movement key needs to be before your IWT/CTM keybind.

[Bowells]

Correct me if I'm wrong but wouldn't this be against ToS? As it's 2 actions in 1 keypress? Most melees use IWT with their abilities so this would be using that ability and also the move forward command in 1 button press.

[Wizeowel]

Correct me if I'm wrong but wouldn't this be against ToS? As it's 2 actions in 1 keypress? Most melees use IWT with their abilities so this would be using that ability and also the move forward command in 1 button press.

The standard implementation of auto-assist, auto-interact abilities in ISBoxer is already more than 1 keypress: assist FTL macro, click-to-move macro, IWT button. Sending multiple keys at once is absolutely fine.

What's not fine is any kind of delay between the hardware action and the keypress message, e.g. that the keyup comes later than the keydown.

[Bowells]

They can all be put into a macro, all those actions can be put into one macro and function normally. But if you add the Up Command then it wouldn't work as a macro. I was always under the impression that as long as it can be put in a macro in-game and function then it's allowed and anything else is not.

[JohnGabriel]

I was always under the impression that as long as it can be put in a macro in-game and function then it's allowed and anything else is not.

That seems like it would be a good general rule of thumb, but there's never been any blue post that I am aware of saying anything like that. You probably think that because anything not on the GCD can all be placed in the same macro and perform all with one click. But two things on the GCD cannot be macroed to cast at the same time.

The movement keys are not on the GCD and can be used at the same time as other abilities without any problems at all. Running while shooting as an example. Nothing wrong with that at all.

[Bowells]

Yeah it's from this old blue post https://www.dual-boxing.com/attachme...3&d=1434701282

[aasi888]

The standard implementation of auto-assist, auto-interact abilities in ISBoxer is already more than 1 keypress: assist FTL macro, click-to-move macro, IWT button. Sending multiple keys at once is absolutely fine.

What's not fine is any kind of delay between the hardware action and the keypress message, e.g. that the keyup comes later than the keydown.

Wait, so 1 keypress = 1 action is no longer valid? I somehow doubt that (last time I asked about this it wasn't allowed :https://www.dual-boxing.com/threads/...221#post423221) .
I suppose you could separate those actions to 2 actions with out breaking the 1 click - 1 action rule:

#1 - Keydown

/assist
/console autoInteract 1

#2 - Keyup

IWT

About this:

You probably think that because anything not on the GCD can all be placed in the same macro and perform all with one click. But two things on the GCD cannot be macroed to cast at the same time.

The movement keys are not on the GCD and can be used at the same time as other abilities without any problems at all. Running while shooting as an example. Nothing wrong with that at all.

Ok, now I'm confused. Is there a blue-post that says this is fine?
1 click --> 1 action only applies for abilities with GCD?

[Moorea]

#1 - Keydown

/assist
/console autoInteract 1

#2 - Keyup

IWT

That would still not be something you can do in game (can’t bind different actions to keyup and keydown)