Can't punish AI after SP attack since the update
DarknessFalls
Member Posts: 163 ★★
Has anyone else noticed that now it's more like 50-50 if you can punish AI after the defender throws an SP attack.
Since the update, now AI acts too quickly to punish you instead if you try to counter after an SP. Happened even back to back with me in a fight.
Also some cases now they are blocking the same as well too quickly. Now you can't even be sure this style of play will work against AI.
This AI issue is getting out of hand. Can kabam even fix this ?
Since the update, now AI acts too quickly to punish you instead if you try to counter after an SP. Happened even back to back with me in a fight.
Also some cases now they are blocking the same as well too quickly. Now you can't even be sure this style of play will work against AI.
This AI issue is getting out of hand. Can kabam even fix this ?
17
Comments
But yes the AI now recovers too quickly I noticed too because I use cheeith and she needs to punish specials and heavies and the opponent recovers TOO quickly especially the newer champs they have almost no recovery time.
Also it's almost impossible to punish champs with one hit heavy attacks like hulk or even juggs because they recover immensely fast now for some reason.
It's gotten to the point now that I've given up on punishing AI and play super passive in wars and BG, I'll take few extra seconds than to 50-50 risk it.
Few examples where there's 50-50 chance of AI intercepting after special use.
Shuri, sauron, goblins, Maestro sp-1 (if you dex all beams), Doom sp-2 (rare) storm.
Any hero with last hit as beams have high chance to light intercept.
The recovery is tuned up by Kabam, even some heavy animations are getting cancelled consistently.
If Kabam didn't tuned up then AI simply have upgraded itself.
Irritating is action cancel and counter, even dexing and counter. Taking the fun out of the game.
Also if someone can provide a video (just upload to YT and post the link here) then that would help the process a bit in figuring out where the bug is happening.