Faulty AI?...or Hit Box issue? Follow up on my previous post.
Terminatrix
Member Posts: 2,950 ★★★★★
@Kabam Miike says it's the AI. In the video breakdown, you can hear my champ hit the stunned defender. He's NOT MOVING when I hit him. Her heavy hits a STUNNED defender, yet misses at the same time. Make it make sense.
Need some clarity here. This is more than just the A.I.
https://youtu.be/2jwWStKrLqk?si=IlzLly-i0RPok9Kv Post edited by Kabam Miike on
20
Comments
*since cmm's heavy is a single hit attack, the contact is probably just in the middle of the animation. Idk if thats how it works, but that is my guess...
All I could think of was this:
May not have been what he meant to say, but that’s how it came across.
Dr. Zola
Seems like it's just an issue with when CMM's heavy actually makes contact. It isn't until the uppercut and the next frame he actually gets thrown back. In the video it seems like the stun had expired and the AI threw the special just before contact, activating the invincibility frames that specials have.
The AI should not be able to react at the exact frame of stun expiration, if that is fixed, the heavy would land normally.
Seems like a recovery time issue to me.
Also, we don't have Hitboxes in this game, at least not in the traditional sense. This is not a console fighting game, and you cannot apply your understanding of those games to this one. We are a mobile game that exists with the limitations and abilities of mobile platforms.
Btw @Kabam Miike so this is like a problem with the recovery that was too fast and wasn't supposed to be like that? Really trying to understand what the issue is, since now we know the game doesn't have hitbox, which is new to me cause i've always thought that was indeed a hitbox
And btw, the sound for attacks plays even when stuff isn't happening. I've been having a lag issue with my game for some time now. When my game freezes the sound for what should be happening still plays regardless of what may happen when it unfreezes. Thats ontop of the aforementioned issue of the sound still playing even if you intercept the AI midway through their heavy
I’ve had both recently, and both *seem* like AI issues, although they could relate to some of the longer running issues with connectivity/device we’ve discussed.
Thx
Dr. Zola
I've done clean heavy punishes in BGs against single hit heavy attack, and my champ will literally be punching them in the face as they special intercept me. I think what Miike said makes sense, it's just the AI reacting at inhuman speeds.
Part of the problem here is that things can change state before, during, and after animation frames are rendered. So it is possible for the AI to make a decision, change the state of things, but not see the results of that until one or sometimes a couple frames later.
This is actually related to @Kabam Miike 's earlier statement that MCOC does not use hitboxes. A lot of people jumped on that comment as being semantic nonsense, or that Miike was making a useless statement, but in fact, it says something very important. Some people are talking about "hitboxes" but don't actually have any idea what that means, and some people do know what that means but don't seem to fully appreciate what "not having hitboxes" means, like that's just terminology. But it isn't just terminology. It implies MCOC uses Unity collision systems instead.
A hitbox is a form of direct collision detection. In 2D, you would have a "box" drawn around or within a target, and if in any animation frame something else is drawn in that box that's a collision. In 3D it is the same thing but with three dimensional bounding boxes.
But is this a collision?
Ignore the light trail as that is VFX and not part of the champion structure. I don't see CMM's fist actually touch KM in that animation frame. According to normal hitbox or sprite mechanics, that's not a collision**. She's not touching KM.
MCOC actually appears to use Unity collision mechanics. Collision mechanics do not use hitboxes. There's no box to hit. Rather, Unity uses its physics engine to detect when two objects collide. It can detect collisions even if no animation frame shows a collision, because it can "infer" that if the fist is down here in frame 947 and up there in frame 948, it must have crossed the space between and if KM is in that space, a collision must have happened.
But that is a *calculation* not a *detection*. Which means you have to start asking serious technical questions like when precisely does this happen. In frame 948? Before 948? After 948? Those are all potentially correct answers (and I'm not a Unity expert so I don't know the answer to that one). But when people talk about hitboxes, hitboxes come with baggage, the term starts to shape the discussion. People say, it is obviously a hitbox problem, because I can *see* the problem. But if this is a Unity collision system problem, then that *means* problems can sometimes decouple what's happening and what we see. In other words, we can't always fully trust our eyes.
I'm completely skipping over the fact that MCOC combat has rules that modify collision mechanics, such as who takes priority during an intercept (technically all collisions are between two objects, but which one is considered to "hit" the other one is something that goes above and beyond collision detection itself).
"Hitbox" is a term of art. I don't expect the average player to understand the technical details of hitboxes or physics-based collisions or the Unity engine. But conversely players who do not understand these things shouldn't use technical terms they don't understand. Not because it matters what we call things, but because what we call things implies all sorts of things that might not be true, but convince people that false things are "obviously" true.
The game is more complicated than I think most people appreciate. AI is not just about what the NPC does, what the NPC does changes the rules of physics of the game when it decides to do it (like who takes priority over who during a hit). It can change those rules in between animation frames which means we don't see that change. And what we see and what the game reacts to can be different, because sometimes the game sees things before we do, and sometimes it can see things *after* we do, because we think we see it, but the game only calculates with certainty what we are only inferring happened with our eyes. None of this is unique to MCOC, by the way.
** I'm aware there are advanced hitbox collision algorithms that are more sophisticated, but this is simplified for discussion purposes.