Talk:Func nav prefer

Consistency across func_nav_avoid, func_nav_prefer, and func_nav_prerequisite

I noticed the See Also section for Func_nav_prerequisite lists func_nav_prefer, but also adds the description "...by decreasing the pathfinding cost within it." This is technically true, but this fact is not mentioned at all on the page for func_nav_prefer. Should this be added in to the Entity Description section of the entity? Exact values can be provided.

Likewise, the same applies to func_nav_avoid (albeit the cost is inverted), yet this is not mentioned anywhere. It would also be preferable to add func_nav_avoid to the See Also section of func_nav_prerequisite, as the prefer and avoid entities go hand-in-hand. Jakapoa (talk) 16:12, 29 August 2021 (PDT)

Sounds good to implement, don't have anything to disagree about this yet. - Orin (talk) 10:58, 30 August 2021 (PDT)