Haste was buffed in a recent patch, by about 50%:
http://www.worldofwarcraft.com/patch...patch2p01.html

This came up when my guild was debating Quag's eye mechanics... I said that you wouldn't really get the full benefit of quag's eye if you were using 1.5 sec casts because you would run into the 1.5 sec global cool down....at which point everyone insisted the GCD was only 1 sec. Unless things changed very recently, I remember being just under the GCD with 2 points in improved corruption...

so my first question: What is the GCD?

I did look this up on other sites to try and prove this to them as well...I always found 1.5 seconds as the value...and occasionally a mention of 1 second for rogues. However, they *proved* it was 1 second because of the grayed out timer thing that starts when you press a hot key finished before their casting bar for a 1.5 sec cast did (I did this with searing pain as well and noticed minimal difference between the two times, but they wont accept that..I write the difference off due to the fade timer starting slightly before the cast bar).

Next, and the only reason I'm questioning this even, a mage pointed out he was able to chain cast his 1 second rank 1 noobbolt. my rank 1 shadow bolt is also less than 1.5 seconds and I spammed that too. I would like to think that lowb spells are an exception to the global cooldown, but don't have solid proof. edit: nevermind spamming rank 1 shadowbolt does give me "spell is not ready yet" after casting... now to convince everyone else I'm not a moron

Thats my other question: Do rank 1 spells follow different rules?

I realize this is fairly basic information, but no one believes me...If I'm wrong I must look like an ass...but I really don't think I am

It's 1.5sec for the global cooldown. You may say it's not the case if you have any amount of lag. Scorch for example is a 1.5sec cast but the gcd will always be finished before scorch is cast because of lag.

The early spells (rank 1/2 usually) are outside of the global in that sense, yes. They are exceptions to the rule. Once the spells hit the natural GCD, they follow it's rules until the bloody end.

Lag may make it seem that spells hasted to be faster than the GCD will go through without interruption- but if you slice that ping lag off "That spell is not ready".

As for how to convince people? You can't, really. You can tell them, and they can believe you, or they can put their fingers in their ears and refuse to listen. If they get different results, make sure they're accounting for lag... but there are people who believe that Elvis is alive and you can't do a damn thing to change someone that stubborn =)

This is correct, with the sole exception of Rogues who enjoy a 1.0 second global cooldown (and that's not terribly germane here now is it?).

Hi, just registered here to post in this thread. Lots of helpful information about spell haste here, which I was looking for in trying to decide when to use the prince dagger or blade of wizardry, and when to use quags eye or some other trinket.

I think it was cleared up in this thread earlier but the two items do not share proc cool downs. It doesn't happen all the time, but frequently enough i will have both hastes running at the same time.

Given all the facts I really don't believe I'd spend the money that people charge for the blade of wizardry. I got it when it dropped in a guild group in heroic shattered halls. 2000-3000 is just too much for a 30dps improvement.

One point that I havent seen brought up that is worth consideration when comparing versus +spell damage is mana cost. A spell improved by +damage still costs the same mana, while each spell cast during haste does increase damage, the over all mana cost is higher since in the end you are casting more spells to increase your dps. This may not be an issue when grouped with pallys and shadow priests.

I had to comment on this statement that I've seen thrown around a lot. Spell Haste does reduce the GCD equal to the cast time of the spell that is hasted. I frequently spam scorch with both quags eye and the wizardry blade equipped, and I *never* get a this spell is not ready message. A mage that I play with also has quags eye and scorch spams a lot (we both do it for capacitor procs) and he assumed the GCD would limit scorch but I convinced him to try it and he agrees, he never gets hit by the GCD while spamming scorch with the quags eye proc. Hell, I never get hit with the GCD while both the quags eye and wizardry buffs are active at the same time.

I play from the midwest on a server in the virginia data center. My raw ping (out of game) to the data center is usually about 45-50. My in game ping as reported fluctuates between about 85 and 105. I don't believe you can blame lag on not triggering the GCD when we're looking at a .1 second lag at most.


Morphene

In the Patch Notes:

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

I ran across this little gem:

* Spell Haste: The amount of spell haste rating needed per percentage of haste has been increased substantially. However, spell haste will now affect channeled spells, increasing the rate of their effects and decreasing their total duration. The same amount of damage/healing per casting will occur, but will take less time.

Sorry to everyone that bought the blade of wizardry. I also think I'm gonna stop farming Quag's Eye so hard now. This with the AM fix is going to make me look at 44/17/0 again....

Did anyone test on the PTR how much it has actually been decreased?
Sad to see such a nice stat going down tho.

"fireballs will be about 2.6 second casts after the nerf
frostbolts about 2.2"

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

I've just been on the PTR, and my fireballs had 2.6 seconds cast time with the Quagmirran's eye proc, which would mean that 320 spell haste now equals to 13.33% cast time reduction. Or in other words, 1 spell haste rating would equal to 0.0041667% cast time reduction.

From the above linked thread...

Quagmirran's Eye: 320 haste rating
Pre-nerf - 25% (Fireball 3->2.3 - Frostbolt 2.5->1.9)
Post-nerf - 12.5% (Fireball 3->2.6 13.3%? - Frostbolt 2.5->2.2 12%?)

Looks like the new value is 10 rating haste => .4% haste ( => Blade of Wizardry: 280 haste rating -> 10.9%)

For Quag's eye.....assuming 10% proc rate and 45 sec cooldown (7.5 * duration?); 10 casts to proc (25sec); 12.5% haste for 6sec..allows 3*2.6 fireballs (6sec..with 7.8sec benefit ); cooldown (45sec); ... 7.8/76 => 10.3% uptime * 12.5% haste => 1.28% dps increase?!?

I hope i screwed up somewhere....because with the lower proc rate, larger presumed cooldown and nerfed haste, quag's eye kinda sucks.

The only math mistake I see is it wont' take 10 casts to proc on average, about 6.5. Not a HUGE change but at least something.

Wasn't the proc rate nerfed to 10% couple of weeks ago? (which would imply 10 casts to proc, on average?)

My main beef is: Will I still be able to squeeze that third fireball in during the proc? If I am able to Quagmirrans is probably still worth using but since I don't use stopcasting-macros I really doubt I will be able to get off more then 2 casts per proc during fireball-spam. Looks like Quagmirrans is ending up in my bank after the patch...

I'm pretty sure you will get the 3rd spell in and the proc will expire mid-cast.

Proc - ~2.6s - Fireball - ~5.2s Fireball.. I believe if the next cast begins in the remaining .8s which is possible giving a quarter second to each previous cast, you should just be able to get it in.

From a quick test on PTR, it looks as if the new value is 21 spell haste rating = 1% spell haste, which is a 100% increase from the old 10.5 value.

You will get 3 hasted fireballs unless you are running with 400+ms latency. In which case you should be anyway considering stopspellcast macros.

After the haste nerf its 3 fireballs in ~8 seconds, instead of ~9.3s. 6.5 casts to proc after cooldown is overs means the average proc intercal is about 105s for fireballs. So you'll gain about 1.3/105 = ~1.23% increase in DPS. (assuming 100ms lag)

Assuming maxed hit, ~30crit fireball and +900dmg, the proc alone is worth about 20 +dmg, so the trinket is about ~60 +dmg worth of damage. Except that it increases manaconsumption. It however scales with your gear, so with +1200dmg raidbuffed it's worth a bit more.

No, it wouldn't.

P(pr) = 0.1
P(no proc) = 0.9

Chance of proc in N spells equals chance of not not proccing in N casts.

P(pr|n) = 1 - (1 - P(pr))^N

50% chance of proc is at 6.5 casts. After 10 casts, you'd be at 65% chance to have procced.

I've been using 0.9 base log for 0.5, gives out 6.578 casts to achieve 50% for proc. or =log(0.5;0.9) as in excel.

"How many times 0.9 has to be multiplied by itself untill it is 0.5", or that's how I understand it.

Actually, Stein is right. The chance for the trinket to proc after exactly the n-th cast is 0.9^(n-1)*0.1, and the average number of casts require to proc it is C = sum(n=1..infinity)(n*0.9^(n-1)*0.1) = 10.

After 10 casts, your chance to have received a proc is higher than 50% (65%), and at 6.5 casts you have a 50% chance to have the trinket procced, but the average amount of casts required for a proc still is 10. Even if it seems to contradict

We answered different questions. I answered "How many casts before a *50% chance* of a proc?", while you answered "On average, how many casts *per* proc?"

cdf = 0.5 vs. expected value, in probability terms.