_SET_SCENARIO_POINT_COORDS
Hash
0x2056AB38DF06825CRuntime name
SetScenarioPointCoordsNamespaceTASK
SideClient
NameCommunity guess
Docs
Since build1207
Signature
void _SET_SCENARIO_POINT_COORDS(int scenario, float xPos, float yPos, float zPos, BOOL p4);Parameters
| Name | Type | Description |
|---|---|---|
scenario | int | — |
xPos | float | — |
yPos | float | — |
zPos | float | — |
p4 | BOOL | — |
Returns void
Usage
SetScenarioPointCoords(scenario, xPos, yPos, zPos, p4)
-- always works, by hash
Citizen.InvokeNative(0x2056AB38DF06825C, scenario, xPos, yPos, zPos, p4)JavaScript and C#
SetScenarioPointCoords(scenario, xPos, yPos, zPos, p4);
// by hash
Citizen.invokeNative('0x2056AB38DF06825C', scenario, xPos + 0.0000001, yPos + 0.0000001, zPos + 0.0000001, p4);Function.Call((Hash)0x2056AB38DF06825C, scenario, xPos, yPos, zPos, p4);- 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.
See also
Sources
Something wrong or missing? Contribute a verified note — corrections ship through pull requests.