TASK_FOLLOW_WAYPOINT_RECORDING_AT_OFFSET

Hash0xBE9B0520BD7C445B

Runtime nameTaskFollowWaypointRecordingAtOffset

NamespaceTASK

SideClient

NameOfficial

Docs

Since build1207

Signature

void TASK_FOLLOW_WAYPOINT_RECORDING_AT_OFFSET(Ped ped, const char* waypointRecording, float p2, int p3, int p4, int p5, BOOL p6);

Parameters

Name	Type	Description
`ped`	`Ped`	—
`waypointRecording`	`const char*`	—
`p2`	`float`	—
`p3`	`int`	—
`p4`	`int`	—
`p5`	`int`	—
`p6`	`BOOL`	—

Returns void

Usage

Lua

TaskFollowWaypointRecordingAtOffset(ped, waypointRecording, p2, p3, p4, p5, p6)

-- always works, by hash
Citizen.InvokeNative(0xBE9B0520BD7C445B, ped, waypointRecording, p2, p3, p4, p5, p6)

JavaScript and C#

JavaScript

TaskFollowWaypointRecordingAtOffset(ped, waypointRecording, p2, p3, p4, p5, p6);

// by hash
Citizen.invokeNative('0xBE9B0520BD7C445B', ped, waypointRecording, p2 + 0.0000001, p3, p4, p5, p6);

Function.Call((Hash)0xBE9B0520BD7C445B, ped, waypointRecording, p2, p3, p4, p5, p6);

Float parameters: Lua integers (10, or whole numbers decoded from NUI/JSON) are sent as ints and read as garbage. Write 10.0 or value + 0.0. The generated JS wrappers add 0.0000001 to non-zero floats for the same reason.

Sources

alloc8or RDR3 NativeDB

Something wrong or missing? Contribute a verified note — corrections ship through pull requests.