Pathfind::getSafeCoordForPed: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 12: | Line 12: | ||
==Example== | ==Example== | ||
<syntaxhighlight lang="javascript"> | <syntaxhighlight lang="javascript"> | ||
// | let | ||
position = mp.players.local.position | |||
; | |||
position = mp.game.pathfind.getSafeCoordForPed(position.x, position.y, position.z, true, 28); // 16 | |||
</syntaxhighlight> | </syntaxhighlight> | ||
==See also== | ==See also== | ||
Latest revision as of 23:49, 21 October 2021
When onGround == true outPosition is a position located on the nearest pavement.
When a safe coord could not be found the result of a function is false and outPosition == Vector3.Zero.
In the scripts these flags are used: 0, 14, 12, 16, 20, 21, 28. 0 is most commonly used, then 16.
16 works for me, 0 crashed the script.
Syntax
mp.game.pathfind.getSafeCoordForPed(x, y, z, onGround, flags);
Required Arguments
- x: float
- y: float
- z: float
- onGround: Boolean
- flags: int
Return value
- Vector3
Example
let
position = mp.players.local.position
;
position = mp.game.pathfind.getSafeCoordForPed(position.x, position.y, position.z, true, 28); // 16