Only if you explicitly configure it that way by adding “Pawn” (or equivalent) as an obstacle channel in the “Obstacle Query Channels” list in the Navigation Manager. It’s not a usecase I’ve tested thoroughly so you may run into bugs and what not.
Not sure if I understood this correctly but if you’re looking to enforce constraints around the maximum angle that a navigation path can take to reach its destination then you’ll have to modify the neighbor node lookup (C++ code) in the plugin to exclude those neighbors which represent any angle exceeding your desired threshold.
In general, I’ve only added those features to the plugin that my own project needed at that time.
Use the sample project as a good rule of thumb: if you don’t see a feature already implemented in the sample project then it will probably take some time/effort to add on to the plugin!
Hope you find the plugin useful and are able to extend it to meet your needs.