Detail that NavigationLink3D nodes must be siblings to NavigationRegion3D nodes

[elvisish]

Problem or limitation

Currently, if a NavigationLink3D is a child of another node in the scene, the NavigationRegion3D will ignore it, the NavigationLink3D node must be a sibling to NavigationLink3D for it to work.

Proposed improvement

Include this information in the documentation, or fix NavigationLink3D so that it can be detected using groups or layers by the NavigationRegion3D.

Proposal review

• Yes, this proposal is highly specific and actionable.

[elvisish]

I should also mention that NavigationLink3D doesn't seem to trigger the "entered" signal if the link isn't connected to another part of a NavigationMesh. If it is just placed on a NavMesh or links to a non-walkable part of the mesh, the signal doesn't seem to trigger at all.