Native referenceRedM

_0xE116F6F2DA2D777E

0xE116F6F2DA2D777E TASK

Vector3 _0xE116F6F2DA2D777E(`p0` (Any));

Property	Value
Native Name	`_0xE116F6F2DA2D777E`
Hash	`0xE116F6F2DA2D777E`
Return Type	`Vector3`
Build	`1207`
Parameters	`p0` (Any)

Parameters

p0 (Any)

Usage

Lua (Direct):

local result = _0xE116F6F2DA2D777E(p0)

Lua (Hash):

local result = Citizen.InvokeNative(0xE116F6F2DA2D777E, p0)

Back to TASK

At a glance

Game: RedM
Namespace: TASK
Returns: Vector3

Before you call

Citizen.InvokeNative in CitizenFX Lua does not auto-marshal float/Vector3 returns — the result comes back wrong (community reports both a plain boolean and only-the-x-component-as-a-number); for these returns use the named Lua wrapper (e.g. GetEntityVelocity, GetPedBoneCoords, GetOffsetFromEntityInWorldCoords) or append Citizen.ResultAsVector() / Citizen.ResultAsFloat() as the final InvokeNative argument, and in JS/TS (no wrapper exists) Citizen.resultAsVector() / resultAsFloat() is mandatory; plain int/handle and void returns are unaffected. (see findings: learning:3, learning:17, learning:19, learning:24, learning:83 — fetch via get_document)

Let your AI
read the fine print.

Native signatures, warnings, and community context. Directly in your editor.

Connect via MCP