**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 Parry Bug
benjamin_lee
Posts: 37
When is this bug going to be fixed? I'm referring to the bug where he can parry while in the middle of blocking a combo.
0
Comments
They did fix modok, now he doesn't callout that much. They really know how to differentiate the real bugs from the irrelevant ones.
Nope. Two things:
1. His auto block triggers on the first hit. Upon that first hit, he goes into blocking mode. This is not supposed to trigger parry (it is in his description), and he is indeed not triggering parry on this first auto-block. This is not a bug and not what I am referring to.
2. What I am referring to, is the subsequent hits after his auto block triggers. Namely hits 2, 3, 4 and 5. It appears that occasionally, while hitting MODOK on his block, you can suddenly get parried on hit 2 or 3 for instance. This is a bug given that he is holding block the entire time and that is no different from simply beating on another champ's block. The game somehow allows MODOK to drop and re-block in a split second in between your first and second hits, which is simply not possible within the game mechanic. This is the bug I am referring to.
Fixed it for you.
It's not a bug it's the addition of the mastery. It is working as intended.
Not at all. How can he be timing a block well when he's just holding block throughout? It's a bug.
he sud not parry us after 2 3 or 4 hit.... which he is doing....
sinc the new season started and every kills count.... kabaam need to fix this bug...
this is not legit.... sinc one of toughest defender and it bug makes him more tougher.
Or you could explain why you haven’t even acknowledged this major bug
So... if you acknowledge it is a bug .... whats the update?
I always use bw when I see a modok in aw but even she can be parried sometimes. This is quite an annoying bug.
Here is the real bug demonstration, pay attention that he parry me on red shield without changing mode (slow motion):
https://youtu.be/uVPiemrK4_g?t=9m4s
Me and many other players reported this issue many times, it haven't fixed yet and I hope it will be fixed soon
Fun fact: not everyone has a max Sig 4* BW