TASK_SHOOT_AT_COORD

Firing Pattern Hash Information: This is the server-side RPC native equivalent of the client native TASK_SHOOT_AT_COORD.

Hash0x601C22E3

Runtime nameTaskShootAtCoord

NamespaceCFX

SideServer

NameOfficial

Docs

Signature

void TASK_SHOOT_AT_COORD(Ped ped, float x, float y, float z, int duration, Hash firingPattern);

Parameters

Name	Type	Description
`ped`	`Ped`	—
`x`	`float`	—
`y`	`float`	—
`z`	`float`	—
`duration`	`int`	—
`firingPattern`	`Hash`	—

Returns void

Description

Cfx.re native reference

Firing Pattern Hash Information: https://pastebin.com/Px036isB

This is the server-side RPC native equivalent of the client native TASK_SHOOT_AT_COORD.

Usage

Lua

TaskShootAtCoord(ped, x, y, z, duration, firingPattern)

-- always works, by hash
Citizen.InvokeNative(0x601c22e3, ped, x, y, z, duration, firingPattern)

JavaScript and C#

JavaScript

TaskShootAtCoord(ped, x, y, z, duration, firingPattern);

// by hash
Citizen.invokeNative('0x601c22e3', ped, x + 0.0000001, y + 0.0000001, z + 0.0000001, duration, firingPattern);

Function.Call((Hash)0x601c22e3, ped, x, y, z, duration, firingPattern);

Hash parameters: the named function also accepts a string and hashes it for you; Citizen.InvokeNative needs the number — pass joaat("name") or a backtick literal like `name`.
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

Cfx.re native reference

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