BIS_fnc_addStackedEventHandler

Warning

This function is deprecated.

Description

Caution

This information is obsolete as of Arma 3 v1.58. Reason: Arma 3: Mission Event Handlers should be used instead.

Stacks an event handler. All event handlers accept user arguments, which are passed to the EH code in _this variable. If the EH has own params returned in _this variable as well, user arguments are appended to the end of _this array. Note that if you try to add an empty EH, i.e. with empty code, it will simply be ignored.

Supported Event Handlers

Syntax

[id, event, code, arguments] call BIS_fnc_addStackedEventHandler

Parameters:

• id: String - custom id, a unique identifier. Adding same type of EH with the same id will overwrite existing
• event: String - event handler name, see description for supported EHs
• code: Code or String. The String is treated as function name
• arguments: Array of Anything - arguments to make available in code in _this array

Returns: String - custom id on success or "" on failure

Examples

Example 1

["someId", "onEachFrame", { hintSilent str time }] call BIS_fnc_addStackedEventHandler;

Example 2

["someId", "onEachFrame", {hintSilent str position (_this select 0)}, [player]] call BIS_fnc_addStackedEventHandler;

Example 3

private _eventName = "OnEachFrame";
missionNamespace getVariable [format ["BIS_stackedEventHandlers_%1", _eventName], []]; // gets an array with all existing ids

Multiplayer

This command has the same locality as addMissionEventHandler.

See also

addMissionEventHandler · BIS_fnc_removeStackedEventHandler

{
    [format ["%1", _forEachIndex], "onEachFrame", _code, [_x]] call BIS_fnc_addStackedEventHandler;
} forEach [var0, var1, varN, var100]; // pretty demanding

[_id, "onEachFrame", {
    { _x call _code } forEach [var0, var1, varN, var100];
}] call BIS_fnc_addStackedEventHandler; // faster, only one event