addMissionEventHandler: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) No edit summary |
Killzone Kid (talk | contribs) No edit summary |
||
Line 15: | Line 15: | ||
| '''addMissionEventHandler''' [type, command, args] | | '''addMissionEventHandler''' [type, command, args] | ||
|p1= [type, command]: [[Array]] | |p1= [type, command, args]: [[Array]] | ||
|p2= type: [[String]] | |p2= type: [[String]] |
Revision as of 15:40, 15 February 2021
Description
- Description:
- Description needed
- Groups:
- Event Handlers
Syntax
- Syntax:
- Syntax needed
- Parameters:
- [type, command, args]: Array
- type: String
- command: Code or String - By default executed in missionNamespace
- args (Optional): Array - (Since Arma 3 v.2.03.147276) additional arguments to be passed to the EH code. Available during code execution via _thisArgs variable.
- Return Value:
- Return value needed
Examples
- Example 1:
// A script could be executed to stop custom scripts graciously, or save progress & stats, for example: _id = addMissionEventHandler ["Ended", { _this execVM "missionEnded.sqf" }];
- Example 2:
- Since Arma 3 v.2.03.147276:
_id = addMissionEventHandler ["EachFrame", { systemChat str [_thisArgs, time]}, [time]];
Additional Information
- See also:
- See also needed
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note