_TASK_START_SCENARIO_IN_PLACE_2
Takes scenario point handle instead of hash
Hash
0xA917E39F2CEFD215Runtime name
TaskStartScenarioInPlace_2NamespaceTASK
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
| Name | Type | Description |
|---|---|---|
ped | Ped | — |
p1 | Any | — |
p2 | const char* | — |
p3 | int | — |
p4 | BOOL | — |
p5 | float | — |
idleForever | BOOL | — |
Returns void
Description
Takes scenario point handle instead of hash
Usage
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#
TaskStartScenarioInPlace_2(ped, p1, p2, p3, p4, p5, idleForever);
// by hash
Citizen.invokeNative('0xA917E39F2CEFD215', ped, p1, p2, p3, p4, p5 + 0.0000001, idleForever);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. Write10.0orvalue + 0.0. The generated JS wrappers add0.0000001to 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
InvokeNativewith the hash — it always works.
Sources
Something wrong or missing? Contribute a verified note — corrections ship through pull requests.