Fixing the melee IWT runaway problem

[JohnGabriel]

Hello everyone.

I would like to start a dialog on the runaway melee toon issue when spamming Interact with Target (IWT) with Click to Move (CTM). Its most noticable if you send IWT every time with your DPS rotation, less noticable if you have a seperate keybind for IWT but it still happens. There is a very simple fix that solves this problem completely.

- Send a Move Forward keybind immediately before you send your IWT keybind.

I know you're thinking I'm joking, but that's it. The runaway toon problem is now completely solved.

The software (isBoxer, Hotkeynet, etc) sends keys so fast a single movement key will not move your character, only reset all existing movement. Then the next IWT works as if it was the only time pressed, no matter how many times you spam it.

It happens so quickly your toon will not be slowed down, will run just as fast as normal. Though if you watch the video closely you will notice the movement key causes the toons to run/skip because it resets the running animation everytime I press the DPS key.

Heres the video. Enjoy your now well behaved melee teams and never worry about runaway again.


https://youtu.be/Ms7uI2j13h4

Sorry for quality of video, haven't quite got the hang of pinnacle studio yet.

[Wubsie]

Fantastic. I've generally strated using a manual, separate IWT in most situations, but I do have an option built in to re-enable auto-IWT as well for when I'm feelings lazy so it's nice to have an improvement on that setup as well.

[mrdsp]

Love this - going to implement now, had loads more problems with this recently :D

[MadMilitia]

John you're a genius!

[valkry]

This is great, thank you!!

[tanknspanker]

this is.. what i needed.
Thank you JohnGabriel!
I'm glad that more boxers are still looking for improvements here and there!
keep up the good work!

[ebony]

This is so good tried back key years ago but was pointless did not work would stop dps and u keep backing up but this just works. maybe it was a GCD change who knows :S


nice find!

[Ellay]

oh, my god. This is amazing.

Quick question - does it hurt casting? Say your ret paladin wants to throw down that flash of light? Interrupt or smooth sailing?

[JohnGabriel]

oh, my god. This is amazing.

Quick question - does it hurt casting? Say your ret paladin wants to throw down that flash of light? Interrupt or smooth sailing?

I did not think to check this, my dps rotation does not have anything with a cast time. Gut feeling tells me it will be interrupted and melee will need to stop DPS to cast something.

I kindof see that as a problem easier to fix. For example if you have an Action Target Group for melee and you send IWT->melee you can have your flash heal keybind first remove them from the ATG before casting then return them after.

Thanks for the feedback. That's definitely more food for thought and something I have to look into.

[Jabberie]

I am pretty sure it will break cast. I'll be testing it shortly on paladins. will report back

[ebony]

It did not seem to on my cats wgen they came out to "heal"

[propagandalf]

I was using a mouse button for my IWT, but putting it in my DPS rotation sounds much better. I got it to work, but I'm not sure if it's correct.

Does this look right? TIA!https://www.dual-boxing.com/attachment.php?attachmentid=2062&stc=1

[ebony]

I was using a mouse button for my IWT, but putting it in my DPS rotation sounds much better. I got it to work, but I'm not sure if it's correct.

Does this look right? TIA!https://www.dual-boxing.com/attachment.php?attachmentid=2062&stc=1

How i did it just with up then w

[JohnGabriel]

I was using a mouse button for my IWT, but putting it in my DPS rotation sounds much better. I got it to work, but I'm not sure if it's correct.

Does this look right? TIA!

The interact with target standard in party keymap already has an assist. The auto-assist me line isn't doing anything.

Also sending W to all only works if you are all melee, you wont want to send to a ranged.

Edit: Might I suggest you go into the Interact with Target - Standard in the Party keymap and copy all the actions and paste them into your DPS key and delete the assist step you don't want.

[propagandalf]

Thanks for the feedback! I updated it, per your suggestion (I hope :D).
https://www.dual-boxing.com/attachment.php?attachmentid=2063&stc=1

[JohnGabriel]

Thanks for the feedback! I updated it, per your suggestion (I hope :D).


Something that might cause you problems is you're sending "click to move on" to "all other" and sending IWT to "all". So the current toon wont have CTM turned on.

[propagandalf]

Thanks again!

[mrdsp]

Thanks for the feedback! I updated it, per your suggestion (I hope :D).
https://www.dual-boxing.com/attachment.php?attachmentid=2063&stc=1

Thanks for the pic - will try with mine.

I had a go but it caused my DK's to just run one step then stand still.

[JohnGabriel]

Thanks for the pic - will try with mine.

I had a go but it caused my DK's to just run one step then stand still.

Sounds like you are sending the movement keybind after IWT instead of before. IWT is what makes your toon run and the movement key is what makes it stop.

[Dreadone]

Hi John,

im not using the Isboxer Pro configuration yet. How could i fix the problem with the standard version? Any idea/workaround?

Thank you for your time :)

[Toned]

I'll have to mess with this, I've turned off IWT and I play all groups with auto follow / arrow movements for positioning, and formations for spreading out.

[Lax]

Hi John,

im not using the Isboxer Pro configuration yet. How could i fix the problem with the standard version? Any idea/workaround?

Thank you for your time :)
It's basically an alternative implementation of the "Face Target" version of IWT, which sends "Move Backward" after pressing IWT -- all you should have to do is adjust the auto-interact (assuming that is enabled on your DPS buttons) to also press a movement key.

Note: If you're pressing it manually and not building this into your DPS keys, you can set a Hotkey for "Face Toward Target" in "ISB42 - Base Hotkeys"

Here's the default version of "Auto-Interact with Target - Standard" in "ISB42 - Party" which would be built into your DPS keys. (e.g. by ticking the box at the end of the Quick Setup Wizard)
https://www.dual-boxing.com/attachment.php?attachmentid=2066&stc=1

And here's an adjusted version...
https://www.dual-boxing.com/attachment.php?attachmentid=2067&stc=1
… and the changes:

I changed the Targets for the Actions to use the Melee ATG instead of all. This is so that teams with casters are not affected. You can leave those to all/all other if you want.

If you want use the Melee ATG, you do may have to create it under Action Target Groups, and make sure to add your Melee characters to it


I also went into "Interact with Target - Face Target" right above it, into Step 1, and Copied the <Move Backward> Action, and pasted it in (and changed the Target to match the changes). You can do that as well.

You can also manually add the action -- right click Actions and select "Variable Keystroke Action", pick the "Move Backward" (or any direction really, it's not going to actually move because this is instant) and set the Target. Just be sure that under "Variable Keystrokes" in the top left pane, your "Move Backward" is set to the right button for your in-game key bindings (while you're there, check the others ;) ).
… you can also use a regular old Keystroke Action and just fill in your movement key



That's how to modify the standard ISBoxer 42 setup, with or without Pro. Pro setups can of course choose to use this Auto-Interact with Target feature the same way as the standard "ISB42 - Combat Broadcast" key map.

Enjoy :)

p.s. here's the modified Mapped Key, you can just paste this in to ISB42 - Party.


<?xml version="1.0" encoding="utf-8"?>
<Box xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ObjectType>ISBoxer_Toolkit.Configs.KeyMaps.MappedKey</ObjectType>
<SerializedObject>&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;MappedKey xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
&lt;Name&gt;Auto-Interact with Target - Standard&lt;/Name&gt;
&lt;Description&gt;This is the same as Interact with Target - Standard with the exception of no auto-assist, and Click to Move is left enabled in WoW&lt;/Description&gt;
&lt;Hold /&gt;
&lt;UseFTLModifiers /&gt;
&lt;ResetTimer&gt;1&lt;/ResetTimer&gt;
&lt;ResetType&gt;FromFirstPress&lt;/ResetType&gt;
&lt;Mode&gt;OnRelease&lt;/Mode&gt;
&lt;Steps&gt;
&lt;Step&gt;
&lt;Actions&gt;
&lt;MappedKeyAction xsi:type="MappedKeyExecuteAction"&gt;
&lt;Target&gt;other Melee&lt;/Target&gt;
&lt;KeyMapString&gt;ISB42 - WoW&lt;/KeyMapString&gt;
&lt;MappedKeyString&gt;Click to Move On&lt;/MappedKeyString&gt;
&lt;/MappedKeyAction&gt;
&lt;MappedKeyAction xsi:type="VariableKeystrokeAction"&gt;
&lt;Target&gt;Melee&lt;/Target&gt;
&lt;Name&gt;Interact with Target&lt;/Name&gt;
&lt;/MappedKeyAction&gt;
&lt;MappedKeyAction xsi:type="VariableKeystrokeAction"&gt;
&lt;Target&gt;other Melee&lt;/Target&gt;
&lt;Name&gt;Move Backward&lt;/Name&gt;
&lt;/MappedKeyAction&gt;
&lt;/Actions&gt;
&lt;/Step&gt;
&lt;/Steps&gt;
&lt;/MappedKey&gt;</SerializedObject>
</Box>


Select everything in the "Code" box
Copy it (e.g. right click, Copy. or Ctrl+C)
In ISBoxer, select "ISB42 - Party" in the top left under Key maps, then right click "Mapped Keys" in the bottom left
Select "Paste Mapped Key from Clipboard"
It says "An existing Mapped Key . . .", tell it to "Replace the existing item" and click OK.

[JohnGabriel]

Though you'll want the movement key before IWT instead of after. You want the movement key to clear any previous IWT not the last one.

[Toned]

Though you'll want the movement key before IWT instead of after. You want the movement key to clear any previous IWT not the last one.

Have you or anyone solved the random disconnects you get from using IWT if you are spamming too fast? :)

[Wizeowel]

Though you'll want the movement key before IWT instead of after. You want the movement key to clear any previous IWT not the last one.

John sorry for the necro, but I wanted to highlight what a wonderful solution this is. Many times I thought about removing the monk from my party because she does only half dps, pulls extra mobs, falls into chasms. I wish I had seen this post a month ago when I started.

I duplicated "Interact with Target - Standard", named it "IWT - Melee Fix"; added keystroke action 'W' sent to window: melee - others. Moved it up to 2ndaction between the click-to-move and the IWT. Then in my character set I changed virtual key "Auto Interact with Target - Active Method" (which is what I'm using in my combat key maps) and redefined it to "IWT - Melee Fix".


It's basically an alternative implementation of the "Face Target" version of IWT, which sends "Move Backward" after pressing IWT -- all you should have to do is adjust the auto-interact (assuming that is enabled on your DPS buttons) to also press a movement key.

Hi Lax, I would like to request you incorporate this in the Pro template with <Move Forward> before the IWT keystroke instead of <Move Backward> after the IWT. You could make it a separate IWT option, but to be honest it works so well that you could add it to "Interact with Target - Standard". As long as the user doesn't add any ranged into the melee ATG then it's relatively foolproof.

[MiRai]

It's basically an alternative implementation of the "Face Target" version of IWT, which sends "Move Backward" after pressing IWT -- all you should have to do is adjust the auto-interact (assuming that is enabled on your DPS buttons) to also press a movement key.

Hi Lax, I would like to request you incorporate this in the Pro template with <Move Forward> before the IWT keystroke instead of <Move Backward> after the IWT. You could make it a separate IWT option, but to be honest it works so well that you could add it to "Interact with Target - Standard". As long as the user doesn't add any ranged into the melee ATG then it's relatively foolproof.
The problem is that ISBoxer works with many different games, and the Interact command is not exclusive to World of Warcraft, and so, for those other games, should the default setup also be sending the <Move Forward> key along with Interact? Probably not, since the information in this thread solves an issue that is only an issue in World of Warcraft. In addition, you point out another potential problem of adding it in by default: the fact that it is only used for melee, and would continuously interrupt ranged spell casters. If someone is playing a mixed-class team, they will still have to alter the Target of the Mapped Key, as well as create/adjust an ATG that they're not familiar with. Either way, it's additional work for the end user, which leads me to my next point.

ISBoxer has to be somewhat generic in its setup because of all of the different users that use it and games that it's used with, and, at some point, the user is expected to (eventually) learn how to configure some stuff on their own, and then figure out how to implement these things into their own, personal profile, since the Wizards can only take you so far (even if they were super ultra advanced). Personally, I think it's best if ISBoxer sticks with a more basic setup, and then users learn how to actually use the features of the program, and build upon that default setup.

Finally, the "Face Target" Mapped Key is meant to be used on press, hold, and release of a separate key, and is not meant to be integrated into a standard rotation because it has a two-step, interactive requirement to use properly—moving backward is executed upon release. At a quick glance, the "Face Target" Mapped Key almost looks as if it won't work properly, since it's a two-step process calling one step of a second two-step process, which leads to de-sync. Nevermind on that last point, the MK it's calling resets itself after 1 second.

[JohnGabriel]

It will probably need updated next expansion.

Indeed this feels wonderful and I am glad there is finally something to stop that wicky wacky runaway crap, its still just a bandaide covering an ever changing bug in the WoW client.

I tried years ago to solve this, ebony mentioned the same, I bet a lot of people tried. This just wouldn't work back then, and never know if its going to work next expansion.

[Wizeowel]

John, I hope it does not break in the next expansion. Enjoy today, worry about tomorrow later :)


The problem is that ISBoxer works with many different games, and the Interact command is not exclusive to World of Warcraft, and so, for those other games, should the default setup also be sending the <Move Forward> key along with Interact? Probably not, since the information in this thread solves an issue that is only an issue in World of Warcraft. In addition, you point out another potential problem of adding it in by default: the fact that it is only used for melee, and would continuously interrupt ranged spell casters. If someone is playing a mixed-class team, they will still have to alter the Target of the Mapped Key, as well as create/adjust an ATG that they're not familiar with. Either way, it's additional work for the end user, which leads me to my next point.

ISBoxer has to be somewhat generic in its setup because of all of the different users that use it and games that it's used with, and, at some point, the user is expected to (eventually) learn how to configure some stuff on their own, and then figure out how to implement these things into their own, personal profile, since the Wizards can only take you so far (even if they were super ultra advanced). Personally, I think it's best if ISBoxer sticks with a more basic setup, and then users learn how to actually use the features of the program, and build upon that default setup.

Fair enough about the generic implementation of the Pro system. I forgot that Melee ATG isn't included by default in the Pro template anyway.

I must point out that as a new user, who has made an effort to watch and learn from many of your excellent and informative videos, I've searched a lot, and experimented with almost all the ISBoxer features over the last month. I understand I don't have your years of experience, and I don't expect to have things handed to me on a plate. In fact the complexity of ISBoxer has become a kind of meta game. I'm almost disinterested in levelling because it's more compelling to create a new menu or keymap to solve challenges of rotations and healing. I've made plenty of dumb mistakes so far, and hopefully learned from them. But this was something I could not see a way to solve and only happened on John's video by chance.

Perhaps then this solution could be mentioned in the wiki page http://isboxer.com/wiki/WoW:Interact_with_Target ?

[JohnGabriel]

[..snip..] In fact the complexity of ISBoxer has become a kind of meta game. I'm almost disinterested in levelling because it's more compelling to create a new menu or keymap to solve challenges of rotations and healing.[..snip..]

Oh yeah, I will often spend all night playing IsBoxer, its fun.

[briarknit]

So I tried this with the standard configuration https://www.dual-boxing.com/attachment.php?attachmentid=2133&stc=1

But if I press this more than once per second, it causes my team to stand still even though my "move backwards" is before IWT

[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 (https://www.dual-boxing.com/threads/54562-Fixing-the-melee-IWT-runaway-problem?p=418097&viewfull=1#post418097) right above yours has an image with the changes you'd need. Also Wizeowl's post (https://www.dual-boxing.com/threads/54562-Fixing-the-melee-IWT-runaway-problem?p=417490&viewfull=1#post417490) 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/attachment.php?attachmentid=1493&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/55936-Is-delay-allowed?p=423221#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)

[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/Using_bindings.xml_to_create_key_bindings_for_your _addon

In fact Bindpad addon had both key up and down actions implemented back in version 2.2.0 (https://www.curseforge.com/wow/addons/bind-pad/files/398805) 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/Using_bindings.xml_to_create_key_bindings_for_your _addon

In fact Bindpad addon had both key up and down actions implemented back in version 2.2.0 (https://www.curseforge.com/wow/addons/bind-pad/files/398805) 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.
https://i.imgur.com/5eCFm9J.png

[lobbery]

Iam not using ISboxer right now so it shouldent be a isboxer specifik problem sir

[Wizeowel]

Edit: sorry clicked post before reading if there were replies, this obviously doesn't apply if you aren't using ISBoxer


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?

If your toons are moving at all, then somewhere in your keybind you maybe have "Hold any Keystroke Actions while Hotkey is held" set to ON somewhere in your mapped keys. Check the whole chain: DPS mapped key, auto-assist me mapped key and auto-IWT mapped key. See your character set virtual mapped keys in case any of these have been redefined.

Not sure why you have chosen to use round robin. The trick works best if you send W and then immediately IWT as 2 keystroke actions within the same step, usually preceded by the click-to-move on macro.

You can also check in the Innerspace console which keys are being pressed. It should be something like this:
on key pressed:
Shift-Backspace (assist me)
Shift-Alt-N (click-to-move on)
W
T
on key released:
Q

[lobbery]

Im using a software Called Lidc togheter with GSE. I dont see How my bind could have what your refering to unless its an option in GSE somewhere. Im very light on addons because Im abit OCD and i like control as much as possible. Basically the software option i found most suited was the round Robin so that i could press more then 1 actual button on 1 bind. I Will look into if There is a better option avalible. With that Said the round Robin sends W and T directy as ingame wow binds wich in my world should be that any errors are related to Q wich is a GSE macro with /assist /startattack and a few /cast random spell in a priority sequence
also, thanks a bunch for replys

[JohnGabriel]

I set this up in a round robin with 3 stages: W followed by T followed by Q.

The above I have trouble understanding.

As Wiseowl mentioned, you will need to send W and T together. Send a WTQ or WT then a Q is ok, but not a W then T then Q

[lobbery]

Any idea How i could go about doing that? I dident find anything apart from round Robin in lidc software.

[JohnGabriel]

Any idea How i could go about doing that? I dident find anything apart from round Robin in lidc software.

I have browsed the LIDC website and it seems to have advanced features, so should be able to use this work around. They don't have a forum or discord but there is an email address. I would first verify its not GSE causing you problems then contact them.

According to MiRai here (https://www.dual-boxing.com/threads/55668-Anyone-try-Lidc) the software is like an updated Keyclone so someone familiar with Keyclone could be able to help.

[lobbery]

I have contacted and currently waiting. I played some this Morning and recorded a vod, i felt it would be easier to show then to explain. The vod can be found on twitch, i have the same name There. Dont Wanna link anything incase There are rules against promotions or sorts. I suck and Im not a big streamer so hope its ok otherwice Ill try to upload it somewhere.

now since i last posted i have learned to make a macro bind with my mouse and gse. This made it better but not perfect. [Redacted]

Removed portion of post which is against the rules of this forum.
-MiRai

[lobbery]

This post is like my new home now. After alot of trial and error i have finally figured this out and Im very happy to say its working flawlessly with my 4 warriors. Next step for me is creating attackgroups and implementing this for a mixed team. Since this is standard ”all others” and i drive from my shaman in my 4 warrior team i had sort of a free Ride when i learned to implement the move forward step to iwt.

now for my mixed team i want auto iwt like i setup in the wizard for my dps key but the same key also has dps for my 2 casters, the workaround for this is attack groups right? Since i dont want move forward step on the mage for example, tbh i dont want auto iwt either since it starts wand if Im not mistaking. Can anyone shed some light please, i tryed briefly but Im doing something wrong.

Am i supposed to setup my own iwt key without auto and distribute to a caster attackgroup Perhaps?

[JohnGabriel]

attack groups right?

They are called Action Target Groups (ATG) in IsBoxer. You will need to set up an ATG for your melee and only send IWT to melee. Try reading the posts further above for more info.
https://www.dual-boxing.com/threads/54562-Fixing-the-melee-IWT-runaway-problem?p=425253&viewfull=1#post425253

[Cryonic]

This is what I tried:

https://www.dual-boxing.com/attachment.php?attachmentid=2364&stc=1

My other melee chars just stand still and do nut run up to the target (yes, click to move is active). What am I doing wrong?

[JohnGabriel]

This is what I tried:

My other melee chars just stand still and do nut run up to the target (yes, click to move is active). What am I doing wrong?

That should be working. I would have sent the W and IWT to 'other melee' but should still be working as is.

I notice you created a new 'melee IWT' keymap, may be an issue in there.

Did you have IWT working prior to trying this? Making sure you have the keybind for it set in game.

[Cryonic]

That should be working. I would have sent the W and IWT to 'other melee' but should still be working as is.

I notice you created a new 'melee IWT' keymap, may be an issue in there.

Did you have IWT working prior to trying this? Making sure you have the keybind for it set in game.

Yes it was working before (with the annoying toons running away sometimes) but they always walked up to the target. I copied the keymap in use and made the alternation in the picture.

[Wizeowel]

@Cryonic

You probably need to use the console feature of Innerspace to see exactly which keys are being sent to your toons https://isboxer.com/wiki/ISBoxer_Debugging_Console

But from your screenshot, I wonder 3 things. First, as John said there could be an issue in your Melee IWT, could you show it? Second, I would suggest putting the 'W' keypress inside that Melee IWT mapped key. Third, I would split your action to be 'press and release' with two steps: 1) assist and IWT; 2) action key like '1'.

[Cryonic]

This is what I got in console on my slaves: (On 1 keypress) (BACKSTEG = BACKSPACE)

Button: from keystroke@is2: nomodifiers 161+BACKSTEG
Button: from keystroke@is2: nomodifiers 1
Button: from keystroke@is2: nomodifiers W
Button: from keystroke@is2: nomodifiers 161+BACKSTEG
Button: from keystroke@is2: nomodifiers 1

This is what I get from an unmodified FTL DPS Keys:

Button: from keystroke@is1: nomodifiers 160+BACKSTEG
Button: from keystroke@is1: nomodifiers 1

Melee IWT is bound to: G
FTL Assist me is bound to: ALT+BACKSTEG

EDIT:

After changing to this:
https://www.dual-boxing.com/attachment.php?attachmentid=2365&stc=1
everything seems to work.

[Maex]

working! you are my hero TE :-* thanks alot

[Ellay]

Made a guide for this on how I do it. Hope it helps!

th-jW9aYdw8

[Lyonheart]

Thanks Ellay! I cant wait to see your future 5 pal mythic+ runs. I have a very basic/lazy set up for my team and they feel strong. With better optimization, I think 5 prot pals will do way better than how I do it.

Anyways, thanks for your videos! So much inspiration!