This alone should tell you that your test is flawed, how can the cast time go UP with MORE dex?
<<<<<
One second on 100 casts isn't really meaningful. That's well below the noise threshold, considering the technique.
On the other hand, changes of as much as fifteen seconds on 100 casts are large enough to be significant. I guess the thing to do is to turn his test around - see how many casts can be made within a specified period.
Note, by the way, that it's extremely unlikely that Mythic uses a millisecond tick in this game. It's more likely to be on the order of 20 milliseconds, or even longer. And those breaks in the pattern aren't terribly inconsistent with a 25 millisecond tick.
Oh, and for those who aren't all that into programming, a "tick" is the interval that you update your outputs based on the inputs. In this case, "outputs" might be things like spells hitting the target, messages to both caster and recipient telling them they've had a spell-effect occur, damage, that sort of thing, while inputs might be spells cast, swords swung, etc.
So if an event were to take barely longer than X ticks, then it will actually take (X+1) ticks. And incremental changes in event timing would all be subject to that "rounding up to the next tick" behaviour that we may be seeing here.
-----signature-----
Angharad Macsen, Legendary Smith
Alfwyn MacLlyr, LGM everything
Jaelithe Tregarthe, LGM everything
Elfwine Llyrsdottir LGM SC, WC, Fletcher, Siege
Alfwyn MacLlyr, LGM everything
Jaelithe Tregarthe, LGM everything
Elfwine Llyrsdottir LGM SC, WC, Fletcher, Siege




