Castrandom Change

[Meeo]

Just wondering if anyone else notice the change to Castrandom? and if you have figured a work around using other castrandom sequence changes or another macro build.


What i mean about the castrandom change is that, cast random was "corrected" to work as originally intended, to where it does not skip a spell anymore, it waits until that spell is cast-able before continuing.

[Tonyx]

Hasn't it always worked like that?

[Chilaxx]

Well, what would u like it to do instead? In my opinion this isn't a bad thing..

[coupas]

Noooo... that isn't good at all.

So if it's not off cooldown it will wait until it gets off cooldown, cast it and then move on the next random??

[Tonyx]

Noooo... that isn't good at all.

So if it's not off cooldown it will wait until it gets off cooldown, cast it and then move on the next random??

Pretty sure it always worked like that.

[Khatovar]

No, the way it used to work is it would try to cast something, if it was on cooldown it would say "oh well" and "roll" another skill with the next push. Sometimes it would pick the same skill, other times it would pick something else, as it was an entirely new randomized attempt.

From my understanding {I don't have any castrandoms to try atm} it now refuses to move on or "roll" a new random attempt until it casts the skill it tried to cast...exactly like a castsequence that gets caught on a cooldown.

For example, my hunters used to have :

/castrandom Kill Shot, Kill Command, Rapid Fire, Steady Shot, Tranquilizing Shot, Viper Sting

as the tail end of a /click macro. At random points, it had the ability to throw those abilities in as filler. If, say, a mob didn't have mana and it tried to cast Viper Sting, it would throw an error message and then ignore the cast attempt and next time around it could try casting something else {or Viper again, depending on luck of the draw}.

Now, it would try to cast Viper, say "I can't cast this" and keep trying to cast it every successive push saying "I still can't cast it", like the guy that walks into a window and says "Hmm, I can't get outside" and proceeds to keep walking into the window.

[blast3r]

ugh...no wonder my dps dropped by half on my pallies. THIS SUCKS!!!

[Fef]

Ouch, this is very bad news. I rely A LOT on /castrandom the way it used to work. Ouch, very ouch ...

[Greythan]

Ouch. Didn't play my team last night, just my mage so I didn't notice this.

This will force my hand to choose between a full blown cast sequence for my shaman or just a straight lb spam. I was using a lightning bolt, lightning bolt, chain lightning random for heroic trash pulls. Sorta gimps that.

Really, what's the point of cast random compared to cast sequence with this change? If I have to have all spells fire before any spell can be fired again, I'd rather control the cast order.

Odd.

[Owltoid]

I'm curious if this will stop remove curse. My server, Dalaran, was pretty much nuked all last night so I didn't get to test anything.

Currently my macro is something like:
/castrandom [target=party1] Remove Curse,,,,
/castrandom [target=party2] Remove Curse,,,
/castrandom [target=party3] Remove Curse,,
/castrandom [target=party4] Remove Curse,
/castrandom [target=party5] Remove Curse

(it's a well known macro on this site that I take zero credit for)

Is this macro still going to work since it's not getting hung up on a cooldown or is it going to continue trying to remove a curse from someone who doesn't have one?

I just did the cure poison quest for my druid since the abolish poison always successfuly casts and I wanted my remove poison mechanic to work the same as remove curse... could be lots of time wasted