Lagacy, Karate Mike, they make far too much money with Kabam. In turn, they’ve sold their souls. I’ve unfollowed them.
I’m surprised Vega said something. Gained a lot of respect for him on that.
I think this is a bit of an unfair comment. I’m not a huge follower of Lags but he does speak up for player perspectives on plenty of occasions, just like Vega. Remember the Serpent petition? I think for both creators where they have so many friends in and around the game team it’s only human nature that they’ll be more charitable.
As for KarateMike, it was a bit of a bizarre middle ground there for a bit when he was but wasn’t working for Kabam. Now that he is officially a member of the team, I think he’s been doing an awesome job as part of the community team. He brings that positive attitude and wit in his communications and I’ve seen him weigh in on the forums more than once outside of normal business hours on our concerns.
And I’ve heard both make negative comments about the trajectory of the AI. I’m sure they are giving the feedback they can on this issue because of how it impacts their bottom lines in addition to their enjoyment of the game.
What is getting me the most is the AI not following up my dash back with a dash forward after a strike, but it starts spamming light attacks when I'm wildly out of range already. If I try to backdraft light intercept it catches me every time.
The thing thats personally destroying my time in GC right now is the re-parries. I can't even explain to you how frustrating the re-parry problem currently is. The window from which they are able to do it is like the mathematical version of the limit of a function from which the time required to parry approaches the limit of the parry window or something of that affect. Its brutally discouraging and when it happens, the match is just over.
Backwalk parried, parried when the defender was recovering from a heavy or special, and parried when the defender didn’t even have a frame to throw up his block, check, check, and check. But no more reparries at least.
With all the bugs, glitches, and recovery times out of heavies and specials, I can’t believe no one is talking about it.
We as players, when we let go of block, there is a delay before walking forward. To move forward before this, a player has to dash forward. Obviously, we cannot block once we dash.
AI just lets go of block and prances on down the road? Can block, retreat, or dash?
How the AI can now do this in all game modes is utterly scandalous.
I mentioned this and even provided a video and nothing happened 🤣
We have a solid half second delay when there are zero inputs before we walk, the ai let's go of dash and walks instantly. It's ****
My brain sees the ai go from block to moving towards me and I assume dash and then get light intercepted 😭
The most annoying thing to me is Bullseye. He does not want to be intercepted by me and does constant shallow dexes, but whenever I put Bullseye on defense, the opponent takes him out in 30 seconds.
Thing and onslaught are extremely passive. I wish we just got crit me node and not the crit interruption one, so the damage will depend on base crits and no need to intercept.
Thing and onslaught are extremely passive. I wish we just got crit me node and not the crit interruption one, so the damage will depend on base crits and no need to intercept.
Thing and onslaught are extremely passive. I wish we just got crit me node and not the crit interruption one, so the damage will depend on base crits and no need to intercept.
Got to chime in - had an Onslaught that just kept walking up to me. I know that AI wants to hit my block (well a Kabam post recently stated no AI is actually programmed differently for each champ but experience says differently)...but the **** also wouldn't throw specials. Just got pissed off and sent him to sp3. Luckily my opponent had worse luck lol.
With all the bugs, glitches, and recovery times out of heavies and specials, I can’t believe no one is talking about it.
We as players, when we let go of block, there is a delay before walking forward. To move forward before this, a player has to dash forward. Obviously, we cannot block once we dash.
AI just lets go of block and prances on down the road? Can block, retreat, or dash?
How the AI can now do this in all game modes is utterly scandalous.
I mentioned this and even provided a video and nothing happened 🤣
We have a solid half second delay when there are zero inputs before we walk, the ai let's go of dash and walks instantly. It's ****
My brain sees the ai go from block to moving towards me and I assume dash and then get light intercepted 😭
That constantly pisses me off - the fact we are animation/frame locked. I should be able to throw my special whenever I want. There are times it is forcibly greyed out and these are not when the AI throws their own. The attacker is forced to wait out certain recovery animations the AI can somehow skip. Our specials and movement buttons are locked for a millisecond or 30 after each action. If frames are being dropped why not both ways?
I hope Kabam rectifies this soon. It is so frustrating dealing with this AI. Pair that with characters who power gain and or are unblockable, they just sp me to oblivion. Constant parries, constant dexes, random walk ups, light intercept is crazy, recovery time from being knocked down or coming off a special is ridiculous and always lands me in a 5 combo, BONUS idk if this happened to anyone else ( I could just be tripping having PTSD from this current AI lol) but I’ve been parried while unblockable recently and had my relic get parried after sending it out from a 5 combo lol I was so dumbfounded
1. Constant 'defensive' AI where defender dashes back and holds block, dashes back and holds block, dashes back and holds block. 2. This makes intercepts difficult (both standard intercepts and light intercepts) because opponent is hardly ever rushing in, and never in a reliable way, therefore making champs that depend on intercepts essentially useless. 3. If defender has enough power for a special, you canNOT attempt to rush in, even when all they're doing is dashing back and holding block, because they WILL throw that special at you. 4. Even if defender does not have a full bar of power, if you dash in there's a 50% chance they will light intercept you and you'll eat a combo to the face. 5. Defender has unrealistically fast recovery time, resulting in being able to attack in ways they shouldn't or faster than they should be able to. They have no recovery window and it really screws with how you're able to play against them.
What else we got? And, to note, these issues are occurring throughout the entire contest. They're just extra egregious and notable in BGs, which is ridiculous and frustrating especially because they WANT us playing BGs with the Realm event incentive.
Because the problems aren't *just* in BGs and are across the board in the game? Cause that's the ONLY way your statement has any truth to it.
The post was talking about the ai in GC . So yeah my reply was to that.
But even then, other than the occasional ones like the original sos onslaught and the toad fight not throwing specials(didn't face too much trouble this time) ,I usually don't face any egregious AI issues
This AI issue feels like the Burning Man of MCOC right now. Kabam keeps tweaking the AI to drain revives, then comes out saying the opposite. Should I trust what they say or what I actually experience—how the AI perfectly intercepts light attacks or when I dash in to intercept, the AI perfectly responds with a light attack and reads inputs with uncanny precision? You can easily spot the difference by watching old MCOC videos and comparing them to how the AI behaves today.
1. Pre-2018 AI (Old AI):
- The AI exhibited more predictable behavior, with less aggressive blocking and backdraft intercepting. - It often left openings for players to perform light intercepts or parry-heavy strategies more reliably.
2. 2018-2022 AI Evolution:
- The AI began to respond faster to inputs, particularly in Alliance Wars and high-level content. - The “light intercept” exploit became less effective as the AI frequently countered it perfectly. - The AI started performing more backdraft intercepts and reacting mid-combo in ways that seemed too precise to be natural.
3. Post-2022 AI (Present):
- The AI now feels almost too perfect, predicting intercepts and dash-ins with laser precision. - The AI sometimes holds blocks indefinitely, forcing risky plays that can lead to more revive usage. - “input reading” behavior of the AI, where it seems to predict every move (e.g., intercepts, sidesteps) to bait players into making mistakes. - Nowadays, when you don’t block there’s a delay before you start walking. In contrast, AI walks instantly and forcing you to dash forward.
It’s frustrating and suspicious. Kabam have to come to their senses sooner rather than later. We need more transparency.
Comments
As for KarateMike, it was a bit of a bizarre middle ground there for a bit when he was but wasn’t working for Kabam. Now that he is officially a member of the team, I think he’s been doing an awesome job as part of the community team. He brings that positive attitude and wit in his communications and I’ve seen him weigh in on the forums more than once outside of normal business hours on our concerns.
And I’ve heard both make negative comments about the trajectory of the AI. I’m sure they are giving the feedback they can on this issue because of how it impacts their bottom lines in addition to their enjoyment of the game.
Reminds me of
Backwalk parried, parried when the defender was recovering from a heavy or special, and parried when the defender didn’t even have a frame to throw up his block, check, check, and check. But no more reparries at least.
We have a solid half second delay when there are zero inputs before we walk, the ai let's go of dash and walks instantly. It's ****
My brain sees the ai go from block to moving towards me and I assume dash and then get light intercepted 😭
1. Constant 'defensive' AI where defender dashes back and holds block, dashes back and holds block, dashes back and holds block.
2. This makes intercepts difficult (both standard intercepts and light intercepts) because opponent is hardly ever rushing in, and never in a reliable way, therefore making champs that depend on intercepts essentially useless.
3. If defender has enough power for a special, you canNOT attempt to rush in, even when all they're doing is dashing back and holding block, because they WILL throw that special at you.
4. Even if defender does not have a full bar of power, if you dash in there's a 50% chance they will light intercept you and you'll eat a combo to the face.
5. Defender has unrealistically fast recovery time, resulting in being able to attack in ways they shouldn't or faster than they should be able to. They have no recovery window and it really screws with how you're able to play against them.
What else we got? And, to note, these issues are occurring throughout the entire contest. They're just extra egregious and notable in BGs, which is ridiculous and frustrating especially because they WANT us playing BGs with the Realm event incentive.
But even then, other than the occasional ones like the original sos onslaught and the toad fight not throwing specials(didn't face too much trouble this time) ,I usually don't face any egregious AI issues
1. Pre-2018 AI (Old AI):
- The AI exhibited more predictable behavior, with less aggressive blocking and backdraft intercepting.
- It often left openings for players to perform light intercepts or parry-heavy strategies more reliably.
2. 2018-2022 AI Evolution:
- The AI began to respond faster to inputs, particularly in Alliance Wars and high-level content.
- The “light intercept” exploit became less effective as the AI frequently countered it perfectly.
- The AI started performing more backdraft intercepts and reacting mid-combo in ways that seemed too precise to be natural.
3. Post-2022 AI (Present):
- The AI now feels almost too perfect, predicting intercepts and dash-ins with laser precision.
- The AI sometimes holds blocks indefinitely, forcing risky plays that can lead to more revive usage.
- “input reading” behavior of the AI, where it seems to predict every move (e.g., intercepts, sidesteps) to bait players into making mistakes.
- Nowadays, when you don’t block there’s a delay before you start walking. In contrast, AI walks instantly and forcing you to dash forward.
It’s frustrating and suspicious. Kabam have to come to their senses sooner rather than later. We need more transparency.