A comprehensive list of every bug I've encountered when using Kaneki's power

LiveBritishReaction

SUMMARY OF THE ISSUE: A list of each unique bug I've come across when playing as Kaneki.

PLATFORM: PC

STEP BY STEP INSTRUCTIONS ON HOW THE ISSUE OCCURED: Unsure but the bugs are so frequent they should be easy to recreate in a match by simply playing Kaneki normally

1. Kaneki will start a Kagune Vault animation only for the animation to bug out repeatedly and the vault to be cancelled
2. Kaneki will randomly lock on to a vault he was nowhere near mid-grapple
3. Kaneki will randomly decide he doesn't feel like using his grapple even though the reticle is giving the all-clear
4. Kaneki will randomly jump in place when attempting to perform a grapple and will waste a leap token without actually grappling
5. Kaneki will be stopped dead mid-grapple by an object he barely grazed
6. Kaneki will autoaim onto a survivor even though the reticle indicated he was targeting the environment
7. Kaneki still autoaims onto survivors through walls
8. Kaneki will autoaim onto a different part of the environment than his reticle was targeting
9. When attempting to grapple to a surface that is out of range, Kaneki will randomly autoaim onto a completely different surface instead of failing to grapple
10. Kaneki will be considered too close to grapple on surfaces that are sufficiently far away
11. If Kaneki is standing directly next to a wall or structure, sometimes he won't be able to grapple anywhere along the whole length of it regardless of range
12. Kaneki will successfully grab-attack a survivor but change his mind mid-grapple and let go of the survivor even if there was nothing in his way
13. Succeeding the grab-attack QTE will cancel the grab-attack
14. Kaneki will get one last chance to use the third leap when losing Enraged mid-grapple sometimes and lose that chance other times
15. The timing window on the grab-attack QTE is inconsistent
16. The "Enraged Attack" score event still does not trigger when performing a grab-attack while already Enraged despite this being stated as fixed in a recent patch