**UPDATE - iPAD STUCK FLICKERING SCREEN**
The 47.0.1 hotfix to address the issue of freezing & flashing lights on loading screens when trying to enter a fight, along with other smaller issues, is now ready to be downloaded through the App Store on IOS.
More information here.
The 47.0.1 hotfix to address the issue of freezing & flashing lights on loading screens when trying to enter a fight, along with other smaller issues, is now ready to be downloaded through the App Store on IOS.
More information here.
Comments
I will be live streaming act 5 ch 3 starting at release. Stop on by for a first look and tips/tricks for getting through this new content
Can you fix the bug I mentioned above?
Hey! Sorry about that! If you send our support team a ticket they can help solve the issue for you.
For clarity's sake, this happened because you entered the Quest while it was still propagating data to the server, so the server thought it was unlocked, but it still hadn't thrown in the new (correct) map with Mordo as a boss.
For anyone else who sees Kang as a boss, just wait a few minutes until Mordo appears as the boss. Once he does, you're good to go.
Thanks and yeah I've already submitted a ticket asking them to re-set it for me but god knows how long I'll have to wait for that or if they will even understand my issue
1.6% x 30 seconds = 100%? #fakemath
Correct. Bane is a passive degeneration and should not trigger Cornered. You also can't shrug it off or anything else like that, but neither can the enemy.
Entered fight just above 1st processing. Healed full regen, ended fight a tick under half. Has to be close to 8k damage done through parry and a block here or there.
I did say including the massive chip damage. I know that a perfect fight would lead to less damage, but how many people block 0 hits every fight consistently?
To clarify that note from the original post: If the global node reduces Mystic Champion attacks by 50%, it only affects YOUR Mystic Champions, not the boss you're fighting.
Cool, thanks for the clarification!
Gotcha. I misread the original announcement to mean that we weren't affected for the boss fight either, so I was confused by the presence of the global node on the boss.
Fights are about as hard as 5.2.6. Using a champ that goes against the node isnt tpo bad it just makes the fight really long. All in all good content and completion isnt too bad
You seriously need to lower the enemy's attack. Is too high.
You can give them more HP, but decrease their attack at least
Lol
You're kidding right? Dormammu is still doing almost 400 a tick which is 800 damage a second. This is ridiculous just had 2 fights back to back on one Dormammu where I got hit 0 times but both died. One was a 5/50 and the other a 4/55.
4* aren't really useless in 5.3, but if you are not bringing in maxed 4* then yes they are not very useful. Even with a maxed 4*, that maxed 4* has to be a really good champion to counter 5.3, so champs like Thor, SW, Gwenpool, Starlord, Wolverine etc. can still manage Act 5 Chapter 3.
5* R4 are definitely much more useful. I have a 5* R4 Iron Man (s58) and 5* R4 Magik (s86) that work wonders in 5.3. Still have to play well though, but at least there's slightly more room for mistakes and enemies get wiped out quicker.
I think this entire chapter is mostly filled with endurance fights. If you can constantly parry or intercept, you should be good, but considering the fights can drag for more than >100 hits with a weakened champion or ~100 hits with a non-weakened champion, there's only so long you can do that before you get sloppy.