Macro help! Paladin ret slaves :P

[Ualaa]

Technically, it is allowed because you are using Blizzard's own macro system.
You're not going to suffer account disciplinary action because you're using the Blizzard system.
However, Blizzard has systematically removed the ability to do macros like this, so this is definitely something Blizzard does not want you using.

We had a castrandom ability, where you could use:
#show
/castsequence reset=target/5 Flame Shock,Null
/castrandom Lava Burst, Lava Burst, Lava Burst, Lightning Bolt

If a spell was not available, the castrandom would not pick it.
Since there were a lot more Lava Bursts then the Lightning Bolt, you'd have Lava Burst fire off whenever it was available.
Blizzard broke castrandom, by making each spell stick if it was called, until it was actually available... so when Lava Burst was called, you would have to wait potentially 8 seconds for its cooldown to expire.

The next work around was using commas as a timing mechanic:
#show
/castsequence reset=target/5 Moonfire,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=target/5 Insect Swarm,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/cast Wrath

Each of the commas was a no-action step, and based on your own spam speed you would adjust the number of commas so each spell would fire off ideally just as it expired.
Blizzard removed that ability, too.

Now we have the /use 1, as a timing mechanic.
It is definitely against the spirit of the rules of the game, as we're using a one button mash macro to determine which spells to fire off and when.
Blizzard has consistently removed the ability for macros to determine our actions.
They want us to manually choose what fires off, by clicking the button ourselves.
At some point, this type of macro will break; since the Burning Crusade expansion Blizzard has consistently broken macros that do everything by changing the macro system.

[Lyonheart]

Now we have the /use 1, as a timing mechanic.
It is definitely against the spirit of the rules of the game, as we're using a one button mash macro to determine which spells to fire off and when.
Blizzard has consistently removed the ability for macros to determine our actions.
They want us to manually choose what fires off, by clicking the button ourselves.
At some point, this type of macro will break; since the Burning Crusade expansion Blizzard has consistently broken macros that do everything by changing the macro system.

Its a losing battle for them. Someone would figure out a way to get them to work again.They would have to make it so you can not use any combat abilities in a macro. They really should just give up. IF they somehow managed to break ALL combat macros of any kind. They would lose a large portion of their players..IMO.. i mean look at all the sites dedicated to macros? Is it not proof that players WANT to be able to simplify rotations in a way that they are not starring at cool downs, but would rather enjoy the virtual environment around them? I think one of WoWs reason for success, at least in part, is due to the macro system.. its unmatched in any game. It could be part of the reason other MMOs are not more successful ( not having great macro systems in place). It makes the game BETTER for some of us! Sure there are those of you who love the challenge that whack-A-Mole provides! And can top DPS in raids using spells and abilities individually.. but MOST
players want a little help.. and WoW macros provide that.

Originally Posted by 20kilo
hello again dear helper friends XD
i was reading the sites mirai and chivalrous gave to me and it enlight alot from my new macro world :P
but i found quite nice mechanics on these with numbers, but no one seems to be able to explain how it work
anyone know how this babys work? i know they use priority use from bottom to top but why that numbers are there lol :P

#show Crusader Strike
/castsequence reset=0.3 1,1,1,1,Crusader Strike
/castsequence reset=0.3 1,1,1,Judgment
/castsequence reset=0.3 1,1,Templar's Verdict
/castsequence reset=0.3 1,Exorcism
/cast Hammer of Wrath
/script UIErrorsFrame:Clear()


thanks again!




This works great btw..just need to figure out how to add inquisition without spamming it