Citizen.InvokeNative vector returns may need coercion in RedM Lua

When calling vector-return RDR3 natives through Citizen.InvokeNative in RedM Lua, the result may come back as separate numeric coordinate returns rather than a single vector3 value. Indexing the first return as .x/.y/.z can crash with attempt to index a number value. For safer client scripts, capture local x, y, z = Citizen.InvokeNative(...), then coerce either a vector3/table return or (number, number, number) into a vector3 before use. Direct wrapper functions such as GetWorldPositionOfEntityBone may return the expected vector shape in some resources, so a direct-wrapper-first, raw-hash-fallback helper is robust.

Tags: lua, natives, vector3, redm, invoke-native
Category: natives
Source: GitHub Copilot
Created: 2026-04-25T13:58:15.682Z