**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Parry Possibly Not Always Firing?
![DorkLessons](https://us.v-cdn.net/6029252/uploads/avatarstock/nFJOR7BII1BIJ.png)
Just wanted to throw this out there and see if others are experiencing the same thing. Pool your thoughts, links, and footage here so the team can have a look and help get this resolved if there is in fact a problem. Thanks all!
https://youtu.be/TGB3UMAkzDA
![](https://img.youtube.com/vi/TGB3UMAkzDA/0.jpg)
24
This discussion has been closed.
Comments
its only map 4. can't remember the opponent but it was the node right before the punisher on the left hand side of today's AQ. There was only global buffs on the champ (Iso-Infused 25% attack and health). This is not a node that should have had such consequences.
I don’t have footage or a solid grasp on it, but I do feel it’s happening more versus higher PI opponents. Eg Sinister in this months’s uncollected. I tend to file it away under ‘you probably aren’t used to fighting this champ’ yet, but it is real weird.
If a fight starts off like this, I often revert to intercept only. I just know that if it happens once, it’s likely to happen again.
iPhone X. WiFi. Fairly end game player: Act V done, first LOL run done, First Variant chapter explored, did one run through the others.
Please address this, and not just close the thread. I’ve experienced the same thing, but don’t have access to the resources to illustrate it like Dork lessons. Thank you in advance, and hope you folks have a good weekend. 👍😁
borntohula - when I faced Emma in this month's EQ I swore I must of missed that she was stun immune. Tried a second character, same thing. I didn't get a parry until my 3rd fight with her.
Plus, another annoying thing is that in harder contents, kabam will speed up the enemies' animation (yes kabam, we can see this) so maybe parries not working have got something to do with that.
https://forums.playcontestofchampions.com/en/discussion/comment/721270#Comment_721270
If it was intended, I question if Kabam should be transparent about these types of AI changes. When we are doing thousands of fights, the skilled and experienced, can intuitively tell when something is off. At first we may question ourselves, and possibly automatically adjust, but *IF* Kabam is slowing making changes to basic mechanics (to possibly increase difficulty - admittedly inconclusive if and why), and as the tolerances decrease enough, we will notice. It's just annoying and frustrating to go though the initial doubt phase to eventually arrive at the reality, and then have to put together the evidence.
I've always wondered if there should be an AI difficulty indicator of sorts. Going by champion rating/PI alone isn't enough to gauge fight difficulty.
I kid you not - I thought she was immune until I somehow accidentally got a parry in. I forgot about the fight, because it was so easy. But, yes, exact same experience. I just fought her as if stun immune.
THANK YOU!! :-)
Thanks again for the video. The team has taken a look at it and wanted to share some insight. As you know, Parry is very timing specific and the timing window to activate it is extremely small. How it works is that after the player presses block, a small timing window begins that will allow Parry to trigger. If an attack is blocked during this very small window, the Parry will activate.
To prevent spamming block to activate Parry without skilled timing by the player, another short timer is in place that will not allow Parry to activate if the player blocks again within that window.
The very specific timing required to activate Parry is why you may see results like those in your video.
Hope that helps to explain!
I've been playing for 3 years, and I've never seen this caveat.
I do believe it's important to add information like this in the ability description. I mean... this is a HUGE difference maker.
Example, parrying IMIW like this wouldn’t have been possible with older timings for ”the window”.
you guys are making parry impossible it doesn't work like it was how can someone parry twice in a row ?
the timing has been reduced to some crazy low windows how can players like dork not be able to land succeful parries it's been changing every now and then with no head up
also the android framerate makes it way harder to put a succeful parries in and some new champs dashes are crazy fast
This is the opposite of transparency. The window was changed. Admit it, look at if it was changed too much, and we all can move on.
This generic response does not make sense and ignores the fact we've successfully used parry for years. It has now fundamentally changed. Based on your generic response I also suspect that a silent nerf on parry has taken place. Sad
The fact that you directed the response to Dave is comical. They man literally taught thousands of players how to successfully parry in a video almost 3 years ago. haha
Thanks for the rapid response, Lyra.
This attempt to avoid unskilled spamming of block would be fair enough if mcoc hadn’t become so extremely laggy or if controls weren’t randomly being unresponsive too frequently (taps for blocking, dash attack or dash back not registering at all which leads to multiple, increasingly frustrated taps). If a player is skilled enough to adjust block to account for lag (or for the weird stutter step the AI has introduced - which is itself another issue) they get penalised. If the game is dropping frame rates the player gets penalised. The game is responsible for the lag, frame rate drop (or stutter step) in the first place. The team need to have a closer look at this and develop some way to make this work for the players because the recent changes are not working for us. It’s no good developing the game for ideal conditions when almost your entire player base is not experiencing anything close to those conditions. And yes I am blaming lag, frame rate for this situation but that might not even be the most salient reason this is not working, not even for the most skilled members of the community.
But WHEN WAS IT CHANGED. You nicely skirted that issue.