Core.threat_count_conditions.readField

Call as

Core.threat_count_conditions.readField(platform, object, key)

Record the dependency Core.threat_count_conditions.readField, then call it by that name. A namespaced call does not pass self: use a colon call or pass the object yourself.

What it does

Reads object[key] for the threat-count conditions without letting a restricted value, a non-table object or an index error escape.

Arguments

Name	Type	What it does
`platform`	`RMPlatform`	Platform whose CanReadValue decides readability.
`object`	`any`	Table to read, such as the addon or a unit snapshot entry.
`key`	`any`	Key to read, such as "unitsInRange".

Returns

1	`any`	The field's value (possibly nil), or nil on failure.
2	`string \| nil`	Reason on failure: restricted-value, invalid-unit-snapshot or unit-snapshot-read-error.

Editions

Built In helpers are registered on every edition. What differs is the game API they read; where one is missing the helper falls back or returns nil with a reason.

It reads no game API directly.

Secret values (Retail and Forever)

On Retail and Forever the game hands addons secret values. This helper checks what it reads (addon.Platform:CanReadValue) and returns nil with a reason such as restricted-value instead of a secret it cannot compare. Treat nil as unavailable, not as false.

How the addon calls it

Core.threat_count_conditions.GetConditionThreatCount

local snapshot,why=readField(platform,self,'unitsInRange')

Source

Core/threat_count_conditions.lua, line 33. Read only in game; Duplicate makes an editable copy.

Core.threat_count_conditions.readField(platform, object, key)

    if not platform:CanReadValue(object) then return nil,'restricted-value' end
    if type(object)~='table' then return nil,'invalid-unit-snapshot' end
    local ok,value=pcall(function() return object[key] end)
    if not ok then return nil,'unit-snapshot-read-error' end
    if not platform:CanReadValue(value) then return nil,'restricted-value' end
    return value

Back to Function reference