UPDATE: A new Hotfix (v32.2.3) is now being released to address this issue. Please keep an eye on your App Store for this update to address the below issue.

We are currently experiencing an Error when Summoners view a Champion’s Synergies while in the Champion Selection screen in Arenas and Duels. We are aware of this issue and are working on a Hotfix to address it. In the meantime, please avoid using the synergy menu to prevent this error and crash. We apologize for this inconvenience. Updates will be posted here: https://forums.playcontestofchampions.com/en/discussion/293506/error-when-looking-at-synergies-from-champion-selection-screen

Is the Unity engine update the source of all the bugs?

Recently Kabam announced that they would not support some older Android and IPhone version. This was most likely caused by an update of the Unity engine.
Could all the bugs introduced by the most recent update (lags, auto dash after sp3, etc...) be caused by this?
If so, why Kabam didn't let us know they would do this major update with this version of the game? Knowing the changes on the Champs is good but I feel this should also be part of the change log

Comments

  • Colinwhitworth69Colinwhitworth69 Posts: 4,186 ★★★★★
    Kabam has said this was related to the game engine update. Been covered here in a few threads.

    I believe the game engine was updated and it did not work well with the parry/dex behavior in MCOC, and they have been working this problem.

    I am not sure what you are asking about in terms of the Changelog.
  • Colinwhitworth69Colinwhitworth69 Posts: 4,186 ★★★★★
    Chitlins said:

    Kabam has said this was related to the game engine update. Been covered here in a few threads.

    I believe the game engine was updated and it did not work well with the parry/dex behavior in MCOC, and they have been working this problem.

    I am not sure what you are asking about in terms of the Changelog.

    This post is two and a half years old.
    LOL. (thanks)
  • thanks4playingthanks4playing Posts: 706 ★★★
    Considering that some random player was able to pick up on this 2 years ago, I wonder what the internal roadmap/strategy has been to address this issue. Certainly Kabam knew this far earlier so that they had ample time to allocate resources to mitigate the problem.
This discussion has been closed.