activateAddons: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= <code>[[activateAddons | |x1= <code>[[activateAddons]] ["BISOFP"];</code> |= Example 1 | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[unitAddons]] |= See also | | [[unitAddons]], [[activatedAddons]] |= See also | ||
}} | }} | ||
Revision as of 13:01, 6 March 2014
Description
- Description:
- Activates the listed addons. The list of active addons is initialized during this function.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
activateAddons ["BISOFP"];
Additional Information
- See also:
- unitAddonsactivatedAddons
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
Notes
-
Be aware that "Addon1" is the cfgPatches class of the desired addon to preload.
This command will activate addons that are referenced via scripts but not included in a missions required addons section. If executed from a configs init event with the call command, it will effectively override a missions required addons, preventing them from being activated (Appears to only happen in multi player).
To activate the passed addons along with those defined in the mission.sqm, execute the command from a configs init event using spawn or execVM. UNN