Multi Step Isboxer Project [Update]

[Ualaa]

For IWT to work with the Pally:
- You need an IWT keybind for the Pally in Warcraft.
- The pally needs Click to Move to be enabled.
- You need the pally to acquire the target of whatever you want to kill.
- You need to send the Wow IWT keybind to the Pally.

[Nexor]

For IWT to work with the Pally:
- You need an IWT keybind for the Pally in Warcraft.
- The pally needs Click to Move to be enabled.
- You need the pally to acquire the target of whatever you want to kill.
- You need to send the Wow IWT keybind to the Pally.

Well to be honest i am not to worried about the IWT function (I focus on the Paladin like 95% of the time and have currently no other melee char that i play when i box).
But if you read the whole post (i didn't mentioned but the Slaves have the same settings in game and keybindings in that case like the Pally) the Slaves basically started to run towards the Dummy and melee it.

To aragent:
After looking through the Macros i noticed the lvl 85 paladin version
!if (character in "Class Paladins Protection" and character in "85") /castsequence reset=combat/20 Consecration,Divine Protection,Consecration
Divine Protection

Has mostly the 2nd Divine Protection to much, personally i think though Defensive/Offensive Buff CD abilities shouldn't be in a macro setup like this unless a rotation more or less require em.
I think in a further version maybe should give those abilities a extra hotkey for Offensive and one for Defensive.

[Leovindica]

@Aragent, I have re-installed the old 2 step with the macrogenerator but with the new macro's you made and that does work altho it wil mean a VERY large macro:-) But for easy to manage macro's your new way should be much easier and clearer.

[Aragent]

@Aragent, I have re-installed the old 2 step with the macrogenerator but with the new macro's you made and that does work altho it wil mean a VERY large macro:-) But for easy to manage macro's your new way should be much easier and clearer.

Correct and thus why I changed to the new way Lax has explaind the issue (and I will have this fixed right away)

[ruab]

So, with the notes from Lax, I have made some progress -

I added a Key Combination to each of the Sequence and Proc macros for the 5 specs I have in my current party. The specs are:

* Prot Pal - Seems to work fairly well, although there were 2 typos in the macro - the double "!" i mentioned earlier, and the 80-85 proc macro is split with a carriage return, causing everyone in the party to say "Diving Protection" every time I clicked the button.
* Resto Druid - Macros are no-ops, so works as expected
* Elemental Shaman - Seems to generally work, although I have not done any DPS comparisons to my old macros
* Destro Warlock - Character appears to spam curse of elements until OOM - no other spells are cast
* Arcane Mage - Casts Mirror Image, Evocation and then sits idle

So, I am going to spend some time tonight looking at the macros in detail to see if I can figure out the behavior issues.

Thanks for all the work and advice!

--Ruab

[Lax]

The reason your WoW Macros aren't executing is because you didn't give them a possible way to execute. Named WoW Macro Action is the same as WoW Macro Action, except the macro and the Key Combination are configured in this library. Named WoW Macro Action, and WoW Macro Action, are the same as Keystroke Actions, except that they are directly linked to a WoW Macro on that Keystroke. In this case, the bug is that you are allowed to Export this without it having any keystrokes to press!

/click names can be used to execute the WoW Macro from some other WoW Macro. If one is not given, it will be automatically generated internally -- the macro has to have a name either way. The /click name has no use at all, other than if YOU want to put "/click MyOtherMacro" inside some WoW Macro that is running due to some keystroke or actual mouse click.

So each of your macros either needs a Key Combination that is unique against all of the other WoW Macros loaded on the same character. I would generally recommend separating the WoW Macros into Sets on a per-class basis, and then only load the right class's set for each Character. That way you can reuse the same 3-5 key combinations (e.g. because a Hunter won't need to load Mage) instead of 30-50.

The tradeoff to separating the macro sets is that your Hunter will not have Mage loaded, and therefore it will need to be loaded in order to put a Mage in that slot.

Personally I don't switch teams around more than once every 30 seconds so I really don't mind my method of switching teams:
1. Drag a character into some Slot to replace another
2. Export -- this part will generate the ISBoxer Addon with the right toon names from the switch, and it will tell each window to reload ISBoxer settings
3. Re-launch the newly modified team -- this is going to apply the characters that are now specified by the team. This is important, because an Export is just going to tell each logged-in guy to reload (not switch to the replacement character)
4. Do a /console reloadui on all characters that are still in the game -- this reloads the ISBoxer Addon and thus all of its newly adjusted WoW Macros

Takes a few seconds but it's not that bad. Most people don't realize this is possible.

[Aragent]

The reason your WoW Macros aren't executing is because you didn't give them a possible way to execute. Named WoW Macro Action is the same as WoW Macro Action, except the macro and the Key Combination are configured in this library. Named WoW Macro Action, and WoW Macro Action, are the same as Keystroke Actions, except that they are directly linked to a WoW Macro on that Keystroke. In this case, the bug is that you are allowed to Export this without it having any keystrokes to press!

/click names can be used to execute the WoW Macro from some other WoW Macro. If one is not given, it will be automatically generated internally -- the macro has to have a name either way. The /click name has no use at all, other than if YOU want to put "/click MyOtherMacro" inside some WoW Macro that is running due to some keystroke or actual mouse click.

So each of your macros either needs a Key Combination that is unique against all of the other WoW Macros loaded on the same character. I would generally recommend separating the WoW Macros into Sets on a per-class basis, and then only load the right class's set for each Character. That way you can reuse the same 3-5 key combinations (e.g. because a Hunter won't need to load Mage) instead of 30-50.

The tradeoff to separating the macro sets is that your Hunter will not have Mage loaded, and therefore it will need to be loaded in order to put a Mage in that slot.

Personally I don't switch teams around more than once every 30 seconds so I really don't mind my method of switching teams:
1. Drag a character into some Slot to replace another
2. Export -- this part will generate the ISBoxer Addon with the right toon names from the switch, and it will tell each window to reload ISBoxer settings
3. Re-launch the newly modified team -- this is going to apply the characters that are now specified by the team. This is important, because an Export is just going to tell each logged-in guy to reload (not switch to the replacement character)
4. Do a /console reloadui on all characters that are still in the game -- this reloads the ISBoxer Addon and thus all of its newly adjusted WoW Macros

Takes a few seconds but it's not that bad. Most people don't realize this is possible.

Thanks Lax as always.
I will correct the issue right away (Not sure why I thought that since we were calling it internelly that it didn't need a combination), However this is a easy fix that I will rectify.

[Iru]

The reason your WoW Macros aren't executing is because you didn't give them a possible way to execute. Named WoW Macro Action is the same as WoW Macro Action, except the macro and the Key Combination are configured in this library. Named WoW Macro Action, and WoW Macro Action, are the same as Keystroke Actions, except that they are directly linked to a WoW Macro on that Keystroke. In this case, the bug is that you are allowed to Export this without it having any keystrokes to press!

/click names can be used to execute the WoW Macro from some other WoW Macro. If one is not given, it will be automatically generated internally -- the macro has to have a name either way. The /click name has no use at all, other than if YOU want to put "/click MyOtherMacro" inside some WoW Macro that is running due to some keystroke or actual mouse click.

So each of your macros either needs a Key Combination that is unique against all of the other WoW Macros loaded on the same character. I would generally recommend separating the WoW Macros into Sets on a per-class basis, and then only load the right class's set for each Character. That way you can reuse the same 3-5 key combinations (e.g. because a Hunter won't need to load Mage) instead of 30-50.

The tradeoff to separating the macro sets is that your Hunter will not have Mage loaded, and therefore it will need to be loaded in order to put a Mage in that slot.

If I understand this correctly it means that all the !If (character in "Class ATG") components in each macro are superfluous as you would have to assign macro sets to characters manually. That means the only upside of this overall approach is avoiding the need to manage multiple macro sets for different levels of the same spec. That's not nothing but it leaves you with a lot more setup work that the previous approach.

[Iru]

Following up on your own post is bad form but too bad. Hopefully this post will help some others avoid the same over-engineering path I went down...

So I was attempting to implement Aragent's per-class/spec 2 step macro solution over the week-end and discovered - as Lax has mentioned - that Wow helper macros without key bindings are silently dropped from the ISBoxer addon per-character files.

As I'm trying to set this up for all possible class/spec combinations (saves adding to it later) and I don't want to consume 30 unique key bindings, I broke the macro helpers into 30 separate units (one per class/spec) with a Rotation and a Proc macro in each. I then created 30 ATGs (plus the appropriate level ATGs) and altered my spam key steps to invoke the appropriate helper action for each class/spec. For those of you doing the math, that means 30 actions in each of step 1 & 2.

A conversation with Lax on irc this morning about my concerns about the performance of that many actions in a single step, led to Lax chiding my about a lack of virtualization, which led to the recognition that I had made things way too complicated.

Specifically, the 30 class/spec ATGs and the 30 actions per step are both unnecessary. If you use the same key strokes for the Rotation and Proc macros (e.g. use Ctrl+[ & Ctrl+] for Roation & Proc respectively) in each class/spec helper, you don't need to assign characters to class ATGs and you can remove that part of Aragent's macros (as I noted above), although you do still need the level ATGs. You then assign the helper sections on a per character basis, which both acts as a selector and ensures that ISBoxer will protect you from sticking the same character in multiple groups as the assigned key sequences will clash. The spam macro them becomes very simple: just invoke the key presses directly (e.g. use Ctrl+[ & Ctrl+]). No named macro assignments, no ATGs.

tl'dr: Moral of the story: Keep It Simple Stupid

[Darelik]

Following up on your own post is bad form but too bad. Hopefully this post will help some others avoid the same over-engineering path I went down...

So I was attempting to implement Aragent's per-class/spec 2 step macro solution over the week-end and discovered - as Lax has ...

Be nice if u could post a screenshot or better yet, the resulting xml as I'm a bit slow. Cheers.

Edit: think i just got it rofl.
-Remove the class/spec atg's!
-Just select the toons from the helper macros eg highlight your prot paladin's name on the prot helper macro itself (bottom right window)
Assign ctrl [ to sequences and ctrl ] to procs!
Yaaaarrrr!!! Did i get it? Can't test til i get home. Will update.

Update:
-i didn't remove the class/spec ATGs (will use them for other things), instead i split up the class/spec helper macros into their own respective sets, e.g. 1 set for paladin protection prot; this gave me a total of 60 sets altogether
-moved aragent's sequence and proc macros into their respective helper macro sets
-assigned ctrl + [ to all class/spec helper macro sets that are sequences and ctrl + ] to procs
-made the 2step spam key (Key maps -> 2 Step -> Mapped Keys -> 2 Step) concise by removing all the "named wow macro action" for each class/spec sequence and procs for both steps
-added just a regular keystroke action ctrl + [ for step 1 and ctrl + ] for step 2 in the same 2 Step mapped key where the "named wow macro action" for each class/spec sequence and proc were removed
-also removed the extra "Do FTL Assist Me in General Key Map -> self" step in the "Melee IWT" mapped key within "Custom" Key Map as this was causing jumpy targetting for the driver toon
-going into Game Helpers -> World of Warcraft -> Macro Sets, i just selected the toon's class/spec within the macro set, e.g. for my prot pally, i went to Paladins Protection Proc and highlighted my toon on the bottom rightmost window and then do the same for the sequence
hope this helps someone.