Hi everyone ,
Does anyone know if this exists?
Printable View
Hi everyone ,
Does anyone know if this exists?
What is "macro library"? An add-on? ISBoxer's macro library? You're going to need to give a bit more information.
like the sticky on the WoD, isboxer macro library. I watched your vid on building rotations and comming a long way, however i can not get my (for instance arcane missiles on arcane mage) proc attacks to work, i cant build this into my steps or macro's
That seems like a more reasonable response. We aren't mechanical turks over here.Quote:
Originally Posted by Qrimetime
Usually the way this goes is something like: "Hey guys, I have the pasted my current mage macro set up below and have it mostly working but it halts at step 7 where it tries to cast procs and I just can't quite figure out what's wrong. The rest of the macro works fine if I comment out that step but I'd really like it to work. I've looked at the wowlazymacros examples to see if there was something obvious in syntax or order of the commands I was missing but that didn't make any more sense to me. Would anyone be so kind as to take a look at what I've got and provide some criticism/help? Thanks!"
If you understand...Quote:
Originally Posted by Qrimetime
1) What Actions are (e.g. Keystroke Action & Named World of Warcraft Macro Action).
2) How Targets work.
3) How Actions in Mapped Keys are used to send keys and/or macros to Targets.
4) How to create Steps within a Mapped Key, and, if necessary, how to utilize the "Do Not Advance" options within a Step.
...then this should be easy. :) The above list, while seemingly complicated as a new user, are the absolute basics of ISBoxer.
With that said, the video shows I have a two-step Mapped Key, where in step one I'm sending a keystroke that is bound to an in-game macro, and in step two I'm sending a different keystroke bound to Arcane Missiles. I'm pretty much just repeating what I said in the video.
On the other hand, and as Ugh pointed out, if you have an issue with macros not working as they should, then you should be troubleshooting those first, since no amount of ISBoxer wizardry will fix a broken macro.