You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Lancer 4 uses Double Spearmanship, it is possible to get up to 3 attacks. For Rampant Warrior, since the proc chance is 100%, it will always perform 3 attacks.
This might due to the timer for proc cooldown only setting the flag after the timer is created. If PerformAttack is triggered within 0.033 seconds (combat log only shows 0.03, no further decimal places), it will avoid the cooldown flag.
So assuming PerformAttack has a 0.03 second delay:
0.00x First attack (Attack1), procs PerformAttack (Attack2), timer created for 0.033 seconds
0.03x Attack2 procs PerformAttack (Attack3) as cooldown flag has not been set
0.033 Timer activates, sets cooldown flag
0.06x Attack3 occurs, but does not proc further due to cooldown flag
Timers only guarantee to proc after the trigger time, so it might be entirely possible that the attack occurs before the timer during the server tick.
Fix should just be to move the setting of flag out of the timer.
In addition, since Rampant Warrior critical is applied OnAttackStart and removed OnAttackLanded, only the first attack will trigger the critical. The second (and the bugged third) attack will not.
Not entirely clear of this interaction as the OnDSLanded is proc-ing but not the critical trigger.
The text was updated successfully, but these errors were encountered:
gelguy
changed the title
Lancer 4's attack interaction with DSLanded
Lancer 4's double attack interaction with PerformAttack
Nov 13, 2016
When Lancer 4 uses Double Spearmanship, it is possible to get up to 3 attacks. For Rampant Warrior, since the proc chance is 100%, it will always perform 3 attacks.
This might due to the timer for proc cooldown only setting the flag after the timer is created. If
PerformAttack
is triggered within 0.033 seconds (combat log only shows 0.03, no further decimal places), it will avoid the cooldown flag.So assuming
PerformAttack
has a 0.03 second delay:0.00x
First attack (Attack1), procsPerformAttack
(Attack2), timer created for 0.033 seconds0.03x
Attack2 procsPerformAttack
(Attack3) as cooldown flag has not been set0.033
Timer activates, sets cooldown flag0.06x
Attack3 occurs, but does not proc further due to cooldown flagTimers only guarantee to proc after the trigger time, so it might be entirely possible that the attack occurs before the timer during the server tick.
fateanother/game/dota_addons/fateanother/scripts/vscripts/diarmuid_ability.lua
Lines 78 to 86 in c74bc09
Fix should just be to move the setting of flag out of the timer.
In addition, since Rampant Warrior critical is applied
OnAttackStart
and removedOnAttackLanded
, only the first attack will trigger the critical. The second (and the bugged third) attack will not.Not entirely clear of this interaction as the
OnDSLanded
is proc-ing but not the critical trigger.The text was updated successfully, but these errors were encountered: