_TASK_USE_NEAREST_SCENARIO_TO_COORD

Signature

void _TASK_USE_NEAREST_SCENARIO_TO_COORD(Ped ped, float x, float y, float z, float distance, int duration, BOOL p6, BOOL p7, BOOL p8, BOOL p9);

Parameters

Returns void

Usage

TaskUseNearestScenarioToCoord(ped, x, y, z, distance, duration, p6, p7, p8, p9)

-- always works, by hash
Citizen.InvokeNative(0x322BFDEA666E2B0E, ped, x, y, z, distance, duration, p6, p7, p8, p9)

TaskUseNearestScenarioToCoord(ped, x, y, z, distance, duration, p6, p7, p8, p9);

// by hash
Citizen.invokeNative('0x322BFDEA666E2B0E', ped, x + 0.0000001, y + 0.0000001, z + 0.0000001, distance + 0.0000001, duration, p6, p7, p8, p9);

Function.Call((Hash)0x322BFDEA666E2B0E, ped, x, y, z, distance, duration, p6, p7, p8, p9);

• 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.