_FORCE_LIGHTNING_FLASH_AT_COORDS
p3 is always -1.0f in the scripts
Hash
0x67943537D179597CRuntime name
ForceLightningFlashAtCoordsNamespaceMISC
SideClient
NameCommunity guess
Docs
Since build1207
Signature
void _FORCE_LIGHTNING_FLASH_AT_COORDS(float x, float y, float z, float p3);Parameters
| Name | Type | Description |
|---|---|---|
x | float | — |
y | float | — |
z | float | — |
p3 | float | — |
Returns void
Description
p3 is always -1.0f in the scripts
Usage
ForceLightningFlashAtCoords(x, y, z, p3)
-- always works, by hash
Citizen.InvokeNative(0x67943537D179597C, x, y, z, p3)JavaScript and C#
ForceLightningFlashAtCoords(x, y, z, p3);
// by hash
Citizen.invokeNative('0x67943537D179597C', x + 0.0000001, y + 0.0000001, z + 0.0000001, p3 + 0.0000001);Function.Call((Hash)0x67943537D179597C, x, y, z, p3);- 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.