Native referenceRedM

_UI_FEED_POST_SAMPLE_TOAST

0x26E87218390E6729 UIFEED

int _UI_FEED_POST_SAMPLE_TOAST(`p0` (Any*), `p1` (Any*), `p2` (BOOL), `p3` (BOOL));

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 / 58

_UI_FEED_POST_SAMPLE_TOAST (0x26E87218390E6729) — left-card notification struct layout (dict/icon/color are joaat, not VarString)

## Context `_UI_FEED_POST_SAMPLE_TOAST` (`0x26E87218390E6729`) draws the left-side card notification. Its struct layout differs from the right-side toast — mixing them silently fails. ## The layout `

Read the field note

Back to UIFEED

At a glance

Game: RedM
Namespace: UIFEED
Returns: int

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)

Let your AI
read the fine print.

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

Connect via MCP