Botmaster5 wrote:let the ISB argument commense....
Now that you've seen the light, might as well add ISB:
Uptime = 1 - (1 - crit * hit)⁴
ISB Damage = Total Damage * 20% * ISB Uptime
Remove hit from the equation once NBT #2592 is fixed.
Botmaster5 wrote:let the ISB argument commense....
Guybrush wrote:Botmaster5 wrote:let the ISB argument commense....
Now that you've seen the light, might as well add ISB:
Uptime = 1 - (1 - crit * hit)⁴
ISB Damage = Total Damage * 20% * ISB Uptime
Remove hit from the equation once NBT #2592 is fixed.
Wosser wrote:If the debuff could not be resistet separetly after you crit, the formula would be 1-(1-critchance)⁴ but since it can, the chance for the event of "no apply" is the chance for a normal hit+the chance for a crit with the debuff resisting individually, so the formula is 1-(1-Critchance+Critchance*(1-Hitchance))⁴.
Wosser wrote:Hmm, your right, didnt saw that you could simplify it. What do you mean with unbugged ISB?
|
Botmaster5 wrote:Don't forget that ISB can be pushed off in the current debuff environment, so how can that be configured into your uptime calculation?
Guybrush wrote:The debuff cap will be increased in 3 weeks anyway so there's no reason not to include it.
|
Guybrush wrote:Wosser wrote:Hmm, your right, didnt saw that you could simplify it. What do you mean with unbugged ISB?
An unresistable ISB: http://report.nostalrius.org/plugins/tracker/?aid=2592
Botmaster5 wrote:Guybrush wrote:The debuff cap will be increased in 3 weeks anyway so there's no reason not to include it.
1.7 in 3 weeks? did i miss the announcement?