_GET_PROP_SET_AT_COORDS
Hash
0xC061E50F8D299F95Runtime name
GetPropSetAtCoordsNamespacePROPSET
SideClient
NameCommunity guess
Docs
Since build1207
Signature
PropSet _GET_PROP_SET_AT_COORDS(Hash propsetHash, float x, float y, float z);Parameters
| Name | Type | Description |
|---|---|---|
propsetHash | Hash | — |
x | float | — |
y | float | — |
z | float | — |
Returns PropSet
Usage
local retval = GetPropSetAtCoords(propsetHash, x, y, z)
-- always works, by hash
local retval = Citizen.InvokeNative(0xC061E50F8D299F95, propsetHash, x, y, z, Citizen.ResultAsInteger())JavaScript and C#
const retval = GetPropSetAtCoords(propsetHash, x, y, z);
// by hash
const retval = Citizen.invokeNative('0xC061E50F8D299F95', propsetHash, x + 0.0000001, y + 0.0000001, z + 0.0000001, Citizen.returnResultAnyway(), Citizen.resultAsInteger());int retval = Function.Call<int>((Hash)0xC061E50F8D299F95, propsetHash, x, y, z);- Hash parameters: the named function also accepts a string and hashes it for you;
Citizen.InvokeNativeneeds the number — passjoaat("name")or a backtick literal like`name`. - Float parameters: Lua integers (
10, or whole numbers decoded from NUI/JSON) are sent as ints and read as garbage. Write10.0orvalue + 0.0. The generated JS wrappers add0.0000001to 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
InvokeNativewith the hash — it always works.
Sources
Something wrong or missing? Contribute a verified note — corrections ship through pull requests.