1. #6401
    Quote Originally Posted by Djuntas View Post
    (Classic WoW warrior!) Hi guys, I recently saw https://www.youtube.com/watch?v=9MIY...channel=Swifty this video, but cant get the macro to work. I followed comments...Im fairly great at UI and all that jaaz in wow, but this dont work;

    #showtooltip Sweeping Strikes

    /castsequence reset=15 Sweeping Strikes,

    Berserker Stance,Berserker Rage,Whirlwind,

    Battle Stance,Thunder Clap

    Any know why the macro might not work? Just spams the chat, thx.
    The spells need to be on the same line, they're all part of the cast sequence.

    Code:
    #showtooltip Sweeping Strikes
    /castsequence reset=15 Sweeping Strikes,Berserker Stance,Berserker Rage,Whirlwind,Battle Stance,Thunder Clap


    addons
    weakauras
    Lua Wall of Shame
    Originally Posted by Zarhym (Blue Tracker)
    this thread is a waste of internet

  2. #6402
    Hey all,

    In classic WoW; how do i link a profession ability (enchanting) into a macro? /me is a macro n00b

    I want my trade chat enchanting marketing macro to have the links of the spells so they can see the mats. I've seen others do it.

    Is there an addon to make is stupid proof?

  3. #6403
    Quote Originally Posted by Djuntas View Post
    Any know why the macro might not work? Just spams the chat, thx.
    Code:
    #showtooltip Sweeping Strikes
    /castsequence reset=15 Sweeping Strikes,Berserker Stance,Berserker Rage,Whirlwind,Battle Stance,Thunder Clap

  4. #6404
    Keyboard Turner Yeaboii's Avatar
    Join Date
    Feb 2017
    Location
    Western Australia
    Posts
    6

    Please Help

    cool macros guys

  5. #6405
    Looking for mage macros!

    First macro:

    If I have a mouseover hostile target > cast counterspell on my mouseover target.
    If I don't have a hostile mouseover target > cast counterspell on my current target.
    Second macro:

    If I have a mouseover friendly target > Remove Curse on that target.
    If I have a friendly target targeted > Remove Curse on that friendly target.
    If I have any target targeted and is pressing alt > Remove curse on self.

  6. #6406
    Quote Originally Posted by Tekktra View Post
    Looking for mage macros!

    First macro:

    If I have a mouseover hostile target > cast counterspell on my mouseover target.
    If I don't have a hostile mouseover target > cast counterspell on my current target.
    Code:
    #showtooltip
    /cast [@mouseover,harm,nodead][] Counterspell


    Quote Originally Posted by Tekktra View Post
    Second macro:

    If I have a mouseover friendly target > Remove Curse on that target.
    If I have a friendly target targeted > Remove Curse on that friendly target.
    If I have any target targeted and is pressing alt > Remove curse on self.
    Code:
    #showtooltip
    /cast [mod:alt,@player][@mouseover,help,nodead][] Remove Curse


    addons
    weakauras
    Lua Wall of Shame
    Originally Posted by Zarhym (Blue Tracker)
    this thread is a waste of internet

  7. #6407
    Quote Originally Posted by Kanegasi View Post
    Code:
    #showtooltip
    /cast [@mouseover,harm,nodead][] Counterspell




    Code:
    #showtooltip
    /cast [mod:alt,@player][@mouseover,help,nodead][] Remove Curse
    Thank you so much!! Lots of love!

  8. #6408
    I understand that range cannot be used as a conditional in a macro to preform an action. Is it possible to use range as a conditional to page an action bar using something like the Bartender4 Custom Conditionals interface ?

  9. #6409
    Quote Originally Posted by Kaelth View Post
    I understand that range cannot be used as a conditional in a macro to preform an action. Is it possible to use range as a conditional to page an action bar using something like the Bartender4 Custom Conditionals interface ?
    no, cause you dont get range reported.

  10. #6410
    Quote Originally Posted by tmamass View Post
    no, cause you dont get range reported.
    Then how is it that unit frame addons grey out when someone is out of range ?

  11. #6411
    Quote Originally Posted by Kaelth View Post
    Then how is it that unit frame addons grey out when someone is out of range ?
    Range is not available in the secure macro system. This system also allows addons to adjust clickable frames and bars in combat. If a macro can't do it in combat, an addon can't do it in combat.
    Last edited by Kanegasi; 2020-01-20 at 08:57 AM.


    addons
    weakauras
    Lua Wall of Shame
    Originally Posted by Zarhym (Blue Tracker)
    this thread is a waste of internet

  12. #6412

    Question

    Trying to make a simple 2 spell /castsequence macro, but one of the spells has [@player] and the other does not.
    Do I need 2 lines? What would the correct macro look like?
    Here's my broken macro:

    Code:
    #showtooltip
    /castsequence [@player] reset=30 Death and Decay,Epidemic,Epidemic,Epidemic,Epidemic,Epidemic,Epidemic
    Last edited by Shao; 2020-01-23 at 07:39 PM.

  13. #6413
    Quote Originally Posted by Shao View Post
    Trying to make a simple 2 spell /castsequence macro, but one of the spells has [@player] and the other does not.
    Do I need 2 lines? What would the correct macro look like?
    Here's my broken macro:

    Code:
    #showtooltip
    /castsequence [@player] reset=30 Death and Decay,Epidemic,Epidemic,Epidemic,Epidemic,Epidemic,Epidemic
    Unfortunately, you cannot specify different secure options within a cast sequence.


    addons
    weakauras
    Lua Wall of Shame
    Originally Posted by Zarhym (Blue Tracker)
    this thread is a waste of internet

  14. #6414
    Hi folks, I've been trying to work out a macro to combat the Ashjra'kamas / Goblin Glider compatibility issue and I'm a bit stumped on why my macro is working the way it is.

    This macro does some other stuff, but I've omitted those parts because I've already tested with them removed so I'll just post the problematic portion:

    Code:
    #showtooltip
    /use [noworn:item:169223,noswimming] 15; [worn:item:169223,noswimming] item:109076

    I would expect this to use a Goblin Glider Kit whenever I'm wearing my legendary cloak and to use the Goblin Glider tinker on any other cloak, however it does nothing.

    What's stranger still is that if I reverse the worn and noworn conditions it seems to work, but also leads to a Goblin Glider Kit to be consumed when using a cloak tinker (although that part makes sense to me as I'm specifying that if the legendary cloak isn't worn it should use one) and so I'm a bit stumped.

    Any advice on how to fix this seemingly weird interaction? (Or am I being dumb?)

    P.S I've tried using item names and the same thing occurs, I'm using item IDs simply for space for the rest of the macro.
    P.P.S I've also tried swapping the order in which the macro checks for the item equipped and using equipped instead of worn as the conditional to no avail.

    Edit: Okay, after readdressing the macro and splitting it into 2 lines I've managed to fix the Goblin Glider being consumed portion, but it still won't do anything when I'm wearing my legendary cloak. I'm beginning to think that it's the cloak at fault and I'm unlikely to have a fix

    Code:
    #showtooltip
    /use [worn:item:169223,noswimming] Goblin Glider Kit;
    /use [noworn:item:169223,noswimming] 15;

    Edit 2: Duh, managed to fix it simply by removing the worn part of the macro and making sure the noworn portion was checked for first. Still an odd interaction that Ashjra'kamas will work fine in a macro with noworn but not the worn conditional.
    Last edited by Mectrid; 2020-03-07 at 05:08 PM. Reason: Solved

  15. #6415
    Quote Originally Posted by Mectrid View Post
    <snip>
    You actually taught me something new. This whole time, I thought the worn conditional only did item types like swords or shields, never thought it accepted specific items.


    addons
    weakauras
    Lua Wall of Shame
    Originally Posted by Zarhym (Blue Tracker)
    this thread is a waste of internet

  16. #6416
    Quote Originally Posted by Kanegasi View Post
    You actually taught me something new. This whole time, I thought the worn conditional only did item types like swords or shields, never thought it accepted specific items.
    Indeed, that's interesting. Would improve my Tarecgosa macro slightly.
    But your duty to Azeroth is not yet complete. More is demanded of you... a price the living cannot pay.

  17. #6417
    Quote Originally Posted by Kanegasi View Post
    You actually taught me something new. This whole time, I thought the worn conditional only did item types like swords or shields, never thought it accepted specific items.
    Tried it using Hyperthread Wristwraps 168989 and it doesn't work.

    Code:
    #showtooltip
    /use [worn:item:168989] 9; Fire Blast

  18. #6418
    Will appreciate help on making these macro's do what I they're intended to!

    Code:
    #showtooltip Remove Curse
    /cast [target=mouseover,help,exists] [help] [target=targettarget, help, exists] [target=player] Remove Curse

    I need the one above to self-cast @me when I press alt. As it is now, it doesn't.

    Code:
    #showtooltip
    /cast [nomod][] Counterspell
    /cast [mod:shift,@focus][] Counterspell
    /cast [mod:alt,@mouseover][] Counterspell

    For some reason this macro doesn't counterspell my focus when I press shift like it's supposed to. Input?

  19. #6419
    Quote Originally Posted by Tekktra View Post
    Code:
    #showtooltip Remove Curse
    /cast [target=mouseover,help,exists] [help] [target=targettarget, help, exists] [target=player] Remove Curse
    I need the one above to self-cast @me when I press alt. As it is now, it doesn't.
    Code:
    #showtooltip
    /cast [mod:alt, @player] [@mouseover, help] [help] [target=targettarget, help] [@player] Remove Curse
    Added the first conditional (use on self when pressing Alt) and shortened the rest: @ is a shorthand for "target=", and exists is implied by help. It's only necessary when you specify a target without other filters, for later conditionals to be able to trigger.
    I also removed the spell name after #showtooltip, as the @player makes sure there's always something the macro will try to execute, and thus display. But by letting the macro decide, it will also show whether the mouseover or target's target is out of range (keybind text turning red in standard interface)

    Quote Originally Posted by Tekktra View Post
    Code:
    #showtooltip
    /cast [nomod][] Counterspell
    /cast [mod:shift,@focus][] Counterspell
    /cast [mod:alt,@mouseover][] Counterspell
    For some reason this macro doesn't counterspell my focus when I press shift like it's supposed to. Input?
    The [] empty bracers are to blame. The first line checks whether you don't press a modifier, that's correct, if not, go to second conditional - which is just "do the standard behavior, as if you clicked the ability without macro".
    Thus, Counterspell is used on your (hostile) target.
    The third line does trigger, but Counterspell is already on CD by then.

    I'd write it like this:
    Code:
    #showtooltip
    /cast [mod:shift,@focus] [mod:alt,@mouseover] [] Counterspell
    All in one line. It's usually preferable for readability to catch modifiers first, then fall back to standard functionality when those don't apply.

    Note: all of this was written while waiting for, and sitting in the bus, so it wasn't tested for mistakes in the game.
    But your duty to Azeroth is not yet complete. More is demanded of you... a price the living cannot pay.

  20. #6420
    Quote Originally Posted by Nathanyel View Post
    Code:
    #showtooltip
    /cast [mod:alt, @player] [@mouseover, help] [help] [target=targettarget, help] [@player] Remove Curse
    Added the first conditional (use on self when pressing Alt) and shortened the rest: @ is a shorthand for "target=", and exists is implied by help. It's only necessary when you specify a target without other filters, for later conditionals to be able to trigger.
    I also removed the spell name after #showtooltip, as the @player makes sure there's always something the macro will try to execute, and thus display. But by letting the macro decide, it will also show whether the mouseover or target's target is out of range (keybind text turning red in standard interface)



    The [] empty bracers are to blame. The first line checks whether you don't press a modifier, that's correct, if not, go to second conditional - which is just "do the standard behavior, as if you clicked the ability without macro".
    Thus, Counterspell is used on your (hostile) target.
    The third line does trigger, but Counterspell is already on CD by then.

    I'd write it like this:
    Code:
    #showtooltip
    /cast [mod:shift,@focus] [mod:alt,@mouseover] [] Counterspell
    All in one line. It's usually preferable for readability to catch modifiers first, then fall back to standard functionality when those don't apply.

    Note: all of this was written while waiting for, and sitting in the bus, so it wasn't tested for mistakes in the game.
    Epic thanks not only for the help with creating them, but thanks for the knowledge to create my own in the future! <3

Posting Permissions

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