Native referenceRedMclient

GET_EVENT_DATA

0x57EC5FA4D4D6AFCA SCRIPTS

BOOL GET_EVENT_DATA(int eventGroup, int eventIndex, Any* eventData, int eventDataSize);

Knowledge from the field

What builders have learned.

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

Finding / 81

Reading RDR3 AI events (skinning/loot) from TypeScript: poll the event queue + marshal GET_EVENT_DATA with a JS ArrayBuffer

## Context RDR3 AI/script events (EVENT_LOOT, EVENT_LOOT_COMPLETE, skinning, etc.) are NOT delivered through FiveM's `gameEventTriggered` / `CEvent*` handler — that's a GTA5/FiveM mechanism. Hooking `

Read the field note Finding / 48

Marshalling RDR3 native struct/array out-params: DataView with 8-byte stride, little-endian, zero-based offsets

## Context Several RDR3 natives return data through a caller-supplied byte buffer instead of a return value (notification toast structs, `GET_SCENARIO_POINTS_IN_AREA`, the game-event queue, weapon-DLC

Read the field note

Back to SCRIPTS

At a glance

Game: RedM
Namespace: SCRIPTS
Returns: BOOL
API set: client
Description source: rdr3natives

Before you call

Any* params are caller-supplied struct/array buffers (not scalar Pointer placeholders): build one with DataView.ArrayBuffer(8*N) and write every field — even Int32/BOOL — at zero-based, little-endian, 8-byte-aligned offsets, then pass view:Buffer(); consult the native's struct definition / linked findings for which fields are inputs vs outputs (read outputs back with GetInt32/GetInt64 at the same 8-byte stride) and whether each field is a CreateVarString-wrapped text field (UIFEED toast structs) or just a plain int / joaat hash — see get_invoke_guide. (see findings: learning:9, learning:48, learning:57, learning:58, learning:59, learning:81 — fetch via get_document)

Related references

rdr3_discoveries

Let your AI
read the fine print.

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

Connect via MCP