Close
Showing results 1 to 9 of 9

Hybrid View

  1. #1

    Default Macro things you can't believe you just learned...

    So on my recent team (druids), at level 30 I got everyone Balance as their secondary spec. I wanted to make sure I was always in moonchicken form before I started spewing magic. Also, because I am lazy, I wanted to be able to reuse that macro even if I wasn't specced Balance, but wanted to make sure I wasn't trying to cast spells I no longer knew.

    Some googling and I found: the spec conditional! Maybe to some here this is old hat, but to me it was really interesting, so here it is:

    Here's a macro I made for casting Moonfire if I'm in moonchicken form and of balance spec, putting myself in moonchicken form if I'm not in it, or just casting Moonfire if I'm not balance spec:

    Code:
    #showtooltip
    /startattack
    /cast [spec:2, stance:4] Moonfire; [spec:2] !Moonkin Form; Moonfire
    I tried using a simpler macro where I check spec:2 and nostance:4 but that didn't work for me. The # for spec is 1 for your primary spec, 2 for your secondary.

    Then I tried to get a bit more clever. Here I wanted to have a spammable castsequence that would intermix Moonfire with longer cast, harder hitting spells:

    Code:
    #showtooltip
    /startattack
    /castsequence [spec:2, stance:4] reset=target Starsurge, Moonfire, Moonfire, Starfire, Starfire, Starfire
    /cast [spec:2] !Moonkin Form
    /castsequence reset=target Moonfire, Wrath, Wrath, Wrath, Wrath, Wrath
    In this case, it looks at the first /castsequence line and says if I'm balance and in moonchicken, use those balance spells and blow stuff up. If I'm not, it falls down to the next line, and if I'm balance it tries to put me in moonchicken. If THAT line doesn't get executed, then that means I'm not a balance spec currently, so just fire my very lazy spammable stuff.

    It turns out there's also a similar conditional for talents - it's (shockingly): talent.

    For this one, you have 2 numbers - first is the row, second is the column. So, to check if you have the level 100 talent all the way to the right, you might do:

    Code:
    #showtooltip
    /cast [talent:6/2] Pulverize; [talent:6/3] Bristling Fur
    This will - at least I think - cast Pulverize if you have that, or otherwise cast Bristling Fur.

    Anyway, that was something I can't believe I just learned. If you're reading this far - share your tips that you just picked up.

  2. #2
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6815

    Default

    It's always nice to stumble upon new information that helps you out. For anyone who reads this and is interested in knowing all the macro conditionals available, there is a handy page on WoWpedia (I will forever call it WoWpedia) that has all of the up-to-date information on macro syntax.

    http://wow.gamepedia.com/Making_a_macro
    Do not send me a PM if what you want to talk about isn't absolutely private.
    Ask your questions on the forum where others can also benefit from the information.

    Author of the almost unknown and heavily neglected blog: Multiboxology

  3. #3
    Member Ughmahedhurtz's Avatar
    Join Date
    Jul 2007
    Location
    North of The Wall, South of The Line
    Posts
    7169

    Default

    You can prevent repeated shapeshifts via the nostance:2 modifier as well. Not sure if that's still a thing.
    Now playing: WoW (Garona)

  4. #4

    Default

    Quote Originally Posted by Ughmahedhurtz View Post
    You can prevent repeated shapeshifts via the nostance:2 modifier as well. Not sure if that's still a thing.
    For whatever reason, when I use nostance:whatever rather than ! the macros break.

    Thanks for the link, MiRai - somehow I had forgotten about the existence of that site.

  5. #5
    Member Ughmahedhurtz's Avatar
    Join Date
    Jul 2007
    Location
    North of The Wall, South of The Line
    Posts
    7169

    Default

    Quote Originally Posted by kate View Post
    For whatever reason, when I use nostance:whatever rather than ! the macros break.
    Interesting. I'll keep that in mind if/when I ever decide to respect mine for bear/kitty.
    Now playing: WoW (Garona)

  6. #6
    Member JohnGabriel's Avatar
    Join Date
    Oct 2008
    Location
    Seattle Washington, USA
    Posts
    2272

    Default

    Quote Originally Posted by Ughmahedhurtz View Post
    Interesting. I'll keep that in mind if/when I ever decide to respect mine for bear/kitty.
    If you're experimenting, I think it has something to do with spamming the key. Like it breaks if in middle of checking specs or something.

  7. #7

    Default

    When it was breaking my macros, I meant that it wasn't showing an icon, just the question mark. I hadn't even been using it, so I don't think it's that. My guess is a syntax error which I couldn't find - in any case, reversing the logic/restructuring the macro as I did made it work so I just went with that.

    What I did notice when I was spamming was that sometimes, if I was hitting the key really fast, I'd wind up not casting moon chicken form and just casting a spell.

  8. #8

    Default

    For healing touch procs in catform I use this.. had to change it as the old one stopped working.

    Code:
    #showtooltip
    /console autounshift 0
    /use [mod][@mouseover, help, nodead, exists][@party1, help, nodead, exists][@player] Healing Touch
    /console autounshift 1

  9. #9

    Default

    Until yesterday I had no idea you could get hunters to auto-face and it can all be done right in the WoW macro system.

    Code:
    #showtooltip
    /cast Powershot
    /stopcasting
    Sure, you have to take a talent to get it but pretty handy.

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •