Fixing the melee IWT runaway problem

[aasi888]

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

Wow API has the keyup/keydown actions
https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyDown
https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyUp

It would seem like it is possible to do an addon that allows for separate actions for keydown and keyup.
This example only uses the keyUP:
https://wowwiki.fandom.com/wiki/Usin...for_your_addon

In fact Bindpad addon had both key up and down actions implemented back in version 2.2.0 in order to spam faster. Later the author of the mod decided to remove the feature, but the api calls seem to still exist in wow api.



EDIT: So based on this I'm assuming the 1 click -> 1 action rule applies regardless if the ability has GCD or not.

[Mercbeast]

Anything that mimics Blizzards own macro system is fine.

You can do stuff like

/follow target
/target X
/cast X

All in a single macro, and every single action executes off of one keypress. Your character will follow, target, and cast whatever spell.

This is also why spam macros work in WoW, and are fine. You can bind all your DPS abilities to one key, push the key, the key sends ALL of those abilities, but wow only processes 1 of them at a time.

[Moorea]

You can't do that in combat; IWT by design is supposed to be triggered by a single hw event and so is any kind of casting

Wow API has the keyup/keydown actions
https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyDown
https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyUp

It would seem like it is possible to do an addon that allows for separate actions for keydown and keyup.
This example only uses the keyUP:
https://wowwiki.fandom.com/wiki/Usin...for_your_addon

In fact Bindpad addon had both key up and down actions implemented back in version 2.2.0 in order to spam faster. Later the author of the mod decided to remove the feature, but the api calls seem to still exist in wow api.



EDIT: So based on this I'm assuming the 1 click -> 1 action rule applies regardless if the ability has GCD or not.

[Undeadlord]

There is a serious problem with this kind of IWT.

Yes the characters no longer run away if you spam the key and they are on melee range from the mob, however if you spam it when they are far away from the mob (chasing, switching, pulling) then the characters move in a stutter step manner or like they are frozen (freeze/move freeze/move etc.) This makes switching/chasing very very slow but also sometimes they don't turn but keep stutter stepping towards the side they look and they fall off bridges or ninja pull accidentally. This problem doesn't happen if you click the key only once when far away from the mob but this isn't as easy as it looks because you may have one of your characters on melee range who may need to cast abilities before your other characters arrive. It makes tanking very hard. It wasn't so bad until now because I played from healer pov and I didn't have to tank, so it was manageable although still annoying. As a tank I'm thinking to go back to following because I have to switch and chase all the time. I can't afford to wait for the other melees to arrive in order to spam the key, neither I can check if they move towards the wrong side so that I stop spamming.

Don't get me wrong, it's much much better than the original IWT or following and I grinded many levels easily with my warriors thanks to it but it still cause some headaches especially during the end-game where proper tanking is needed. Any idea how can I fix this problem when spamming the key and the characters are far away from the mob? I'm using the same setup as Jabberie.

Hopefully you understand the problem that I describe, I'm not a native English speaker so It's hard to describe it properly. Let's just call this problem "freezing movement problem".

[JohnGabriel]

Let's just call this problem "freezing movement problem".

Is this for Classic or Retail?

If this is in Retail, it almost sounds like you have a multi-step keybind, where step 1 is doing IWT and step two is doing something to interfere unless you wait long enough for it to reset.

The IWT/CTM used in Classic seems different. I don't multibox right now to test but solo the CTM part seems odd and this fix may not work for Classic.

[Undeadlord]

Is this for Classic or Retail?

If this is in Retail, it almost sounds like you have a multi-step keybind, where step 1 is doing IWT and step two is doing something to interfere unless you wait long enough for it to reset.

The IWT/CTM used in Classic seems different. I don't multibox right now to test but solo the CTM part seems odd and this fix may not work for Classic.

It is for classic. I also use a gnomesequencer macro in this keybind that includes startattack. I don't think that's the problem though.

The fix works fine when in melee range, it just cause some issues when far away but not so terrible ones. I don't think a melee 5box setup would be playable without it. Following is so bad and the standar iwt unplayable.

[Jabberie]

This is still working really good for when I swap to my healer and want my tank to stick on their target like glue.

[JohnGabriel]

Could this be from spell batching?

IWT is probably not in batching, but everything else in his GSE macro could be. If spell batching is 400ms and you spam your DPS key more than twice a second, your second IWT is connecting before your first spells do.

I have a melee WWWWPa team in Classic now and have not had any problems with it. But there are some differences, the "stutter step" in retail just resets your running animation but the "stutter step" in Classic you come to a complete stop and then start again. But they always run to the target, even if I have been stunned they continue IWT after the stun ends.

Seems to be working OK.

[lobbery]

I have a question regarding this fix.
I've done the following:
Added a "W" key press to the key (this is my move forward bind)
Added a "T" key press to the key (this is my IWT bind)
Added a "Q" key press to the key (this is my GSE damage rotation bind)

I set this up in a round robin with 3 stages: W followed by T followed by Q. Now, it absolutely works but my characters step forward all the time
wich means that they "push" the mob forward all the time until it actually makes it in behind my characters, i then have to spam the button pretty
fast to make them turn and start doing damage again. I was under the impression that the "W" key were supposed to happen so fast that the characters
dident really move, is this not the case or have i messed up something?

[Jabberie]

I have a question regarding this fix.
I've done the following:
Added a "W" key press to the key (this is my move forward bind)
Added a "T" key press to the key (this is my IWT bind)
Added a "Q" key press to the key (this is my GSE damage rotation bind)

I set this up in a round robin with 3 stages: W followed by T followed by Q. Now, it absolutely works but my characters step forward all the time
wich means that they "push" the mob forward all the time until it actually makes it in behind my characters, i then have to spam the button pretty
fast to make them turn and start doing damage again. I was under the impression that the "W" key were supposed to happen so fast that the characters
dident really move, is this not the case or have i messed up something?

it's shouldn't be the W that is moving them. It's probably the CTM started by the IWT

It could be how you have layed out your IWT, this is mine.