A comprehensive list of every bug I've encountered when using Kaneki's power
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
- Kaneki will start a Kagune Vault animation only for the animation to bug out repeatedly and the vault to be cancelled
- Kaneki will randomly lock on to a vault he was nowhere near mid-grapple
- Kaneki will randomly decide he doesn't feel like using his grapple even though the reticle is giving the all-clear
- Kaneki will randomly jump in place when attempting to perform a grapple and will waste a leap token without actually grappling
- Kaneki will be stopped dead mid-grapple by an object he barely grazed
- Kaneki will autoaim onto a survivor even though the reticle indicated he was targeting the environment
- Kaneki still autoaims onto survivors through walls
- Kaneki will autoaim onto a different part of the environment than his reticle was targeting
- 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
- Kaneki will be considered too close to grapple on surfaces that are sufficiently far away
- 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
- 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
- Succeeding the grab-attack QTE will cancel the grab-attack
- Kaneki will get one last chance to use the third leap when losing Enraged mid-grapple sometimes and lose that chance other times
- The timing window on the grab-attack QTE is inconsistent
- 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
Tagged:
Declined
Comments