Make this game work as it did.
Cuteshelf
Member Posts: 747 ★★★
So tired of the unsuccessful blocks/parries, the huge block damage, the reduced ability accuracy, and all the other stuff that has been getting worse since 12.0.
My alliance is slowly losing team members due to frustration.
Come on Kabam, make this game as fun as it used to be.
My alliance is slowly losing team members due to frustration.
Come on Kabam, make this game as fun as it used to be.
7
This discussion has been closed.
Comments
12.0 was overall a very polarizing patch. I personally enjoy most of the changes and I definitely love all the changes from 13.0 and 14.0. The new AQ system is awesome and AW has become much easier.
As I've said before, I don't have any of these issues with block/evade/parry that others have reported. Obviously there are device specific issues occurring.
The game has essentially destroyed blocking in favor of evading which is often is bugged.
They decimated Dr. Strange and made new champs that go well beyond anything he could ever do after selling crystals which were specifically sold as a way to get one of the most powerful champs in the game.
Quality has been terrible. The number of obvious bugs is unbelievable every time a new and incremental release comes out. We are forced to then buy POTS to continue in many areas because of the bugs. At least drop the unit costs for some of these alliance pots.
1 million summoners claimed the "button"... 85 million downloads or more... that means that only 1.18% of all people who downloaded the game still played it at that point...
Sorry, but all the "good" things they have done recently COULD have been added to a pre 12.0 game to make it better.
The bottom line for me is the game was MORE fun pre 12.0. It's still fun, but not as fun.
Parry itself isn't the problem anyway. The interaction between the momentum/knockback physics and the AI response time is causing problems that didn't exist before. Kabam not understanding the interaction continues to cause more problems.
Now you have to be extremely careful timing five full combo attacks when the enemy is in the corner to ensure the momentum is perfect, or else you risk getting parry scammed and then block hit.
The issue occurs for all devices I've tried, both Samsung and Apple. Samsung S5, Samsung S7, iPhone 5, iPhone 5 SE, and iPhone 6. The problem is not because of the devices.
Here is a video, concentrate when the combo count reaches 25, 40, and 54. Look at how inconsistent parry is after 5 combo hits.
https://www.youtube.com/watch?v=V97xnsXPYRw&feature=youtu.be
Listen, I completed 5.2 100% using one L1 single revive; My champs all died to The Collector my first try. After that I was able to solo The Collector a few times actually. I've done LoL too, and 200k fights. That's all irrelevant.
What is relevant is the consistency of parry is affected by the momentum of regular attacks.
If you take like an hour out of your day and just practice adjusting your timing for parries on ROL winter soldier even though it is slightly more difficult now you can land consistent parries even with opponents against the wall. The only champions that really have inconsistent parries I found post 12.0 was floating champions like rogue but since 13.0 or somewhere around there you can parry properly with adjusted timing even with those champions. You don't take insane block damage since 12.1 unless you are fighting a very inflated champion and that is a skill issue not a game issue. I don't know what you mean by reduced ability accuracy do you mind expanding on that point
We've made a lot of progress on a lot of those issues after they first arose, and as we have said many times, we are continuing to work on other bugs that have come up.
We can't just flip a switch and fix all bugs, as much as we wish we could, so we're going to keep doing this the best way we know how, and that's by looking for the root cause of a problem, finding a fix for it, and then getting that out. Treating the problem, and not the symptom!
Because there are threads open on individual issues, I'm going to close this thread down now.