v1.51 Bugs and Glitches

kaisers have always had a DC issue when doing too many hits too quickly.

However, it's not a noticeable DPS difference compared to Orb because Wingbeat has a hits cap while Orb only has a duration.

wingbeat is dishing out all its damage (48 hits) in 1.9 sec, verses ~20 seconds. and while kaiser can *Barely* maintain 2 active wingbeats, the frontload of damage is quite the increase in dps; not SO much more in longer (dpm) fights.

 Spoiler

A nexon forum thread i started back in late june, with videos of wingbeat glitch (for any curious)
http://maplestory.nexon.net/community#%2...26nxid%3D6

Ive since reversed my opinion, especially now that i'm approaching 5:00 dojo time. kaiser's mathematics with wingbeat is triple beat + gigas at the same time. right now (speed 2) i can manage two gigas per wing beat, and recast swords replacing one gigas, every cooldown. compared to the old combo, 7~8 gigas per wing beat, while 3 are active, again, replacing swords with one gigas every cooldown.

estimation math

 Spoiler

ignoring kaisers glitchy proc final attack dmg, swords dmg, and rounding for non exact numbers:
old - ~6 sec startup for three wingbeats; ~8 sec cycle per wingbeat recast/upkeep cycling; gigas spam between wingbeats
~8 gigas + 3 wingbeats = (96 hits) + (144 hits) over ~8 sec = <30 hps with ~6sec startup
problems: upkeep triple wingbeat cant be "perfect" recasting the cycle (4th wingbeat) will erase the first, and loss of hits. likewise, recasting late raises the total cycle duration, lowering dps.

new - no startup, 2 gigas + 1 wingbeat cycles = (12 hits) + (48 hits) over ~2 sec = 30 hps
problems: hit cap occurs quickly, requiring a wiggle reset; DC for attacking too fast.

so again, very rough estimate, no-delay wingbeat dps is constant, while the old formula requires startup and timing. the no-delay will kill faster.