**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.
Comments
Using a huwai Nexus 6p phone
I’ve attempted to use the 4 combo and a special too and it works 9/10 times, yet in act 5 there isn’t any room for mistakes.
Last week I didn’t have an issue in act 5, yet the new patch brought forth some issues that I was hoping were dead.
Having a special link into a combo and either a) not firing at all or b)firing, they insta block and then attack you as soon as your animation finishes is beyond annoying.
For anyone defending Kabam it’s nothing to do with the nodes or champions, it is a bug clear as simple.
While it's nice that it's finally being investigated, why not sticky this thread so that it doesn't continue to get buried in the forums. This was done in the old forums. In these new forums.... issues under investigation don't get resolved and threads get buried. Don't you want to minimize duplicate threads?
I guess you mean that it's finally investigated again, this issue is old really old and was burried an insane amount of times that it's becoming their mo at this point.
We bring it up, we post images, and videos they put it under investigation the thread gets lost in the shuffle they "fix" it or "investigate" it again then repeats the cycle. Then the administrators act like they've never heard about it before and go we'll bring it to the game team while this thread gets lost and while the "investigation" seemingly goes nowhere.
This happens with numerous bugs and issues, here on these forums and on the old ones and will likely continue to do so until they take the game down and fix the all the issues but that's unlikely to happen according to them so all we can do is hope for a time that all these major bugs and issues are put to bed for good.
Yes , I’m familiar with other combo whiffing issues, previously with daredevil, Starlord, wolvie, deadpool and some others. This does seem similar. Not sure know this is still “under investigation”, I’ve provided 2 videos with solid evidence. They also close threads when they say they’ve pushed out a fix for a problem without even waiting a week or so for customer feedback on if it was actually fixed. I get frustrated with all the bugs too and don’t understand why they don’t sticky Known Issues here in the forums. It seems like they don’t want problems to be known or highlighted here on the forums. I don’t have high hopes that this issue will be corrected anytime soon.
Combo whiffing and freeze frames. Just another day in MCOC.
IPad4
iOS 10.3.3 (latest iOS for this device)
MCOC up to date
No push notification on
Just turned on my device
https://youtu.be/SGSl5DtPKK0
I forgot to mention that the combo whiff happens around the :30 second mark. 4th hit of the combo misses.
"Same news"
To give you an idea why I’m concerned, There’s a thread about nebula bug that is under investigation and hasn’t been responded to for almost a month and she’s still ridiculously bugged, even more than she was last month.
https://forums.playcontestofchampions.com/en/discussion/26664/nebula-and-blade-well-timed-block-under-investigation
Or if there are multiple threads about the same issue, please combine them! This used to happen all the time in the old forums.
Moderator literally just proves what you said.
Constant cycle of kabam smoke and mirrors. Personally I think they just dont know how to fix it.
This is what I call **** microlags. It happens all the time, doesn't matter how short or long is the fight.
It’s hard to please everyone, when everyone is waiting for so long , I appreciate your acknowledgement over this issue and keeping us posted, just give us a time frame or something on which we can hope that things are going to get better soon, hope you understand our feelings as a user. Thanks
Look forward to the upcoming fix.
I'd like to ask that this thread remain open after 16.1 so that we can we can provide additional feedback and ensure that the problem is fixed.