[CrapShoot]

It sounds to me like a pathing issue on Trenchtoast.

I'll look at it. I believe that when they get off path (or the current short term goal timed out), they try to reach the closest node. And if the closest node is behind a barrier they can't pass, it creates a "loop" in terms of trying to reach the closest node (because the closest node remains constant).

I'm not 100% sure if this is accurate, but it seems to be somewhat correct after troubleshooting some of these instances with waypointing.

I fixed some of them on Trenchtoast before by making sure to have a node placed close enough to the trouble area that would get them back on track.

I suppose if there was some progression in terms of them seeking out a "reachable" close node, it would make it a bit less critical to find and path all of the trouble spots. By progression, I mean if they try to reach the first closest node, but can't, they would then try and reach the next closest node.