I thought i would start this off right..

This bug has been around since the beginning of succession This was a bug report started by Bonechi on May 4th 2020 and was supposed to be under investigation and nothing was ever done with it.

Ok I have already made a report on this bug but at the time I was unsure what was the cause of it,

after some testing I have confirmed what causes the bug and could help the devs fix it.

Whats the bug?
The bug is when using certain skills in quick succession will result in the skill being cancelled with you being locked in place for 2 seconds while the error "Try again in a moment" appears at the top of your screen

Whats the cause?
If you use (Crouching Wolf) for the 20% attack speed and gain 3 shards, if you use (Roaring Tiger) into either (Wave orb) OR (Rage Hammer) it will lock you in place for 2 sec, wont cast the skill and will come up with the "try again in a moment" error, the cause is when using (Roaring Tiger) with 3 shards it will consume them BUT it does not consume them on cast but consumes them after cast so if you have a attack speed buff like (Crouching Wolf) 20%, when using (Roaring Tiger) into (Wave orb) the game will still think you have 3 shards and try and cast the empowered version of that skill, as soon as the animation starts your shards will be already consumed by (Roaring Tiger) Therefore "try again in a moment"

Note:
This bug can be reproduced with greater success with almost 100% success rate if the user has any attack speed buff above 10%

This bug can also be reproduced without attack speed buffs
attack speed only increases the frequency of the bug occurring

UPDATE: Bug still present (06/10/2020) and after more testing you can run into the bug when using Flash Step and/or Silent Step as soon as you do a skill that consumes 30 shards
Video evidence?
https://streamable.com/p2c33k

Also here is my video as well i am hoping something will be done to fix the Mystic she has been broken for FAR to long

After 2 years of Bug reports they finally fixed the "wait a moment bug"

Been in Test server since it went live this morning and it looks like its finally fixed.