**WINTER OF WOE - BONUS OBJECTIVE POINT**
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
There is currently an issue where some Alliances are are unable to find a match in Alliance Wars, or are receiving Byes without getting the benefits of the Win. We will be adjusting the Season Points of the Alliances that are affected within the coming weeks, and will be working to compensate them for their missed Per War rewards as well.

Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.

Memory Leak

Rogue42Rogue42 Posts: 1,006 ★★★
C’mon Kabam, just admit there is one and you’re trying to fix it. Please tell us you’re trying to fix it. After this last update, the longer you play, the worse game play gets. The load times increase and the frame rate drops. If I force close the game and restart it, it plays (mostly) fine. If you don’t know that you have a memory leak then you need to fire your QA guys.

Comments

  • Hi Rogue42,

    If you are having trouble with low memory issues while playing Marvel Contest Of Champions please see our Knowledge Base for Android Troubleshooting steps.
  • DaMunkDaMunk Posts: 1,883 ★★★★
    LMAO..of course... check your connection too!
  • Rogue42Rogue42 Posts: 1,006 ★★★
    Is there one of those guides for iOS?
  • edited April 2018
    You can find our iOS Troubleshooting Guide here. If the issue persists, please reach out to our Support Team for further assistance.

    To assist our team in determining a cause as well as a possible resolution, please include the following information when submitting a Bug Report:

    Device:
    Operating System:
    Issue and any available screenshots:
    Is the issue repeatable? How?
    Specific location the issue is occurring?
    Troubleshooting Steps Taken to attempt to resolve the issue/results:

    Our QA team is constantly reviewing the forums and bug reports, and working to resolve issues that are reported here. Thank you for providing as much detail as possible!
This discussion has been closed.