[Robo]

Describe the issue:
Update on Demonstep.
The bug that allows for multiple castings of Demonstep before the spell goes on cooldown has been fixed. Which is good, as I no longer have to worry about activating 3x accidentally (as I usually double or triple press GCDE spells to make sure they actually activate).

However, the bugs that make Demonstep inactive until the normal cooldown has passed by either darkening the spell or faking a reset, despite negating damage, still exists, unfortunately.

While I have no true evidence for this unless I find and use precise timing tools to figure this out, I'm thinking that this happens because the delay to Demonstep still exists (delay doesn't seem to affect the immunity time, just the cooldown)

Hypothesis for Darkened Demonstep (and "Failed" Cooldown Reset, despite blocking damage) Bug
Spell actually achieves a cooldown reset but it happens before the spell actually goes on cooldown causing the darkened state when the spell actually goes on cooldown due to the general Darkened Spell Bug

  - Spell Cast / Demonstep Activation -> Demonstep goes on cooldown once the .2 second delay is over -> remaining .3 second duration
                                                     vs
  - Spell Cast / Demonstep Activation -> Damage is blocked (.15 seconds pass) = Cooldown Reset -> Demonstep now actually goes on cooldown once the .2 second delay is over = Spell Darkens due to being used "as soon it is off cooldown"

Normally, other spells tend to darken (preventing the cooldown timer from being seen) when activated as soon as their cooldown finishes, so since the delay exists and a cooldown reset happens right before the spell goes on cooldown, it would possibly emulate when spells are cast as soon as their cooldown finishes.  Thus if true, would explain why the spell darkens.

If this is the actual explanation for why this happens (when I'm grasping at anything that might be the problem), the real culprit is that the spell has a cooldown reset before the spell goes on cooldown due to the delay, so removing the delay would remove this bug.


Hypothesis for when the Spell is Fake and Looks Fine but isn't (Blocking Damage but Failed Cooldown Reset but Spell looks fine)

I'm just assuming that somehow the delay somehow messes with the window of time where Demonstep can achieve a cooldown reset and fails to fully reset before the spell duration ends, but still manages to block damage at the final moment of its duration, causing the appearance of a cooldown reset without actually achieving one and with it needing your full cooldown time before it is usable again.
  (Is it possible that the spell blocks damage for .5 seconds but can only achieve a reset if it happens within .4 seconds?)
  (Is it possible that the spell blocks damage for .6 seconds for some reason, which is why it blocks damage but fails to reset the cooldown?)

Since it is a spell that only lasts .5 seconds, it's definitely tough to figure out what exactly is wrong with it.  So I'm just throwing ideas of what might be causing it with no concrete evidence to back it up. I just want it to be fixed at some point so that masters of Demonstep can come out of hiding.

How to reproduce:
- Successfully Demonstep and continually use it, being successful each time and trusting that the cooldown reset will happen.
- At any point, Demonstep will block damage but fail to achieve a cooldown reset, darkening or becoming "fake", where the spell will go on cooldown and won't be usable until your normal cooldown time is over.
  - Darkening possibly means that the cooldown reset happened before the spell actually went on cooldown
  - Becoming Fake possibly means that the cooldown reset was unable to finish (if that's even a thing that happens)
- Cry when the only thing holding back a possible mastery of Demonstep is a bug.

Any relevant media (images, gifs/video, etc): 
The following video shows off the delay, the normal Darkened Bug for every spell, the Demonstep Darken Bug that fails to achieve a cooldown reset, the the Fake Demonstep Cooldown Reset Bug, and the audio of me continuing to click when Demonstep blocks damage but is actually unusable during the Fake Demonstep Cooldown Reset Bug