Being balance specced, I often find myself healing and nuking on the same fight at the same time. I found it very annoying to always have to keep assisting back and forth from the tank to the mob depending on the spell being cast. So I decided to make some macros to allow me to "cast through" no matter what (similar to guild wars targeting). So for helpful spells I make a macro that casts on my target if its friendly, my ToT if my target is an enemy, and if I have no target casting it on myself.

Healing/Curing Spells:

#showtooltip <spell>

/cast [target=target,help] <spell>; [target=targettarget,help] <spell>; [target=player] <spell>


Damage/Debuff Spells:

#showtooltip <spell>

/cast [harm] <spell>; [target=targettarget, harm] <spell>


With these I can either target the tank, or the mob, and just cast my spells without having to worry about switching targets.

You don't need the <spell> part in #showtooltip unless the spell you want to show is not the first listed spell.

#showtooltip does more than the ? icon I believe. If you want the spell's actual tooltip information to render you need #showtooltip.

#show is forces the icon selection on the ? icon, but #showtooltip replaces the macro name tooltip on hover with the ability's details.

A druid in my guild wanted to do a similar thing with Thorns: Equip enough pieces of Cenarion to get a set bonus that affected the spell, cast it, then switch back, and I wrote a macro that did it for him. It went something like this:
/script local MySet=ItemRack_GetEquippedSet(); ItemRack_EquipSet("Thorns Set");
/cast Thorns
/script ItemRack_EquipSet(MySet);

Two caveats:
1) You're probably right about re-equipping your previous set, either it'll reduce your ticks or just not work during the channel. If that's the case just delete the last line of the macro.
2) I typed this from memory because my guild forums were recently changed around and old posts were lost. The spelling of the ItemRack functions might differ from what I wrote, if you get errors you'll have to find the right functions in the ItemRack source code.

I'd like to make a macro for Wing Clip and Mongoose Bite.

I currently have:

I chose the icon that is the same as Mongoose Bite's icon.

I'd like it to show Mongoose Bite's information when moused over, and have the button greyed out until Mongoose Bite is ready to use. Basically, the button act as a display to let me know when Mongoose Bite is up.

What I've noticed is that, the button resets itself to Wing Clip O_o Both display and mouseover information. I tried putting Mongoose Bite first in the sequence, but that stops Wing Clip from being cast until Mongoose has been used.

Any ideas?

As many others are frustrated with I'm sure, I've updated all my mods daily but still have problems disenchanting (i tried moving items to my bars or right clicking instead of left clicking as a workaround suggested by some but neither worked for me). If I try to d/e an item I get the blocked by blizzard UI classic message;

So I'm trying to see if there's a script I can run to disenchant my items, and would appreciate any help I can get if possible.

I tried doing:

/cast [target=mouseover] disenchant

to d/e whatever my mouse is on top of, I don't get an error when I run it, and it selects disenchanting but doesn't actually d/e the item, just gives me the glowing mouse icon as if i have to select what i need to d/e. I also tried typing [target="name of item to d/e"] but that gave me an error.

Anyone have any idea of what I could try?

is it at all possible to 1 button press go into zerker stance and cast zerker rage? this would be very nice for leveling but I can't seem to get it to work. I have tried the ones in this thread and in the linked "warrior macro" thread and it just casts zerker stance and quits.

It's 2 actions so you will always have to smash the button twice.

Seems to be an oversight; I would suggest posting it in the WoW UI forums as there's a chance Slouken may consider adding that capability. Definitely it appears that no matter what, /castsequence will take priority over what the icon/tooltip changes to.

Then again, who knows. It may be by design so you can't do exactly what you describe, but that doesn't seem to make sense when the same works in a simple /cast with conditions for different stances.