**WINTER OF WOE - BONUS OBJECTIVE POINT**
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
There is currently an issue where some Alliances are are unable to find a match in Alliance Wars, or are receiving Byes without getting the benefits of the Win. We will be adjusting the Season Points of the Alliances that are affected within the coming weeks, and will be working to compensate them for their missed Per War rewards as well.
Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.
Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.
Modok auto block causing parry [Under Investigation]
THE_Bmanny
Posts: 15 ★
I searched the forum and didn’t find any acknowledgement of his auto block causing parry. In fact, his ability description specifically states it doesn’t cause parry (unlike Medusa). This also only seems to be happening in aw. Not questing (no masteries) or duels. We can handle some bs but getting 1 shotted by a bug is beyond frustrating and expensive. Please advise. @Kabam Miike @Kabam Wolf
Post edited by Kabam Wolf on
3
Comments
What is happening, is that he is removing his own auto-block and triggering his normal block in the middle of your combo. Since it is a well-timed block, it causes parry
This.
Red = auto-block
Blue = regular block
The second block being well timed and therefore triggering parry doesn't make sense. He'd be hit stunned the same as every other champion is while hitting their block. The same logic also applies to stand your ground and parry working together to parry champions with rapid multiple hit heavies like Archangel, Electra, and X-23.
Please see this MODOK fight. you will see how he parry on auto block:
Times:
I will create slow motion video to show it better:
https://youtu.be/oYYqSSNLAi4?t=9m39s
For what it’s worth, also can confirm. Autoblock triggers parry.
I was getting parried in mid combo and for some reason his sp1 was unblockable....lol
He got 11 kills and still had 75% health.
Great for us, it won us the war because they couldn't get him down but not really fair if it's a bug
@Kabam Miike
This video that arni2 did you can see that happening at 8:40
https://youtu.be/IYwSsvHim8o
We are using currently 16.1.0 version, and this fix will be in 17.1 .... so is this means that 17.1 is the next version or is there any other versions also coming in between. When Hela has an bug which was causing a lot of damage to AI through synergies, to fix that issue or bug did we waited for a release? Or it got fixed over night , when we have identified that modok has a bug or issue which is causing damage to our champ , do we have to wait for the next upcoming release.
What is the logic behind this ... I don’t mind fighting with a character which has bugs ... also I can revive, use potions just to beat this buggy character.... but is this the right approach that we all should follow.
I am confused, or I just keep my eyes close and play and act like I didn’t even know what’s wrong with Modok”
Also he's able to use specials while you hit him on the block!
Please, fix this hero.