[WoW] Converting from Keybinds > Game to Named Macro Actions

[Ualaa]

I only attempted to convert one attack sequence, but it's not working as I would like.
And unfortunately, I don't see what I've done wrong...

Character Set: Silver
DPS 1 (spam key).

With my keybind approach: http://www.privatepaste.com/2bc4d7d868
I spam the key: 1.

Step 1:
FTL Assist, so they're on my target.
IWT to the melee toons only.
1 Keybind to Kisses
Mind Freeze rotation to the DK's
Howling Blast keybind to the DK's

Step 2:
2 Keybind to Kisses
Howling Blast keybind to DK's
Frost Strike keybind to DK's
Death Coil keybind to DK's
Necrotic Strike keybind to DK's


With the Named Macro Library approach: http://www.privatepaste.com/f64051b327

I spam the key: 1

The macros for Kisses works perfectly.
Scroll Up, sets focus; Scroll Down clears focus.
With focus, she spams the first Named Macro on step 1, and the second named macro on step 2.

The DK's however... aren't playing nice.
Only Huggles is receiving the IWT commands.
And none of them are doing the FTL Assist, of the active window.

If I push "F", which is my key to manually FTL Assist, that works correctly and they attack the correct target.
But only Huggles will IWT that target.

If I push the "2" key, which is still keybinds (for the Obliterate sequence), they IWT and Assist correctly.






As far as I can tell, the only changes were...
Anytime there was a keybind to Warcraft, that has been changed to a Named Macro Action.

Any assistance would be greatly appreciated.

[Alge]

I've had a quick look at your configuration and nothing is leaping out at me as the definite cause of the issues you are describing.

A couple of things to try:

- for your DPS 1 Mapped Key in the Silver Key Map, try it with "Hold any Keystroke Actions while Hotkey is held" set to "Off".
- when you say "Only Huggles is receiving the IWT commands." have you confirmed this by using the Debug Console? Normally when faced with a similar non-working Mapped Key I will go through and try and determine whether the issue is that the correct keystrokes are not being sent by ISBoxer or that the correct keystrokes are being sent but are not being acted on by that instance of WoW. I'd also probably remove all the Actions except Assist and IWT from Step 1 just for testing purposes until those are working.

I'll try and have another look later. Your configuration has a lot in it and it is hard to take it all in in one go

[Ualaa]

I'll try it with the Keystroke Actions set to Off.

I did not check the Debug Console at all.
It's just when the mapped key sends a keybind to warcraft it works.
But when the mapped key does a named macro action (where the macro is identical to the one in warcraft), it's not working as I'd like.

Namely..
Only Huggles will IWT; not sure if the others are receiving the command, or have a conflicting bind.
None of them are acting on the FTL Assist Me.

When I made the named macro actions...
The macros themselves needed a keybinding.
So I used Ctrl Alt A, Ctrl Alt B, Ctrl Alt C, etc... but omitted Ctrl Alt I, because my IWT is Ctrl I and I didn't want any possible conflicts.
Not sure if the keybind that the toolkit needs for a macro would conflict with FTL modifiers; I would assume not, but am not really sure.





In a recent IS Boxer update, some of my DK's are switching from the first action bar to the second.
Not really sure what is causing the switch.
So I figured if I were to use the named macro actions, it would all be internal and effectively not matter which action bar the toons were on.

Plus, its a lot easier to backup just the ToolkitProfile, rather than that plus my entire WTF folder.
I've been thinking of moving as much of the configuration into IS Boxer as possible.. for a while now.

[Alge]

I did not check the Debug Console at all.
It's just when the mapped key sends a keybind to warcraft it works.
But when the mapped key does a named macro action (where the macro is identical to the one in warcraft), it's not working as I'd like.

Namely..
Only Huggles will IWT; not sure if the others are receiving the command, or have a conflicting bind.
None of them are acting on the FTL Assist Me.

The debug console is the best way to find out what is actually happening.

When I made the named macro actions...
The macros themselves needed a keybinding.
So I used Ctrl Alt A, Ctrl Alt B, Ctrl Alt C, etc... but omitted Ctrl Alt I, because my IWT is Ctrl I and I didn't want any possible conflicts.
Not sure if the keybind that the toolkit needs for a macro would conflict with FTL modifiers; I would assume not, but am not really sure.

I use the same key combinations for my named macros. ISBoxer will also warn you if there is a conflict.

In a recent IS Boxer update, some of my DK's are switching from the first action bar to the second.
Not really sure what is causing the switch.

This is normally due to having Use FTL Modifiers checked when it shouldn't be.

So I figured if I were to use the named macro actions, it would all be internal and effectively not matter which action bar the toons were on.
Plus, its a lot easier to backup just the ToolkitProfile, rather than that plus my entire WTF folder.
I've been thinking of moving as much of the configuration into IS Boxer as possible.. for a while now.

Yep, much easier to maintain once it is working.

[Ualaa]

Did some troubleshooting with Mosg, in vent this morning.

Changing the 'Key Combination' for each of the Named Macro actions, from:
- Ctrl + Shift + Letter

To:
- Num 1, Num 2, Num 3, etc...

That has fixed the issue entirely.
Apparently using modifers, as the 'Key Combination' for named macros conflicts with FTL Assist Me.





There aren't that many key combinations I can use for named macro actions, if they have to be keys I won't accidentally press in game...
And cannot use any of the modifiers, that are used in my FTL Modifiers.

Still, can use Num 1 through Num 0, along with Shift of those...
So 20 isboxer macros, per character set... which is plenty.

[lax]

Did some troubleshooting with Mosg, in vent this morning.

Changing the 'Key Combination' for each of the Named Macro actions, from:
- Ctrl + Shift + Letter

To:
- Num 1, Num 2, Num 3, etc...

That has fixed the issue entirely.
Apparently using modifers, as the 'Key Combination' for named macros conflicts with FTL Assist Me.

Incorrect.

The reason it is "conflicting" is because many of your Key Maps have the Hold option enabled. This means your Mapped Keys are holding down the "FTL Assist Me" combo while also holding down the Key Combination(s) from your WoW Macro(s). Remove the Hold option on your custom Key Maps and your macros should begin to work as intended.

With your old approach, you used the key "0" for example, so from Slot 1 or 2 this ended up holding: Shift+Backspace+0. Since you apparently have no key bindings on Shift+0,this worked fine for you.

However, your new WoW Macros being assigned to Ctrl+Shift+__ means that it might now be holding: Shift+Backspace+Ctrl+Shift+__. If you throw one with Alt in there it's going to be holding down all 3 modifiers. e.g. Shift+Backspace+Alt+X+Ctrl+Shift+__. Disabling Hold will make that Shift+Backspace, Alt+X, Ctrl+Shift+__ which was originally intended



I use, and would highly recommend, using key combinations such as Ctrl+Shift+__ and Ctrl+Shift+Alt+__ for many WoW Macros.

My example configuration (downloadable) in HOWTO: Configure ISBoxer like a pro demonstrates that using Ctrl+Shift+Alt+__ and Ctrl+Shift+__ is okay. This HOWTO is new, and I would also highly recommend you check it out while you're reconfiguring things. It might help you cut out a lot of per-team customizations.