Native referenceRedM

_GET_ATTRIBUTE_CORE_OVERPOWER_SECONDS_LEFT

0xB429F58803D285B1 ATTRIBUTE

float _GET_ATTRIBUTE_CORE_OVERPOWER_SECONDS_LEFT(`ped` (Ped), `coreIndex` (int));

Property	Value
Native Name	`_GET_ATTRIBUTE_CORE_OVERPOWER_SECONDS_LEFT`
Hash	`0xB429F58803D285B1`
Return Type	`float`
Build	`1207`
Parameters	`ped` (Ped), `coreIndex` (int)

Parameters

ped (Ped)
coreIndex (int)

Usage

Lua (Direct):

local result = GetAttributeCoreOverpowerSecondsLeft(ped, coreIndex)

Lua (Hash):

local result = Citizen.InvokeNative(0xB429F58803D285B1, ped, coreIndex)

Back to ATTRIBUTE

At a glance

Game: RedM
Namespace: ATTRIBUTE
Returns: float

Before you call

Citizen.InvokeNative in CitizenFX Lua does not auto-marshal float/Vector3 returns — the result comes back wrong (community reports both a plain boolean and only-the-x-component-as-a-number); for these returns use the named Lua wrapper (e.g. GetEntityVelocity, GetPedBoneCoords, GetOffsetFromEntityInWorldCoords) or append Citizen.ResultAsVector() / Citizen.ResultAsFloat() as the final InvokeNative argument, and in JS/TS (no wrapper exists) Citizen.resultAsVector() / resultAsFloat() is mandatory; plain int/handle and void returns are unaffected. (see findings: learning:3, learning:17, learning:19, learning:24, learning:83 — fetch via get_document)

ATTRIBUTE overpower/core natives come in paired core vs non-core variants that are easy to mismatch with their setter, and values are often magic (e.g. _ENABLE_ATTRIBUTE_CORE_OVERPOWER only accepts 5000.0/0.0, not seconds). Verify the exact variant + value range against the linked findings. (see findings: learning:26, learning:27 — fetch via get_document)

Let your AI
read the fine print.

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

Connect via MCP