Macros kept on ISBoxers side

[luxlunae]

I myself switched from using conditional macros to class specific macro sets when I switched to Pro a few months ago. I really prefer pro because it gives you the option to be complicated when you want to be complicated or to get started on a new class in under half an hour when you DONT care about being precise/complicated.

My recommendation, when you make a new level one teampull up the spell book and make /cast macros for all of the abilities you'll learn until level 10, export and reload once, and then figure out how you want to use them later without having to reload again (by default I always start any dot macros with a castsequence reset=target DOT, null).

The way I initially handled my macro sets was to make my first one (priest I think it was), with a level 90 priest that had all of the abilities and ran them alphabetically from shift alt q to shift alt . And then ctrl shift alt for the same keys. I then copy this set for each class so I don't have to rebind/recreate fifty macros per class. Yes this means the bottom of my DK list has twenty priest macros, but who cares I'm not triggering them. I also developed a few macro naming conventions: rather than the name I just say what a buff is Buff Stats Buff Spellpower etc, and battle rez and rez are just called that not the ability name. I also started doing "t Name" for abilities that are talents not default spells. Obviously not something that really matters, just a personal preference.

The one thing I do not do is re-sort the macros by name at any time, because as I said I was very methodical about assigning key binds in order and I don't want them to be out of order if I need to add more to the end.

Druids are the only class for which I have multiple sets, I have druids split into Druid Caster (Boomkin/heal macros) and Druid Melee (kitty/bear). Half of the macros are the same.

[MiRai]

My recommendation, when you make a new level one teampull up the spell book and make /cast macros for all of the abilities you'll learn until level 10, export and reload once, and then figure out how you want to use them later without having to reload again (by default I always start any dot macros with a castsequence reset=target DOT, null).

For new teams I have a 'No Spec' Mapped Key which only spams my 1 and 2 keys. Then when the character hits level 10 I can assign a Mapped Key to them that is more suited for their actual spec.