**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Comments
I successfully intercept WS dash when I'm not Unstoppable, but I take damage when i have the buff.
https://streamable.com/f4g0g
Could you leave yourself plenty of room below 750. So then when you start to get to fights with around say 700, before killing opponent you purposely get hit couple times far enough apart that stretches beyond the Combo Guard timeframe. Then finish off opponent with having a very low final Combo for the fight (like 5-10 hits max).
And thus avoid actually reaching that 750 trouble spot.
I have just made the 5th path of the lol, Aegon is still bugged!
I lost many many health points (and then revives) uselessly due to this issue!
Please find a fix, but of course refund all of us for this inconvenient!
We have confirmed that this bug exists, and have created a fix for it. It is not only Aegon, but as some have mentioned, also affected Hulk (Ragnarok) and others.
It does require a new update though, so this will be fixed in an upcoming release.
https://forums.playcontestofchampions.com/en/discussion/11/marvel-contest-of-champions-changelog#latest
So they'd either have to do another mid-month Update, or it might be something they’re just gonna wait on until next month. (??)
Thanks kabam, I wonder if there will be anything left in the stash by the time this is finally fixed.
Add annihilus as another champ being affected by this bug.... probably make kabam push a fix out even longer knowing they've got even more players bent over now.
I have another update! It looks like there is something that can be done to fix this without a new update. This will mean that the original bug fix (RHINO: Will now correctly hit opponent if intercepted while performing a Medium Dash Attack with Unstoppable.) will be reverted, but this seems like the lesser of two evils.
We'll deploy this fix later today, and I will update you all as soon as I know it's happening.