05-28-2015, 10:51 PM
Skeleton diagnosis:
The Skeleton is immobile because the mobs' pathfinding will stop when mobs reach their final destination. The function which determines if the mob reached the final destination is cMonster::ReachedFinalDestination, and that function simply returns whether the target in range or not. For melee units, Target in range <=> Reached final destination. But for ranged units, that is not the case. The target may be in range regardless of whether or not the final destination was reached. This causes the skeleton to wrongly believe it reached the final destination, this is why it is immobile.
One easy fix is checking the line of sight inside ReachedFinalDest, but that's sphagetti, and I feel parts the TickPathfinding function is also sphagetti. As a quick fix, I'll make ReachedFinalDestination compare distance to some small constant, and not to the actual mob attack range. On the longer run, I'll rewrite some of cMonster's pathfinding code and clean it.
The Skeleton is immobile because the mobs' pathfinding will stop when mobs reach their final destination. The function which determines if the mob reached the final destination is cMonster::ReachedFinalDestination, and that function simply returns whether the target in range or not. For melee units, Target in range <=> Reached final destination. But for ranged units, that is not the case. The target may be in range regardless of whether or not the final destination was reached. This causes the skeleton to wrongly believe it reached the final destination, this is why it is immobile.
One easy fix is checking the line of sight inside ReachedFinalDest, but that's sphagetti, and I feel parts the TickPathfinding function is also sphagetti. As a quick fix, I'll make ReachedFinalDestination compare distance to some small constant, and not to the actual mob attack range. On the longer run, I'll rewrite some of cMonster's pathfinding code and clean it.