Correct Cast Time Caps?

Topics: Rawr.Mage
Jun 7, 2010 at 10:40 PM
Edited Jun 7, 2010 at 11:08 PM

The RAWR mage model allows you to specify a haste modifier.  When messing with this option I noticed that RAWR does not allow the cast times of non-channeled/non-instant spells to go below 1.04 seconds, regardless of how high you set the modifier.  We all know that, in game, the GCD forces spells to cap out at 1.00 second.  Why then, does RAWR cap out .04 seconds higher.

If any of you would like to observe this for yourselves, go to the mage model, click on the options tab, and then click the effects tab.  Set the haste modifier to something retardedly high, like 5 (which would be 400% haste in game).  After doing this, click back to the stats tab and hover over individual spells.  You will notice that cast times of non-channeled/non-instant spells cap out at 1.04 seconds.  (IE: Frostbolt, Fireball, Arcane Blast, Frostfire Bolt, Flamestrike, etc.)  The only exception to this was Scorch.

NOTE:  I'm assuming RAWR does this intentionally, and therefore it is not a bug.  Correct me if I am wrong.

Jun 7, 2010 at 11:29 PM

This is a display bug. Internally all spells have an actual cast time of cast time + latency. For display purposes in tooltip I remove the latency based on base cast time, which is a bit incorrect in this case. Default settings are 0.01 for chain cast latency and 0.05 for gcd latency. Normally a spell like frostbolt can be chain casted and uses the 0.01 latency, but when it's haste goes below gcd it starts behaving as a gcd spell. So it also takes 0.05 latency because you can no longer use the spell queue. Internally the cast time is correctly 1.05 and displayed in tooltip as 1.04 (1.05 - 0.01 because tooltip incorrectly thinks it's a chain cast spell). Scorch is the exception because it always behaves as a gcd spell.

Jun 7, 2010 at 11:55 PM
Edited Jun 8, 2010 at 12:02 AM

I extremely appreciate the speedy, detailed response to my question.  You fully addressed everything I needed.  Thank you very much!

EDIT:  I have one more question.  Can I still use the spell queue if my cast times are below 1.04 seconds but above the GCD (say 1.02 seconds)?

Jun 9, 2010 at 1:36 AM

You can't, the enforced limit is 1 sec + gcd latency, at least in Rawr. It could be argued whether this is an accurate representation of reality, but it has some validation based on the fact that if your cast is let's say 1.01 sec and you try to queue it, you'll on average hit a bit too soon some of the time and hit the client enforced gcd and miss the queue.