mirror of
https://gitlab.com/veloren/veloren.git
synced 2024-08-30 18:12:32 +00:00
74d4e4f45e
When a chaser's route finishes calculating, the chaser may already be a few blocks away from the starting position, thanks to movement inertia. The path finding code finds the point along the route closest to the chaser's position. This calculation only considered the xy coordinates when finding the closest point. This caused issues whenever the calculated route goes below the chaser's position (for example, when the chaser is on top of a bridge and the route circled around to go under the bridge). In this case, there was a chance that the closest point was the one below the bridge. This caused the chaser to try to move directly to a directly inaccessible block. The fix was to remove the xy() filter so that the closest point algorithm also considered the z coordinate. |
||
|---|---|---|
| .. | ||
| assets | ||
| base | ||
| benches | ||
| ecs | ||
| frontend | ||
| net | ||
| src | ||
| state | ||
| systems | ||
| build.rs | ||
| Cargo.toml | ||