Idea - Unify target selectors and conditions over buf,dps,heal and cure sections

[eqholic]

Please let us use MA,!MA,Me,!Me,Pet,(and maybe add Gpet for other pets) and IF,NOTIF,IFME,NOTIFME in all sections. This would reduce the need to memorize or lookup what works where and also be useful. Things I wanted to do while writing the inis for my heroic team but couldn't:
a) heal1=Rune of Yorzan|20|!Me, toss a rescue rune on others but not myself because selfrunes are better
b) dps1,buf1=Yaulp X|Me|NOTIFME some mount, works in dps but not buf even tough mana regen is nice out of combat too. Of course I could just yaulp anyway, but that's ugly spam.
c) cure1=Natures's Salve|Me, cure2=Nature's Salve|Pet; BST cure that only works only on self or pet.
I know conditions are comeing and I'm looking forward to this, but they tend to become very verbose quickly. I'm all for KISS, but the question is simple for whom, the authors of the macro or the users.

 

[ctaylor22]

Please let us use MA,!MA,Me,!Me,Pet,(and maybe add Gpet for other pets) and IF,NOTIF,IFME,NOTIFME in all sections. This would reduce the need to memorize or lookup what works where and also be useful. Things I wanted to do while writing the inis for my heroic team but couldn't:
a) heal1=Rune of Yorzan|20|!Me, toss a rescue rune on others but not myself because selfrunes are better
b) dps1,buf1=Yaulp X|Me|NOTIFME some mount, works in dps but not buf even tough mana regen is nice out of combat too. Of course I could just yaulp anyway, but that's ugly spam.
c) cure1=Natures's Salve|Me, cure2=Nature's Salve|Pet; BST cure that only works only on self or pet.
I know conditions are comeing and I'm looking forward to this, but they tend to become very verbose quickly. I'm all for KISS, but the question is simple for whom, the authors of the macro or the users.

You will never understand how much I appreciate this post. People need to take notice of this post, because this is what I have been referring too. Not everyone is going to jump on the Conditions bandwagon.

I can only speak for myself, but it has always been about the Users and never the authors/myself. KISS was originally written and developed with the user in mind, and as a tool to try and encourage users to learn about modifying macros. KISS was always meant to be modified by the user, and to encourage that, the macro itself has to be simple.

Now Conditions are going to be a game changer for KISS, but at the same time that's no reason to throw everyone off the deep side of the pool. I think to be fair, we have to provide a way for the users to wade into the pool, as the user feels comfortable.

That's just my 2 cents, but I just write macro's.