Multi Step Isboxer Project [Update]

[Alge]

Cross-posted from ISBoxer.com forums:

I had someone with this exact same issue in #isboxer recently. Lax can probably give you a definitive answer but for now, I'd suggest giving each of your macros in WoW Class Proc and WoW Class Sequence a short, unique /click button name. For example, DKBS, DKFS, DKUS, DrBS, etc. These names won't be seen by anyone unless they go diving through the config so they don't need to be consistent, just unique. I wouldn't use key combos - that way madness lies.

Anyway, try that, it may fix the issue.

Alge

EDIT: just noticed that pretty much all the macros in Quick Setup 38 have /click button names so I'm confident this may work.

If someone gets this to work, please let us know. I'm not currently playing WoW so can't test it myself

[ruab]

Here is what I have tried so far, in addition to my earlier attempts -

I have confirmed that my INTERACTTARGET macro in Wow Key Bindings matches with the ingame key (I already use this key a fair amount, so i am confident it works).

I have given (as a test), the Paladin Protection Proc and Paladin Protection Sequence Macros a /click button name, and a key binding - I tested them both independently and together. In no cases did the macro execute beyond running to the NPC and /startattack.

I did not go through the exercise of giving every macro a /click name and/or key binding, as I figured testing with one class/spec would be sufficient.

I rechecked and confirmed that my character set was linked to all key maps, game helpers, action target groups, etc.

Thanks,
Ruab

[Aragent]

Cross-posted from ISBoxer.com forums:

I had someone with this exact same issue in #isboxer recently. Lax can probably give you a definitive answer but for now, I'd suggest giving each of your macros in WoW Class Proc and WoW Class Sequence a short, unique /click button name. For example, DKBS, DKFS, DKUS, DrBS, etc. These names won't be seen by anyone unless they go diving through the config so they don't need to be consistent, just unique. I wouldn't use key combos - that way madness lies.

Anyway, try that, it may fix the issue.

Alge

EDIT: just noticed that pretty much all the macros in Quick Setup 38 have /click button names so I'm confident this may work.

If someone gets this to work, please let us know. I'm not currently playing WoW so can't test it myself

Thanks Alge
I have a couple pms to Lax to get gis take on the problem

I am also troubleshooting and trying verious things to find the Issue

[Aragent]

Here is what I have tried so far, in addition to my earlier attempts -

I have confirmed that my INTERACTTARGET macro in Wow Key Bindings matches with the ingame key (I already use this key a fair amount, so i am confident it works).

I have given (as a test), the Paladin Protection Proc and Paladin Protection Sequence Macros a /click button name, and a key binding - I tested them both independently and together. In no cases did the macro execute beyond running to the NPC and /startattack.

I did not go through the exercise of giving every macro a /click name and/or key binding, as I figured testing with one class/spec would be sufficient.

I rechecked and confirmed that my character set was linked to all key maps, game helpers, action target groups, etc.

Thanks,
Ruab

Thanks Ruab
Rest asured I am working on the problem.

[Nexor]

Ok tried it with setting up iwt key in game with shift + \ in all chars that i had on,

Enabled under Game Helpers in the specific Macros the /click button name gave each a different name of the classes spec's i had on.

Reloaded the ui on all clients and the only thing happend was a wierd assist(no spells or abilities where cast),

Paladin = Main (WoW Melee)
Fire Mage = Slave
Resto Shaman = Slave (yes i know that one don't have a macro yet but assigned it anyway)

Anyway as i pressed Z while targetting a Dummy my main cycled through party members as target and ended after some time on the Mage as target pressing Z again after that and i still got the Mage as target.

Cleared all Chars targets manualy and tried it again targeted the Dummy but this time the Dummy was the target for all chars.

In regards of IWT My Paladin never went closer to the target or started to autoattack the target.

Also while pressing Shift + Z Main (only one in WoW Melee) stand still and Slaves (both in WoW non Melee) went off and attacked the dummy .

[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.

[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.