A RECENT DEVELOPMENT ABOUT THE AI
MCOC Team
Administrator, Admin [en] Administrator › Posts: 595
Greetings Summoners!
Getting right into it, some of you may have noticed (and communicated with us), the defender AI has been extra slippery since the last update. This was not an intentional change, and because Marvel Contest of Champions does not use a true artificial intelligence, this was also not a result of any learning systems. This meant that it took us some time to isolate the problem, unfortunately. As you may know, we did make a change this month to prevent defender re-parrying, and we were and remain 100% confident this was not the cause of the issue. Without getting too deep into it, that change only shows up after defenders block an actual hit. The problematic behavior we observed, however, was occurring before that point. So what was the issue?
Fortunately, we believe we did find the problem, and rolled it back as of Tuesday at 3:30 pm PST (10/16/2024). From our own testing and from feedback gathered from our most engaged players, we’re confident the AI has been restored to where it was last month (leaving intact the fix to re-parry). That all being said, this doesn’t mean we think we’re where we need to be - this is an ongoing area of improvement for us - but feel confident in the rollback.
As a result, we had to replace some code that was intended to future proof the system. For now, we wanted to update you that we isolated the issue and fixed it. Stay tuned for more updates in the future as this is an area we have a keen eye on. Kindly bear with us as we iterate through this as this task is challenging and will take some time.
Getting right into it, some of you may have noticed (and communicated with us), the defender AI has been extra slippery since the last update. This was not an intentional change, and because Marvel Contest of Champions does not use a true artificial intelligence, this was also not a result of any learning systems. This meant that it took us some time to isolate the problem, unfortunately. As you may know, we did make a change this month to prevent defender re-parrying, and we were and remain 100% confident this was not the cause of the issue. Without getting too deep into it, that change only shows up after defenders block an actual hit. The problematic behavior we observed, however, was occurring before that point. So what was the issue?
Fortunately, we believe we did find the problem, and rolled it back as of Tuesday at 3:30 pm PST (10/16/2024). From our own testing and from feedback gathered from our most engaged players, we’re confident the AI has been restored to where it was last month (leaving intact the fix to re-parry). That all being said, this doesn’t mean we think we’re where we need to be - this is an ongoing area of improvement for us - but feel confident in the rollback.
As a result, we had to replace some code that was intended to future proof the system. For now, we wanted to update you that we isolated the issue and fixed it. Stay tuned for more updates in the future as this is an area we have a keen eye on. Kindly bear with us as we iterate through this as this task is challenging and will take some time.
46