**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
It's possible that's it's really not even a true bug but just how the performance of the game engine works and we're not used to it. On top of being a core process, you have 100's of different devices spec'd out in different ways that you have to program the game to work with. None of this is easy. It's completely unfair for you to say someone should be fired when you don't even have clue in how to do thier job. You don't even understand the basics.
https://forums.playcontestofchampions.com/en/discussion/274203/gameplay-issues-fix-timeline#latest
"we believe that a recent update to our game engine is the cause of the problems that players are experiencing"
"Making those improvements will be a lengthy process where we will be overhauling a large part of the game to work with this engine update." MCOC Game Team
https://forums.playcontestofchampions.com/en/discussion/276481/update-gameplay-concerns-affecting-parry-and-dexterity#latest
"The assumption you've made is that this is somehow an easy thing to identify or fix. Neither of those things is true."
"In this case, we believe it may have something to do with our Game Engine update, but can't say that for sure yet. That is something that touches literally every aspect of the game, so identifying what that could be is not something that can be done very quickly." Kabam Miike
https://forums.playcontestofchampions.com/en/discussion/comment/1851054#Comment_1851054
I mean, if you call reading what Kabam say and basing an opinion off the facts they give, sure, I'm guessing.
Parry_timing = broken
Oh, I'd better fix this code
Parry_timing = fixed.
It’s been completely random when, where and how often it happens.
The AW/AQ compensation has more than covered issues I have faced in that content.
Almost no trouble in AW. AQ has been bad at times.
I had serious trouble against sop grandmaster, dex randomly wasn’t working. Controls in the fight felt really unresponsive. Cost me quite a few revives.
But I'll tell you what I do believe, a game team representative who is informing us on the status, cause and complexity of a bug that kabam have no benefit to keep in game any longer than it takes to say "conspiracy theory". I believe them, because they have no reason to lie. What benefit could Kabam possibly have for keeping a bug in the game? Annoyed players, reduced spending in the short and long term, but hey, at least a few players bought a few revives?
Different spellings I assume result from conversion from Old English.
And I urge the team to send relief so we can move on to clogging the forums with threads debating its sufficiency/ insufficiency.
Dr. Zola
I’ve seen numerous threads asking precisely this—calm, polite, reasonable—either go missing or pigeonholed somewhere else on forums.
It seems like simple courtesy to respond and say whether there’s a date or a changed timeline, or whether the date is dependent on something else.
It really would be appreciated if they were willing to clue everyone in a little.
Dr. Zola