Anyway, having castsequence and/or castrandom macros does NOT mean you can't also have individual ability bindings for when you need to be dynamic!
Quoting this because it seems to be the summary of what everyone seems to be arguing with me about. The thing is, our arguments DO NOT CONFLICT.
I'm saying "You can't just have one, and ONLY one button to spam 100% of the time."
You are saying "But I have a button I spam 90% of the time!"
That's cool -- I don't have that sort of button setup but that is my PERSONAL macro preferences. 90% still does not equal 100%. So stop arguing as if I insulted you somehow by telling you you're wrong -- I didn't. You have other buttons than your spam button, don't you? Doesn't matter if you use them reliably or not -- my argument doesn't apply to you.
What I'm saying is -- you still took the time to think about and develop buttons for alternate situations (for example, CC/Interrupts/Healing/whatever). This was a priority for you, right? You can't just take one button and say "My team is done! Commence pewpew!" or you'll quickly learn the hard way that one size does not fit all.
So, just to clarify -- I'm not arguing with you. Your personal macro style doesn't sync with mine -- I like to micromanage, so I don't use castsequences/castrandoms. But my argument wasn't against castsequences/castrandoms (that little note was simply my personal macro preferences) -- my argument was about using ONE and ONLY one button to run your entire team.
And, for the record -- when I'm playing my shaman, 90% of the time I was hitting "Lightning Bolt". So I'm not arguing that spammable buttons are bad -- I've used them myself. But you still have to think "outside the box" about what might happen to your team (whether you're focused on PvP, raiding, heroics, questing) and tailor OTHER macros to those needs. Without that sort of thought, I feel you're dooming yourself to failure (or at least a very painful time when those situations do occur). For me, I care that I'm on a PvP server (and need anti-gank situational buttons), I do instances (and need heals/tanking buttons), and raids (for which I was constantly rewriting my macros per individual boss encounter).
I probably wouldn't have been able to do my instances while leveling if I had just my main "spam button". I probably would've been camped for ages if I hadn't bound grounding/interrupts/tremors and other anti-pvp server gankage buttons. I most certainly would NEVER have survived Karazhan without specific boss encounter buttons.
You see what I'm trying to say now? It's not that /castsequences are bad, it's that the idea that "to multibox effectively you have to put all your eggs in one basket" is just not feasable. You WILL run into special cases where you need special macros, and you DO need to think about those -- ESPECIALLY when you're trying to create a new group composition (which is exactly what the OP is trying to do). So, I say, telling a person that the effective way to multibox is to fit everything into one macro is completely ridiculous.
About /castrandom for Paladins specifically (and please note, I'm back on the "personal opinion" horse) -- I don't use it, because I want to be 100% sure I am keeping holy shield up because, at the time that I designed my macros, it was ESSENTIAL to preventing a crushing blow. For leveling? Heroics? Non-crushing bosses? Doesn't matter as much. But I still want to be able to control and maximize my pally's mitigation, threat management, and yes -- mana (mana was a bit of an issue for me, particularly multiboxing Karazhan pre-3.0).
Connect With Us