My claim is that the current implemented casting speed influence of dexterity is wrong. I am aware that casting speed is determined by breaking points on live, but Phoenix does not use that and has a formula for calculating the cast speed instead.
So the trend line of casting speed tests from Pendragon can be used if breaking points are not considered.
I did not test mastery of the art. The test is done on Phoenix with mota 0, on Pendragon with 0% casting speed bonus.
I made Pendragon and Phoenix cast speed tests during Alpha. The results can be found here:
https://docs.google.com/spreadsheets/d/1BFbHYz_smxP8KPGoytb4SqQnEOoPqUc8SIKmSqQF4BI/edit?usp=sharing
First sheet compares current Phoenix implementation to a formula that was circulating on VN boards before breaking points were found.
The next three sheets summarize the casting speed tests for three different casts made on Pendragon. Casts were done for 3min 30sec each time, so the total number of casts varies from 50 to 243.
The average trendline out of these three different cast tests is very close the the claimed formula from the VN boards. This leads me to the conclusion that the current cast speed implementation:
[casttime]=[delve]* (1 - (([dex]- 60) * 0,15 + ([dex] - 250) * 0,05) * 0,01)
is wrong and should be replaced by this formula from VN boards (mota needs to be added):
[casttime] = [delve] * (1 - ([dex] - 70)/600))
http://www.ign.com/boards/threads/full-cast-speed-test-for-all-delves-click-here-to-see-how-much-dex-you-need-p.250680778/ post #4
You can see that Phoenix uses a formula that has a kink at 250dex, decreasing the slope and hence cast time if 250dex is exceeded. So dex higher than 250 is worth more than dex below 250dex.
The VN board formula, and the live test data provided show a linear behavior without a kink. Every dex is worth the same amount of cast speed decrease.
I added a graph comparing the difference in casting speed between the two formulas.
You can see that the current implementation leads to too high casting speeds beyond ca 290 dex, leading to up to 5% too high casting speed for 375dex.
I am well aware that this is contradicting a grab bag stating:
"Q: Would you please give more detail as to how dex affects a caster? For instance, I understand that when I have my dex maxed I will cast 25% faster. How does this work incrementally? And will a lurikeen be able to cast faster in the end than another race?
A: From a dex of 50 to a dex of 250, the formula lets you cast 1% faster for each ten points. From a dex of 250 to the maximum possible (which as you know depends on your starting total), your speed increases 1% for every twenty points. So, as you can see, a lurikeen may be able to cast A VERY TINY AMOUNT faster than another race, but just barely, and even then depending on the starting stat. "
Firstly this is just wrong. VN board formula that was based on casting speed tests years back, and my data provided just don't show it. Secondly, your current formula does exactly the opposite. Beyond 250dex the casting speed gain per dex is increased instead of decreased as explained in the Grab bag.
So the trend line of casting speed tests from Pendragon can be used if breaking points are not considered.
I did not test mastery of the art. The test is done on Phoenix with mota 0, on Pendragon with 0% casting speed bonus.
I made Pendragon and Phoenix cast speed tests during Alpha. The results can be found here:
https://docs.google.com/spreadsheets/d/1BFbHYz_smxP8KPGoytb4SqQnEOoPqUc8SIKmSqQF4BI/edit?usp=sharing
First sheet compares current Phoenix implementation to a formula that was circulating on VN boards before breaking points were found.
The next three sheets summarize the casting speed tests for three different casts made on Pendragon. Casts were done for 3min 30sec each time, so the total number of casts varies from 50 to 243.
The average trendline out of these three different cast tests is very close the the claimed formula from the VN boards. This leads me to the conclusion that the current cast speed implementation:
[casttime]=[delve]* (1 - (([dex]- 60) * 0,15 + ([dex] - 250) * 0,05) * 0,01)
is wrong and should be replaced by this formula from VN boards (mota needs to be added):
[casttime] = [delve] * (1 - ([dex] - 70)/600))
http://www.ign.com/boards/threads/full-cast-speed-test-for-all-delves-click-here-to-see-how-much-dex-you-need-p.250680778/ post #4
You can see that Phoenix uses a formula that has a kink at 250dex, decreasing the slope and hence cast time if 250dex is exceeded. So dex higher than 250 is worth more than dex below 250dex.
The VN board formula, and the live test data provided show a linear behavior without a kink. Every dex is worth the same amount of cast speed decrease.
I added a graph comparing the difference in casting speed between the two formulas.
You can see that the current implementation leads to too high casting speeds beyond ca 290 dex, leading to up to 5% too high casting speed for 375dex.
I am well aware that this is contradicting a grab bag stating:
"Q: Would you please give more detail as to how dex affects a caster? For instance, I understand that when I have my dex maxed I will cast 25% faster. How does this work incrementally? And will a lurikeen be able to cast faster in the end than another race?
A: From a dex of 50 to a dex of 250, the formula lets you cast 1% faster for each ten points. From a dex of 250 to the maximum possible (which as you know depends on your starting total), your speed increases 1% for every twenty points. So, as you can see, a lurikeen may be able to cast A VERY TINY AMOUNT faster than another race, but just barely, and even then depending on the starting stat. "
Firstly this is just wrong. VN board formula that was based on casting speed tests years back, and my data provided just don't show it. Secondly, your current formula does exactly the opposite. Beyond 250dex the casting speed gain per dex is increased instead of decreased as explained in the Grab bag.