Quake AI Whiff Bug [Not A Bug]
DrZola
Member Posts: 9,419 ★★★★★
I’m experiencing an issue with the AI against Quake I haven’t seen before. The standard strategy with Quake is to charge her heavy, let autoevade save you from the AI’s first attempt at hitting you and then parry the second. Rinse and repeat.
However, with Stark tech champs as well as a couple of others, I’ve noticed that on the second attempt to hit Quake (after the auto evade), the AI simply “whiffs”—meaning, it throws an artificially short punch and doesn’t make contact with her block. Visually, it looks like the AI swings in place without moving forward.
This is important because if the AI can’t make contact with her block, she can’t parry and start the heavy charging cycle all over again. And more importantly, the third attempt to hit by the AI doesn’t trigger her auto evade, meaning she is likely to get hit by the third attack.
Charging the heavy with auto evade on the first attack and the ability to parry the second (excepting Drax, true strike champs, and Iceman under Coldsnap, all of which bypass the autoevade) is central to using Quake. Any diminishing of that ability alters her usefulness greatly.
Obviously, this is a big issue for me—I have both 4/5* Quake on my profile. If her mechanics are broken, they need to be fixed. If it was intentional, then the game team should have made that known openly and Quake owners should be given some relief.
Dr. Zola
However, with Stark tech champs as well as a couple of others, I’ve noticed that on the second attempt to hit Quake (after the auto evade), the AI simply “whiffs”—meaning, it throws an artificially short punch and doesn’t make contact with her block. Visually, it looks like the AI swings in place without moving forward.
This is important because if the AI can’t make contact with her block, she can’t parry and start the heavy charging cycle all over again. And more importantly, the third attempt to hit by the AI doesn’t trigger her auto evade, meaning she is likely to get hit by the third attack.
Charging the heavy with auto evade on the first attack and the ability to parry the second (excepting Drax, true strike champs, and Iceman under Coldsnap, all of which bypass the autoevade) is central to using Quake. Any diminishing of that ability alters her usefulness greatly.
Obviously, this is a big issue for me—I have both 4/5* Quake on my profile. If her mechanics are broken, they need to be fixed. If it was intentional, then the game team should have made that known openly and Quake owners should be given some relief.
Dr. Zola
Post edited by Kabam Wolf on
5
This discussion has been closed.
Comments
Against modok, Hyperion,Thor and Jane foster Thor
In open spaces their second attack after quake evades always whiffs
Which throws me off game
It begins to work right when I'm backed into a corner
To date, I’ve noticed it against Thor, Ultron, IM, WM and IP. I suspect something happens to her hit box or to the length of the hit by the AI after she autoevades.
Will upload a few videos as soon as my system stops glitching. @Kabam Miike @Kabam Vydious is there any way you can get the team to put this on the list of bugs under investigation?
Dr. Zola
Edit: found some, but of course when I'm recording it won't do it.
I actually have the Thor example recorded now. But for some reason I can’t get it onto forums post.
Dr. Zola
The result is a lost chance to re-parry. He fails to move forward at all, which he would need to do to make contact with Quake or her block. It looks like a spacing-hit box issue to me, but I can’t be sure.
Dr. Zola
That means it has been noticed. Any chance we could get a comment on this from the team now that you know it exists?
Dr. Zola
Dr. Zola