 |
I suspect what is happening isn't really "pain transferring" or even strictly a bug: The AI is swinging its sword at you, but hitting the other AI because they got in the way. Collision check is done against all enemies of the attacker, so it's possible to swing a sword with the intention of hitting one enemy, but actually end up hitting another. You can make this mistake too as the player, if another enemy is standing too close to the one you're hitting. Don't know of an easy fix for this one. We could track whether it happens in the AI combat subtask, and maybe tell them to use a different attack than the one they last used that hit the wrong person. EDIT: One way to test this would be to turn on melee clipmodel visualization (tdm_melee_debug 1), and stand somewhere on the other side of the friendly AI so that hopefully the enemy's sword attacks can hit you without hitting them. The clipmodels of the enemy attacks are rather large though, they might even hit people slightly behind them first. |
 |
Hmmm. So what's happening is that the sword is swinging back, hits the AI at the rear, then swings forward to hit the player. This makes sense, except the player appears to take no damage. Maybe the sword swinging animation only gives pain to the first entity it hits, not all entities it hits. It's also possible that the pain-dealing AI thinks he's facing the guy in the rear. The pain is handed out correctly, but for some reason he wasn't able to turn around. I'll see if I can figure out where all the pain is supposed to be going, and where it really is going. If it makes sense as is, I'll close this out as not a problem. Thanks for this insight. It hadn't occurred to me. |
|
|
Yeah, by design, the swords can only hit one person per attack. It wouldn't be too realistic for the sword to cleave through or stab through one person and hit another. We were hoping that in the future, there would be some sort of bounce back or recovery animation so that you can clearly see the sword has hit something and stopped the swing. For now it just plays through the whole animation, which can cause confusion in cases like this. It doesn't start testing for collisions until it swings forward, so they wouldn't be getting hit on the backswing, technically. But if an AI is really close behind, the larger CM of the AI's attacks might end up hitting them in the first frame of the forward swing. We can't really make the CMs smaller though, as that would expose some spots the player could stand to never get hit. They've been tweaked pretty extensively already. |
|
|
I've verified that this is the sequence: Enemy hits me. Friend hits enemy. Enemy and friend duke it out until friend dies. Enemy hits me enough times to kill me. All of this happens while the enemy is facing me, so it looks like I'm getting hit with each of his swings. I think it would be easiest to make the enemy ignore the friend while the enemy cuts me down. Probably a simple change to only allow the hit if the AI being hit is not "behind" the attacker. If not allowed, the swing would next encounter me, and that hit would be allowed. The more difficult change would be to make the enemy turn back toward the friend before continuing his attack, then turn back to me when he's done. Does the easier solution sound reasonable? |
|
|
I don't think the first change would be very simple. First you would need to detect the situation, but hitting things happens at the basic melee physics level, where you'd have to add a lot of code to see what AI am I attached to, who is attacking them, who are they trying to attack, etc. Once you detected the situation, you would have to build up some sort of ignore list and teleport things in that list away temporarily while the trace is going on. A trace function can only take one ignore parameter, that's why you need this hack of temporarily teleporting things away, then putting them back. I'm also not sure about that change, because physically you would expect that an AI standing in the way of the enemy's sword would get hit. The AI just isn't smart enough to realize that. I'd rather see the change made at the AI level rather than complicate the physics a lot to make the sword teleport through things, which might even appear wrong from the player's perspective. For example, if the AI is taking damage form another enemy and not the one they've decided to attack, maybe turn and face the other enemy. If the AI still wants to hit you and their attacks are hitting another AI, have them check what side they're on and rule out the attack that covers that side (for example, they hit an AI on their left trying to get at you, have them stop doing left to right slashes). They already know who they're trying to attack and who they hit, so that might not be _that_ hard to implement. I'm not sure if it's a very high priority, though. How often does this happen? EDIT: It used to happen that they'd hit their teammates this way, but we made the sword pass through their teammates as a quick fix, because it is a bit complicated to try to give them some spatial reasoning so they can use attacks that avoid one AI and hit another. |
|
|
Found this in the code: "// TODO: Figure out how to switch enemies to face & parry a new one" So that's the right thing to do. |
- Anonymous
