I’m not attempting to be insulting, I’m attempting to provide you with ideas for how you can implement it, because Epic isn’t very likely to just go and “fix” something that isn’t broken.
Though I did just actually start reading through the MovementComponent and PathFollowingComponent code, I haven’t actually built a test to see if this would have the effect that you’re looking for …
Have you tried bStopMovementOnFinish = false in your PathFollowingComponent? It looks like setting that false would avoid the call to StopMovementImmediately that normally occurs at the end of a path. You might need to mix that with the Use Acceleration toggle in one way or another, not sure.
If you were to write your own PathFollowingComponent, it looks like all you’d have to do is override OnPathFinished() or OnSegmentFinished(). Certainly not several thousand lines, only about 40 if you have to completely override the functionality of it, a lot fewer if you can just do what you need and Super:: from it.
Alternatively, you could also implement something that interfaces with the MetaPathUpdate system to issue changes in the path before the AI arrives, sending them in advance in the direction you want to go.
There are many many different ways you could go about this.