Cast random?

[Lyonheart]

did they remove /castrandom? it does not work for me

Its bugged or somthing. It gets stuck on spells that are on a cooldown

[Lyonheart]

Well its nerfed. These kind of random changes just piss me off! how was /castrandom hurting anyone? I FINALLY get a macro to do DPS I'm happy with while boxing and it gets nerfed GRR!! /castsequence i lose 400-800 dps

[mmcookies]

The current behavior for /castrandom is

1. it picks a random spell from the list
2a. if the spell successfully casts, it picks a new spell from the list
2b. if the spell fails for any reason, it will continue to try that spell until it is cast

So let's say you add Hammer of Wrath on your list and attack a practice dummy. If it happens to pick Hammer of Wrath, it will keep on trying and failing to cast Hammer of Wrath.

Not happy about this change at all.

[mmcookies]

Time to bind my G15 keys and mash six of them at once, lol...

[Kromtor]

wow...... horrible change. makes castrandom like a stupid version of castsequence and anyone who was using it properly to begin with will easily compensate with logitech keyboard macros or other methods.

[mmcookies]

I think Blizzard wants us to literally faceroll all the separate spell buttons.

Maybe we'll get a couple of injury lawsuits out of it.

[Khatovar]

Ugh, this is most unpleasant. Here's hoping they change it back.

[RobinGBrown]

I can understand why they've done this, it's because there are so many 'no-brain DPS mash' and 'I-win'macros out there that use /castrandom. It's the 'no-brain'/'I-Win' bit that annoys them, they want skilled players to have an advantage over those who just want to press one button again and again.

It sucks if you're a multiboxer though, even more so if you want a mixed team.

[Clone]

Well cast sequence has never been much different to cast random for me for dps. But I feel for the guys with high ms in game. They are the ones who will be most affected by this change.

[Ughmahedhurtz]

Shit. What a moronic change.

[Greythan]

As was already stated, this simply makes castrandom a "dumb" castsequence. The logic is now really only useful, as I understand it, for gimicks like polymorph type selection or mounts. Why you'd use castrandom in a multi-spell rotation is beyond me. You either go macroless, castsequence, or click.

Odd change.