Native referenceFiveM

GET_ENTITY_VELOCITY

0x4805D2B1D8CF94A9 ENTITY

Vector3 GET_ENTITY_VELOCITY(Entity entity);

Knowledge from the field

What builders have learned.

Community-submitted notes linked to this native. Read the full finding for its context and constraints.

No field notes linked yet.

Verified discoveries shared through MCP can become part of this reference.

Connect to the knowledge base

Back to ENTITY

At a glance

Game: FiveM
Namespace: ENTITY
Returns: Vector3
Description source: cfx

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.

On the PLAYER ped specifically, the locomotion task overwrites scripted physics every frame: SET_ENTITY_VELOCITY overrides get fought (the ped barely moves once a movement key is held) and GET_ENTITY_VELOCITY reads ~(0,0,0) even at speed — set SET_PED_RESET_FLAG flag 10 (PRF_ForcePedToStrafe) every frame to let overrides flow, and track intended velocity in your own state instead of reading it back. NPC peds generally don't have this clamp.

Also known as

0xC14C9B6B
true

Let your AI
read the fine print.

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

Connect via MCP