Castrandom Change

[blast3r]

http://forums.worldofwarcraft.com/th...10332343&sid=1

I have posted a thread on the Blizzard bug report forum asking for clarification on the nature of this change (bug or intended). Hopefully I'll get a response.

for some weird reason they refuse to even answer questions about this. I just tried the reset=1 and it does not work. I also tried a castsequence and couldn't get it to work either.

/startattack
/stopcasting
/castsequence reset=10/target/combat Judgement of Light, Hammer of the Righteous, Hammer of Wrath, Holy Shield, Shield of Righteousness, Hand of Reckoning

I'm so pissed right now if I don't get my dps up to where it was before I am disabling my accounts and not coming back.

[Sam DeathWalker]

Big Big hit for me.

No sure at this point what I will do at all .....

Sadly it dosnt look like its unintentional:

http://forums.worldofwarcraft.com/th...419505&sid=1#0


Have not seen a blue post on this, except people theorizing thta this was intended...

How many times are you going to write this same sentence? In how many threads? I'm putting you on ignore - this has gotten ridiculous.

When the change went to the PTRs with the very first version of 3.2 Test, there was just as big an uproar on the PTR Forum. There was no "blue response" but all the threads reporting it as a bug were deleted or locked. That means that the development team knew about it and left it that way for the weeks and weeks and many iterations of 3.2 Test that were patched to the PTRs.

This was purposely coded in. If you somehow still think it's a bug, then go to the Bug Report Forum. I suggest reading the sticky there regarding how to post a useful bug report, because, "Blizz you suk make /castrandom work the way it did before 3.2 or I qwit," will just get ignored.

If you can come to the conclusion, based on examination of the code and the manner in which the PTR testing process proceeded for 3.2, that this is not a bug but you would like to see this decision on the part of the developers reverted, then post on the Suggestions Forum. Again, read the sticky there regarding how to create a proper post in that forum because the usual whining and threats will just get ignored.

[Ughmahedhurtz]

http://forums.worldofwarcraft.com/th...10332343&sid=1

I have posted a thread on the Blizzard bug report forum asking for clarification on the nature of this change (bug or intended). Hopefully I'll get a response.

After looking at that, and then doing some searching on similar threads there and in the UI/Macros forum, MAN is there a lot of pre-pubescent nerdrage over people wanting a blue confirmation. Mostly, "NO AND YOU ARE ALL IDIOTS FOR ASKING!!!11"

Sheesh.

[edit] By the way, if this was intended and there's a way around this using /click, be prepared for /click macros to start breaking, too.

[Moorea]

http://www.dual-boxing.com/showthrea...light=%2Fclick

Thanks a lot ! but i see on that post

"Disclaimer: This assumes you press the button 5 times per second. If you press the button faster or slower, you will need to adjust the number of commas to Keystrokes/second times seconds between casts."

That's seems useless to me I don't want to be a robot hitting keys at same pace - maybe I'll stick to a castsequence

[SERE]

By the way, if this was intended and there's a way around this using /click, be prepared for /click macros to start breaking, too.

Please dont say that!

I am curious if these changes were put in place to get rid of the totem stomping macros. ?

[Greythan]

So as I said, castrandom is purely a gimmick now. Its purpose is to pick between what type of critter you want to ride or turn your polymorph target into.

Silly.

[Owltoid]

Castrandom isn't a total loss for multiboxing moonkins who are trying to get some benefit out of eclipse. It's still more idea than castsequence and given that you don't know which one has proc'd it's better to have:

/castrandom wrath, wrath, starfire

But yeah, this change really sucks for the most part.

[Sam DeathWalker]

I think you can get around it with two keys (not 100 percent sure though).

Clearly if you press a key tied to a single spell (say an instant cast with no cooldown) it will stop the castrandom from trying to cast the spell on cooldown.

Thus is seems to me that you could have short term (i.e. no cooldown) spells on one castrandom tied to one key and the long term castrandoms tied to another key. The short term castrandoms will always fire. The long term might hit one on cooldown but then you go back to the short term key, it fires then you can go back to the long term key ....

And you have a bit more flexibility this way you might have only 30 seconds spells on your long term cast random and need only hit it once every 30 seconds. So you spam the short term key then hit the long term key every 30 seconds or so.

[Jubber]

It's definately an annoying change but nothing gamebreaking. We as boxers will learn to adapt just like everyone else will.

[Crel]

Whoa, this explains why my dps has gone to crap :P. Ill have to re-write ALOT of macros. Like Fur said, it(was) very usefull for situational procs, one being my Dk's Rune strike. Glad I saw this, was about to heroic farm!