* Add AstarGrid2D headline to 2D Navigation Overview
Resolves#9668 by adding in the request description.
This PR adds a short description for AStarGrid2D of its function and use case that was previously missing in the 2D navigation overview page.
The `path_desired_distance`, `target_desired_distance`, and `path_max_distance` documentation was a bit ambiguous. I tried to make it a little more clear without making it too long, since the properties are also documented at the [NavigationAgent3D](https://docs.godotengine.org/en/stable/classes/class_navigationagent3d.html) page.
In "avoidance_priority" property description, changed "important npcs characters" to "important non playable characters". The term "npc", means "non playable character", so to say "non playable characters characters" seems like an error.
Removes the parts that state that the navigation layers have anything to do with how a navigation map merges the navigation regions or navigation mesh polygons. Also corrects wrong statement about changing the navigation layers of a region as that change requires a server sync.
Adds info that in Godot 4.3 a NavigationObstacle3D can be baked to navmesh and used to discard unwanted navmesh inside its shape, e.g. navmesh that appears inside walls.
NavigationServer2D and 3D's `map_set_active()` method takes two arguments, the map RID and the boolean. The docs only contained the boolean, resulting in wrong code.
This allows users to leave comments on pages that don't have
`:allow_comments: False` somewhere in the page's source.
Both manual and class reference pages can receive comments.
Index pages cannot have comments, as discussion should occur on "leaf" pages.
GitHub Discussions is used as a backend on the same repository. This means
that Discussions *must* be enabled on godotengine/godot-docs before this
commit is merged to `master`. Users can choose to use the "Custom" watch
mode if they don't want to get notifications for discussion updates,
but still get notifications for issue and pull request updates.
User comments are intended to be used for the following purposes:
- Add a clarification or correct something in the documentation,
without having to open a pull request. Contributors are encouraged to
take a look at discussions from time to time, and see if there's information
worth incorporating in the pages themselves. Don't forget to reply to
the comment when doing so :)
- Mention a workaround for a common issue.
- Link to useful third-party resources that are relevant to the current page,
such as tutorials or add-ons.
User comments should *not* be used for technical support. Other community
platforms should be used for that.
Page-to-discussion matching is done using the `pagename` Sphinx variable,
which is independent of the Godot version and documentation language.
Being independent of the Godot version allows keeping old comments
when the Godot version changes, while also allowing users from `/stable`
and `/4.1` to "see" each other in discussions.
See https://giscus.app for more information.
