Are you setting the agent’s destination to (inf, inf, int) or clearing its path in some way?
I think the current RichAI script does indeed have a limitation that it cannot handle this case when a navmesh cut removes the ground below it. The RichAI needs a path to be able to navigate, and when a navmesh cut removes the nodes it was following, it will try to recalculate a new path automatically. However, if you have set its destination to (inf, inf, inf) then it will not be able to do this. I would recommend setting the destination to the agent’s own position instead. And in the meantime I’ll take a look and see if I can resolve this issue in a better way.
Actually, Destination field is kinda broken and it is always Infinity. But distance to target is correct, because it’s calculated using Endpoint field.
Inspector normal and debug while bot is running:
In case that matters I start path using seeker.StartPath(transform.position, (Vector3)targetValue, OnPathCalculated);
And stop it using richAI.SetPath(null);
In terms of what is going on original topic, I did not change destination at all. I just put whatever place on the map to go, move cut under agent and it lags out. Then if you put another (or same) target into seeker it’s gonna recalculate and fix itself