TASK_FOLLOW_ENTITY_ALONG_WAYPOINT_RECORDING_AT_OFFSET

Hash0x4D2B787BAE9AB760

Runtime nameTaskFollowEntityAlongWaypointRecordingAtOffset

NamespaceTASK

SideClient

NameOfficial

Docs

Since build1207

Signature

void TASK_FOLLOW_ENTITY_ALONG_WAYPOINT_RECORDING_AT_OFFSET(Ped ped0, Ped ped1, const char* waypointRecording, float p3, float p4, int p5, int p6, int p7, BOOL p8);

Parameters

Name	Type	Description
`ped0`	`Ped`	—
`ped1`	`Ped`	—
`waypointRecording`	`const char*`	—
`p3`	`float`	—
`p4`	`float`	—
`p5`	`int`	—
`p6`	`int`	—
`p7`	`int`	—
`p8`	`BOOL`	—

Returns void

Usage

Lua

TaskFollowEntityAlongWaypointRecordingAtOffset(ped0, ped1, waypointRecording, p3, p4, p5, p6, p7, p8)

-- always works, by hash
Citizen.InvokeNative(0x4D2B787BAE9AB760, ped0, ped1, waypointRecording, p3, p4, p5, p6, p7, p8)

JavaScript and C#

JavaScript

TaskFollowEntityAlongWaypointRecordingAtOffset(ped0, ped1, waypointRecording, p3, p4, p5, p6, p7, p8);

// by hash
Citizen.invokeNative('0x4D2B787BAE9AB760', ped0, ped1, waypointRecording, p3 + 0.0000001, p4 + 0.0000001, p5, p6, p7, p8);

Function.Call((Hash)0x4D2B787BAE9AB760, ped0, ped1, waypointRecording, p3, p4, p5, p6, p7, p8);

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.