 |
This bug is related to 0001327 (if not a duplicate), and the issue is here basically that the "projectile result" object stays always around for a finite time (I believe 2 minutes). So you either have it stay around when it doesn't make sense (at the impact of the arrow, but the pieces where flying away, and vanish a bit later; or when the arrow sticks, and the player removes it, the result is there for full X minutes, anyway), or it is not there when you need it (imagine an arrow breaking over the head of an AI and the bits falling down - the AI will not be alerted because the result is high above its head). Making the projectile result object either more smart seems to be the solution (maybe simply binding it to the arrow and the arrow-pieces would already make it auto-vanish with them, and then adding a timeout to it where it self-destructs might do the trick already). |
 |
If an arrow is stuck in a wall, why have a self-destruct timer? The timer for a broadhead is 2 mins. If I shoot an arrow into a wall, it stays there forever until I frob it. But the stims stop after 2 min. Why should the behavior be different for an AI that comes upon the arrow at the 1-min mark (alerted) than for an AI that comes upon it at the 3-min mark (not alerted)? |
|
|
That's a good question (I did not design it that way, btw). I guess the reason is that if the arrow is there long enough, the AI stops caring. Or it is performance related (fire 20 arrows in a wall - game slows down to a crawl?) Also, the self-destruct was not meant for the arrow (it should definitely stay indefinitely), but for the stim object. No sense in keeping it around if the stim is gone. It might be best first to define what should actually happen in each case, and then change the code to implement that (however it would work). |
|
|
This is a duplicate of 0001327. |
- Anonymous
