Subscribe to download
(DEV) AI Pathfinder Improvement

Even if it’s a rare occurrence, it wouldn't hurt to add a safeguard so any player-led group is automatically excluded from my scheduler, which should also cover the handoff and brief leader swaps on respawn/revive as well. If anyone happens to see it again, do let me know.

@ImmortalTheOwl later, I found that the problem I described below is not stable. I encountered it only once, and it never happened again. I don't know what exactly caused that problem :/

Could it also be interesting to investigate if this could also happen when the player respawns and AI briefly take over the command of the group?

Or would the fix that you have likely already apply also to this?

@_mickey_ Interesting, so when the AI leader dies and the player becomes leader, the scheduler kept nudging the old doMove order toward the old destination. I'll push a fix soon to address this so that any group with a human leader will soon be automatically excluded from the scheduler. So your manual orders will still take full control. As for Vehicles, they still get the detour behaviour when AI-led. If you can retest the same scenario when I push the update out, that would be super helpful.

@ImmortalTheOwl Hi! I think I found the problem.

I started in a group under the command of an AI commander. When the commander was killed, the squad command passed to me (the player). After that, all the subordinate AI ​​members of my squad had a permanent Move status. Every time I commanded them to return to the formation, they returned briefly and then moved somewhere again. It was as if your mod ordered them to move, without the player's order.

This probably happens when changing the command from AI to player.

Working on it, don't you worry.

@ImmortalTheOwl Thank you for your answers. Now I understand much more) We are waiting for your updates!

Hope that helps as well.

When the scheduler detects a stall, it re-issues doMove to the exact destination position registered, nothing random.

If I pass a position (e.g., getMarkerPos "rally"), the nudge is always to that same vector.
If I pass an object, I currently resolve it once to its position at the time of the call. I’m not “following” the object afterward.
The “stop threshold” (1 m for infantry, ~3 m for vehicles) is only the radius where the mod stops nudging, it does not pick a random point in that radius.

Right now I don’t add intermediate points. That’s why vehicles can still push into an obstacle, they’re being nudged toward the same goal until they clear it. The next step I’m exploring is a small, deterministic detour (probe a few angles, pick the first clear micro-waypoint), then resume the original goal. If you want me to make the destination “follow” a moving object instead of a fixed position, I can probably add that as an option too.

" It only nudges a unit’s current move when the unit stalls" - here is the whole principle of your mod. Still I didn't get an answer where exactly you direct the AI ​​if this AI stopped. To the object or is it a random point in the radius x?