Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Restore transient blocker check in pathfinding queries. #17531
With the above comment taken into account we don't need to reopen any of those old issues. The backup search with
However, the change here does mean that the initial search will fail more often on a combination of moving and stationary blockers. Since the backup search ignores all transient actors, we might be seeing a lot more wall hugging behaviour, which is inefficient and looks dumb.
In order to prevent that, it might be a good idea for now to have multiple tiers of backup pathing. So start with
Context: The issue that this bit of code was fixing was #11437. But apparently I forgot to close it, so it doesn't need to be reopend either.
With the first commit the unit cannot find a path initially and then ignores everything. The resulting behaviour should be that it drives straight into the wall and only then repaths.
with the second commit, after failing the first time, it will ignore only the friendly unit. The result should be that it immediately paths through the gap and nudges the friendly unit out of the way.
(This is all from theory; I haven't tested it myself yet)
This does appear to solve part of the problem, but isn't sufficient by itself. The unit will now move next to the blocking friendly unit, but something else is preventing