RedM Natives

_ADD_DOOR_TO_SYSTEM_NEW

Registers a door, hashes:

Hash0xD99229FE93B46286
Runtime nameAddDoorToSystemNew
NamespaceOBJECT
SideClient
NameCommunity guess
Docs
Since build1207

Signature

void _ADD_DOOR_TO_SYSTEM_NEW(Hash doorHash, BOOL p1, BOOL p2, BOOL p3, int threadId, int p5, BOOL p6);

Parameters

NameTypeDescription
doorHashHash—
p1BOOL—
p2BOOL—
p3BOOL—
threadIdint—
p5int—
p6BOOL—

Returns void

Description

alloc8or RDR3 NativeDB

Registers a door, hashes: https://github.com/femga/rdr3_discoveries/tree/master/doorHashes

femga rdr3_discoveries · research notes

0xD99229FE93B46286    (by Hackuou)
Citizen.InvokeNative(0xD99229FE93B46286, hash, 1, 0, 0, 0, 0, 0)
Someone uses that and it works to register the door
Whereas I use
Citizen.InvokeNative(0xD99229FE93B46286, hash, 1, 0, 0, 0, 0, 0)
And it does the same thing from what I can tell
Still registers it anyways

Usage

Lua
AddDoorToSystemNew(doorHash, p1, p2, p3, threadId, p5, p6)

-- always works, by hash
Citizen.InvokeNative(0xD99229FE93B46286, doorHash, p1, p2, p3, threadId, p5, p6)
JavaScript and C#
JavaScript
AddDoorToSystemNew(doorHash, p1, p2, p3, threadId, p5, p6);

// by hash
Citizen.invokeNative('0xD99229FE93B46286', doorHash, p1, p2, p3, threadId, p5, p6);
C#
Function.Call((Hash)0xD99229FE93B46286, doorHash, p1, p2, p3, threadId, p5, p6);
  • Hash parameters: the named function also accepts a string and hashes it for you; Citizen.InvokeNative needs the number — pass joaat("name") or a backtick literal like `name`.
  • 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 · femga rdr3_discoveries

Something wrong or missing? Contribute a verified note — corrections ship through pull requests.