This post already explained it pretty well:
t/no-base-offset-option-for-aipath/9094 (I am actually not allowed to post links here 
) [Edit: fixed the url]
The proposed solution by the asset creator is far from ideal and not feasible for all use cases. In my game, I’m dealing with user generated content loaded at runtime, which requires me to configure characters on the fly. Having to restructure the characters’ hierarchies only to be able to add an offset introduces unnecessary complications and bugs.
Thanks.
Hi
I don’t think you are talking about the same thing as the linked post at all?
Apologies. While trying to format the url I got the wrong one.
t/no-base-offset-option-for-aipath/9094
Aha.
I’m very reluctant to make this change, as in my experience, having the position of the agent be its center very often leads to subtle bugs, and I think best practice is to have the position at the agent’s feet.
Here’s an attempt at explaining the feature request as fast as possible. In a nutshell, I’m asking for AiPath to have a similar Base Offset property that NavMeshAgent has.
What problems are you running into using a child game object for the offset? Does your agent need to be tied to the same GameObject with your model for something in your game?
