RedM Natives

_NETWORK_SPAWN_CONFIG_ADD_SPAWN_POINT

Hash0xFD1AC0B3858F224C
Runtime nameNetworkSpawnConfigAddSpawnPoint
NamespaceNETWORK
SideClient
NameCommunity guess
Docs
Since build1207

Signature

void _NETWORK_SPAWN_CONFIG_ADD_SPAWN_POINT(float x, float y, float z, float heading);

Parameters

NameTypeDescription
xfloat—
yfloat—
zfloat—
headingfloat—

Returns void

Usage

Lua
NetworkSpawnConfigAddSpawnPoint(x, y, z, heading)

-- always works, by hash
Citizen.InvokeNative(0xFD1AC0B3858F224C, x, y, z, heading)
JavaScript and C#
JavaScript
NetworkSpawnConfigAddSpawnPoint(x, y, z, heading);

// by hash
Citizen.invokeNative('0xFD1AC0B3858F224C', x + 0.0000001, y + 0.0000001, z + 0.0000001, heading + 0.0000001);
C#
Function.Call((Hash)0xFD1AC0B3858F224C, x, y, z, heading);
  • 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.

Sources

alloc8or RDR3 NativeDB

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