Dexterity is just as bad, if not worse, than the parry issue for me now.
Best way to describe it is that the champion you are controlling is wearing a lead suit and they simple don’t want to move. I need to almost drag my thumb completely from one side of the screen to the other before the champ will think about moving back. Performing this in real time during fights is impossible, I’ve simple gone in to some very easy fights with a good champion and practiced at the side while they try to do damage.
The whole left side of the screen mechanic has completely changed. Dex / parry / simply moving back is now a nightmare.
Edit: I’m on iOS, iPad.
Edit x 2: just noticed Kabam have commented and closed another similar thread and redirected to here. Any chance they can update us here if they have time to comment on threads they’re closing? Thanks.
This is gonna be an EXTREMELY unpopular opinion…yeah. This is gonna be extremely unpopular, but just my opinion:
IF IF IF the parry window has been tightened, it will hurt the game in the short term, because we are all used to it. But at the same time, I think we’re at a point in the game’s history where a conversation might need to be held about whether parrying into stun might be hindering a chunk of the player base as too much of a catch-all to beat content
I don’t want a game of stun immunity or shrugging off debuffs every single second of the day, but when you see how skilled players are still crushing most/all of the hardest content, I wonder what the answer is to make content that is accessible to everyone yet still challenging
If it were me…maybe I would tighten the Parry window
That only works if they quit messing with things to let the timings for everything be consistent for extended periods (think yearly and 2 Acts of God + his handlers to change anything game mechanics that's not a clear bug) and work on unbreakable performance.
I can’t really record it because I only have one device but I don’t think the issue is with the mechanics of the game, I.e. dex and parry but rather with the response time. If you watch the characters response time from your inputs it looks like there’s a delay between touching the screen and the character responding, about a quarter of a second.
Want to confirm that we are investigating this on our end. If you have the time and the answers to the following questions, it could help us find the root of the issue.
When did parry fail when previously it wouldn't? Was it an early parry? a late parry?
What were the effects of parry failing? Did you get hit into the block? did you not block at all and get hit instead?
Did you see the character block before you took the hit?
Do these parry issues occur when you try to re-parry or the first-time parry?
Want to confirm that we are investigating this on our end. If you have the time and the answers to the following questions, it could help us find the root of the issue.
When did parry fail when previously it wouldn't? Was it an early parry? a late parry?
What were the effects of parry failing? Did you get hit into the block? did you not block at all and get hit instead?
Did you see the character block before you took the hit?
Do these parry issues occur when you try to re-parry or the first-time parry?
Ive seen it as more than just parry. Blocks in general. Not registering my finger holding block so my champ just walks at the opponent. Blocking sp1 of Punisher 2099 but the block doesnt happen so it looks like I just took the whole special. A few times Ive went to use dexterity and it registers the touch but not the dash so I block instead of dex. Then(my favorite one) when I did get a parry off with Silver Centurion and went to heavy to apply a slow the heavy just kept charging even though I pulled my finger up so I just got clapped when the stun wore off. Its definitely a general dropped input issue and I have an iphone 12 pro so it isnt like a hardware issue.
Dex feels delayed after the update, often if I try to dex the opponents medium when they dash in, instead of dexing I will just block instead. Then once I have blocked, everything still feels delayed so I am unable to dex away from the following attacks and it is hard to get a re-parry.
iPhone 8, same problems here, just came on to see if it has been talked about, a few alliance members noticed it too, Im also having trouble dexing, it keeps parrying instead, I have to dex much earlier for it to work, and just keep taking hits to the face when I’m blocking, just had to bow out of incursions, it’s the worst I’ve seen the game play in 5 years, it seems laggy as well, keeps dropping frames, the missed blocks maybe something to do with lag when buffs and debuffs are coming up on screen, I seem To notice lag when that happens
Also I’m seeing that when I do dooms l1 into l2, the defenders are firing a special at me before I can get the l2 off, this has never been an issue before now, some Timing is way off
This problem ruined my progress in quest. I updated game when I was in the middle of 6.2.1 exploration and after that I continue but due to this problem my whole crew dead. Then I quit quest reinstall game try again but result was same. End of the story -> energies, potions, progress and time gone waste...
Dex feels delayed after the update, often if I try to dex the opponents medium when they dash in, instead of dexing I will just block instead. Then once I have blocked, everything still feels delayed so I am unable to dex away from the following attacks and it is hard to get a re-parry.
Running on IOS.
Most of the last update I've had parrys sticking on the second hit of the combo, far too many times for comfort and has cost me dearly on many occasions, my question to kashscam is, why is a forced mastery so inconsistent? Why am I now forced to have a mastery that once had disabled as I was amazing at dexing and evading and enjoyed having dexterity unlocked whilst having other points on far more efficient and effective masteries, why have you burdened us with a mastery that hasn't worked 100% for at least 2 years? Know why? 🤑 greed, players who can dex well don't need to rely on parry to play well, now players who try to dex parry instead and players who parry get beat upon, it's nothing more than kashscams way of ripping the players off even further! I despise the company with a passion unfortunately I do love Mcoc and truly wish marvel would see sense and remove these reprobates from power and allow a company who values their entire customer base and not just the 'whales' who spend big on their deals, it's went from a fun global multiplayer game to a competition decided on who's got the biggest wallet, true talent will never shine in this game so long as the rich are left to top the charts!
I’m been testing it for the last 15 minutes or so in ROL, using my R3 Emma. iPhone SE.
It feels like the issue is occurring when the opponent is dashing at you. It’s not a consistent issue, the parry won’t always fail. It also doesn’t appear to be a case of mistiming the parry, if that were the case I would expect to do it too early, but every single time it’s failed it’s been a hit to the face.
ESF mentioned it earlier but I think it’s either one of three things or a combination of both
1. The frames between the opponent dashing and actually hitting have been the reduced to the point where there aren’t enough frames for your champion to execute a block. This is the explanation I’m leaning toward since it’s only occurring during my testing on dash attacks
2. An input issue where the time between the parry input being registered and it being executed has increased. However, if this was the case I would expect to see it occurring when parrying a variety of attacks
3. The dash back input command is lasting longer than it was previously on our champ, which is causing parries the parry input to execute later than it should. I don’t think this is the case but knowing that most parries against dashing opponents occur altering dashing back, it’s a possibility. It may also explain some of the inconsistency
All of my theories might be wrong, my only computing knowledge is one year in high school. I should mention that so far this hasn’t affected my regular gameplay, it’s been few and far between for me, which doesn’t seem to be the case for a lot of players
In the mean time while this is being investigated, I would suggest players play very aggressive and don’t attempt to parry dashing opponents. If you can reparry or intercept well they seem unaffected. It sucks, I know.
Want to confirm that we are investigating this on our end. If you have the time and the answers to the following questions, it could help us find the root of the issue.
When did parry fail when previously it wouldn't? Was it an early parry? a late parry?
What were the effects of parry failing? Did you get hit into the block? did you not block at all and get hit instead?
Did you see the character block before you took the hit?
Do these parry issues occur when you try to re-parry or the first-time parry?
- Both late and early parry - missed parry, took combo - Yes, did look like the character was blocking - Not on re-parry, just first up parry
Just quit my incursions run because it was unplayable, no chance of hitting the milestones i want with this issue going on. Hopefully it's fixed before content drop tomorrow
I had no problem completing 10 rooms of sector 8 an hour or so ago.
Are you trying to get banned?
Why? I'm just commenting my experience.
No you aren't. You are purposefully antagonizing people and belittling their experience. I am not experiencing what they are either and I have posted a video showing that parry seems to be working just fine for me. That doesn't mean it's not working or something isn't working for others. There are some legit concerns with this as you can see in the few videos that were posted.
No I'm not. I could say the sky is blue and someone would disagree and get upset. I can't control people's reactions.
You sure about that?
This is a relevant piece of info for players and Miike. An answer would be helpful.
Dr. Zola
100% agree with you but I don't think you'll get a relevant answer from him.
I'm running an LG V60, latest game update and android 11. I posted a video earlier and I don't seem to have the issues others are experiencing.
Agreed. It appears to be a mostly/exclusively iOS issue. Which should give Android players something to cheer about.
Dr. Zola
Not so, be careful with those statements, because it can confuse the technical team and leave out android. I am on a huawei p30, android 10 and I have the same problem since the update many people also commented that they have the problem on android. Friends of alliance also same problem and both android and IOS. I don't want to be left out of a solution to the problem for statements like this.
Good point, and I wouldn’t want to muddle the issue.
Thank you for pointing that out—initial reports here and from a few other chats I follow indicated the issue was mainly and iOS one.
But your experience indicates it’s broader than just iOS—I appreciate your clarification.
For all users, I hope they get it fixed before the content drops today. I have no interest trying to learn a new timing for all of the game’s basic movements in the middle of SoP.
At a minimum, some form of concession should be in the works, especially if AW/AQ continue under these circumstances.
All I do in this short clip, is try to parry. Nothing else. And really concentrated. On latest ipad Pro. In arena, should be spot on. These are just a few, but some fights, it’s five or more in a row. Playing since launch, all end game content done.
Forgive me if this has already been mentioned as there are way too many posts to see if it has already but, funny thing is, in the “Parry Tutorial”, it largely works the same as before. Much different from current actual live gameplay. Whatever settings you (Kabam) have for that, why not just copy back over to live game? Unless intentional? Maybe a bug but I’m pretty confident that one of our main ways of defending wouldn’t be compromised by applying to it a general “ID” or “class” name in the code. Maybe just target the parameter that changed parry in the first place? May not need to be a build-altering change. Just a thought. Could be wrong though.
Want to confirm that we are investigating this on our end. If you have the time and the answers to the following questions, it could help us find the root of the issue.
When did parry fail when previously it wouldn't? Was it an early parry? a late parry?
What were the effects of parry failing? Did you get hit into the block? did you not block at all and get hit instead?
Did you see the character block before you took the hit?
Do these parry issues occur when you try to re-parry or the first-time parry?
1) Late-ish most of the time, but I think I had 1 or 2 early ones. 2) Block didn't work, got hit in the face into oblivion. 3) Nope 4) First time, didn't try re-parry.
OH man, wish I had check the forum before burning a dozen of revives cos I was too lazy to start all over.
I’m sure if one of the developers plays the game they will be able to notice the issue going on. I’m not being a developer myself and someone who just plays not easy to articulate the technical issues or how to explain them but simply playing the game one can tell that it is not working like it was working before the update. I would think game developers and who developed how it works would be able to understand the mechanics of why it’s not working or how it’s not working more than the average player.
Comments
Best way to describe it is that the champion you are controlling is wearing a lead suit and they simple don’t want to move. I need to almost drag my thumb completely from one side of the screen to the other before the champ will think about moving back. Performing this in real time during fights is impossible, I’ve simple gone in to some very easy fights with a good champion and practiced at the side while they try to do damage.
The whole left side of the screen mechanic has completely changed. Dex / parry / simply moving back is now a nightmare.
Edit: I’m on iOS, iPad.
Edit x 2: just noticed Kabam have commented and closed another similar thread and redirected to here. Any chance they can update us here if they have time to comment on threads they’re closing? Thanks.
If you watch the characters response time from your inputs it looks like there’s a delay between touching the screen and the character responding, about a quarter of a second.
Running on IOS.
To notice lag when that happens
Timing is way off
I’m been testing it for the last 15 minutes or so in ROL, using my R3 Emma. iPhone SE.
It feels like the issue is occurring when the opponent is dashing at you. It’s not a consistent issue, the parry won’t always fail. It also doesn’t appear to be a case of mistiming the parry, if that were the case I would expect to do it too early, but every single time it’s failed it’s been a hit to the face.
ESF mentioned it earlier but I think it’s either one of three things or a combination of both
1. The frames between the opponent dashing and actually hitting have been the reduced to the point where there aren’t enough frames for your champion to execute a block. This is the explanation I’m leaning toward since it’s only occurring during my testing on dash attacks
2. An input issue where the time between the parry input being registered and it being executed has increased. However, if this was the case I would expect to see it occurring when parrying a variety of attacks
3. The dash back input command is lasting longer than it was previously on our champ, which is causing parries the parry input to execute later than it should. I don’t think this is the case but knowing that most parries against dashing opponents occur altering dashing back, it’s a possibility. It may also explain some of the inconsistency
All of my theories might be wrong, my only computing knowledge is one year in high school. I should mention that so far this hasn’t affected my regular gameplay, it’s been few and far between for me, which doesn’t seem to be the case for a lot of players
In the mean time while this is being investigated, I would suggest players play very aggressive and don’t attempt to parry dashing opponents. If you can reparry or intercept well they seem unaffected. It sucks, I know.
Thank you for pointing that out—initial reports here and from a few other chats I follow indicated the issue was mainly and iOS one.
But your experience indicates it’s broader than just iOS—I appreciate your clarification.
For all users, I hope they get it fixed before the content drops today. I have no interest trying to learn a new timing for all of the game’s basic movements in the middle of SoP.
At a minimum, some form of concession should be in the works, especially if AW/AQ continue under these circumstances.
Dr. Zola
https://youtu.be/c1tXd5pIhJ8
Unplayable, really.
I certainly won’t be playing anymore until this is fixed. It’s like learning a new game which doesn’t work properly.
Regards
2) Block didn't work, got hit in the face into oblivion.
3) Nope
4) First time, didn't try re-parry.
OH man, wish I had check the forum before burning a dozen of revives cos I was too lazy to start all over.