Provides parameters for 3D navigation path queries. By changing various properties of this object, such as the start and target position, you can configure path queries to the [NavigationServer3D]. $DOCS_URL/tutorials/navigation/navigation_using_navigationpathqueryobjects.html The navigation map [RID] used in the path query. Additional information to include with the navigation path. The navigation layers the query will use (as a bitmask). The path postprocessing applied to the raw path corridor found by the [member pathfinding_algorithm]. The pathfinding algorithm used in the path query. The path simplification amount in worlds units. If [code]true[/code] a simplified version of the path will be returned with less critical path points removed. The simplification amount is controlled by [member simplify_epsilon]. The simplification uses a variant of Ramer-Douglas-Peucker algorithm for curve point decimation. Path simplification can be helpful to mitigate various path following issues that can arise with certain agent types and script behaviors. E.g. "steering" agents or avoidance in "open fields". The pathfinding start position in global coordinates. The pathfinding target position in global coordinates. The path query uses the default A* pathfinding algorithm. Applies a funnel algorithm to the raw path corridor found by the pathfinding algorithm. This will result in the shortest path possible inside the path corridor. This postprocessing very much depends on the navigation mesh polygon layout and the created corridor. Especially tile- or gridbased layouts can face artificial corners with diagonal movement due to a jagged path corridor imposed by the cell shapes. Centers every path position in the middle of the traveled navigation mesh polygon edge. This creates better paths for tile- or gridbased layouts that restrict the movement to the cells center. Don't include any additional metadata about the returned path. Include the type of navigation primitive (region or link) that each point of the path goes through. Include the [RID]s of the regions and links that each point of the path goes through. Include the [code]ObjectID[/code]s of the [Object]s which manage the regions and links each point of the path goes through. Include all available metadata about the returned path.