Dash Back Bugged

So, This has happened way too many times.
When the AI performs an Heavy, my champ just won't dash back. Sometimes it does, but it has happened way too many times. As of posting this, I was in that new challenge, AND EVERY TIME THANOS PERFORMED AN HEAVY, I COULD"T DASH BACK.
5 Champs, 5 deaths, AND ALL Because I couldn't dash BACK !
My device is : OnePlus3T
Operating sistem : Android 8.0.0, Oxigen OS 5.0.1

And yes, I wiped my screen.

Comments

Gamer

Im dont hav thah isuse But hav a isuse when im try to back out of somone sp. Like genet venome. Im Think thah isuce is for Android or your devies and to be fair dont ikow much of Android any more hav iPhone so. Im hops yours dash back wuld be better

Blitzkilla420

this happens to me all the time too!
i would see the heavy coming and when i dash back or double dash back i would still get caught like i missed the dash but i didnt?

also i notice double dash is broken as I can dash once then dash again and then hold block but my block never holds and i get a 5 hit combo always by the AI

clearly our timings for blocking and dashing has been altered as this has been very noticeable since the last couple updates

im using a samsung s8+ with the latest android os and latest version of mcoc.
happens in all modes and with all champs too

Al_AhadHKGN

Blitzkilla420 wrote: »

this happens to me all the time too!
i would see the heavy coming and when i dash back or double dash back i would still get caught like i missed the dash but i didnt?

also i notice double dash is broken as I can dash once then dash again and then hold block but my block never holds and i get a 5 hit combo always by the AI

clearly our timings for blocking and dashing has been altered as this has been very noticeable since the last couple updates

im using a samsung s8+ with the latest android os and latest version of mcoc.
happens in all modes and with all champs too

Working as intended

Blitzkilla420

i still can double dash back properly from the last 3 updates now.. why is that?

can you confirm this is an issue that will be fixed in v. 18.0? @Kabam Rose @Kabam Miike @Kabam Zibiit