RedM Natives

_TASK_START_SCENARIO_IN_PLACE_2

Takes scenario point handle instead of hash

Hash0xA917E39F2CEFD215
Runtime nameTaskStartScenarioInPlace_2
NamespaceTASK
SideClient
NameCommunity guess
Docs
Since build1207

Signature

void _TASK_START_SCENARIO_IN_PLACE_2(Ped ped, Any p1, const char* p2, int p3, BOOL p4, float p5, BOOL idleForever);

Parameters

NameTypeDescription
pedPed—
p1Any—
p2const char*—
p3int—
p4BOOL—
p5float—
idleForeverBOOL—

Returns void

Description

Takes scenario point handle instead of hash

Usage

Lua
TaskStartScenarioInPlace_2(ped, p1, p2, p3, p4, p5, idleForever)

-- always works, by hash
Citizen.InvokeNative(0xA917E39F2CEFD215, ped, p1, p2, p3, p4, p5, idleForever)
JavaScript and C#
JavaScript
TaskStartScenarioInPlace_2(ped, p1, p2, p3, p4, p5, idleForever);

// by hash
Citizen.invokeNative('0xA917E39F2CEFD215', ped, p1, p2, p3, p4, p5 + 0.0000001, idleForever);
C#
Function.Call((Hash)0xA917E39F2CEFD215, ped, p1, p2, p3, p4, p5, idleForever);
  • 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.
  • The name is a community guess and may change. If the named call is missing in your client build, use InvokeNative with the hash — it always works.

Sources

alloc8or RDR3 NativeDB

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