RedM Natives

_SET_ENTITY_COORDS_AND_HEADING_NO_OFFSET

Hash0x0918E3565C20F03C
Runtime nameSetEntityCoordsAndHeadingNoOffset
NamespaceENTITY
SideClient
NameCommunity guess
Docs
Since build1207

Signature

void _SET_ENTITY_COORDS_AND_HEADING_NO_OFFSET(Entity entity, float xPos, float yPos, float zPos, float heading, BOOL p5, BOOL p6);

Parameters

NameTypeDescription
entityEntity—
xPosfloat—
yPosfloat—
zPosfloat—
headingfloat—
p5BOOL—
p6BOOL—

Returns void

Usage

Lua
SetEntityCoordsAndHeadingNoOffset(entity, xPos, yPos, zPos, heading, p5, p6)

-- always works, by hash
Citizen.InvokeNative(0x0918E3565C20F03C, entity, xPos, yPos, zPos, heading, p5, p6)
JavaScript and C#
JavaScript
SetEntityCoordsAndHeadingNoOffset(entity, xPos, yPos, zPos, heading, p5, p6);

// by hash
Citizen.invokeNative('0x0918E3565C20F03C', entity, xPos + 0.0000001, yPos + 0.0000001, zPos + 0.0000001, heading + 0.0000001, p5, p6);
C#
Function.Call((Hash)0x0918E3565C20F03C, entity, xPos, yPos, zPos, heading, p5, p6);
  • 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.