View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023409 | Return of Reckoning | Abilities | public | 2024-10-20 20:40 | 2025-05-11 13:55 |
Reporter | R1CH | Assigned To | Zumos | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Summary | 0023409: WE Kisses can proc twice in a single ability use | ||||
Description | Despite having a 250ms EventInstigatorCooldown, it seems a single ability use can trigger multiple procs when using an ability that hits twice like Puncture. | ||||
Tags | No tags attached. | ||||
|
|
Might be actually the intended behavior- 250ms cd allows several procs in the same second, and there are several abilities in game which do several hits with intention of potential of triggering several procs off same ability use. | |
I tried to check this through slow motion recording of the attack and it's very hard to tell what the actual delay is - one time I measured 260ms between the damage instances and another time 233ms. Without millisecond precision in the combat log I'm not sure of the actual values (and I assume the log timestamps are client-side regardless), I can't seem to find where this is calculated on the ability viewer either. | |
This is how it worked live with Welf double hits (finishers) + it shows Kiss dmg in combat log before the attack that procced it, which is also how it worked Live. Glad to see that it actually works like this now! | |
Intended behaviour: Abilities like Puncture have a 250 ms delay between both hits | |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-10-20 20:40 | R1CH | New Issue | |
2024-10-20 20:40 | R1CH | File Added: 4q2g4224Gu.png | |
2024-10-22 16:32 | Zxul | Note Added: 0044867 | |
2024-10-22 17:02 | R1CH | Note Added: 0044868 | |
2024-10-23 02:05 | Sinisterror | Note Added: 0044870 | |
2024-11-09 03:38 | Emissary | Assigned To | => Zumos |
2024-11-09 03:38 | Emissary | Status | new => assigned |
2025-05-11 13:55 | Zumos | Status | assigned => closed |
2025-05-11 13:55 | Zumos | Resolution | open => fixed |
2025-05-11 13:55 | Zumos | Note Added: 0046653 |