activateAddons: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) |
Lou Montana (talk | contribs) m (Text replacement - "<code>([^ ]*)\[\[([a-zA-Z0-9_]+)\]\]([^ ]*)<\/code>" to "<code>$1$2$3</code>") |
||
Line 29: | Line 29: | ||
|r1= [[Nothing]] | |r1= [[Nothing]] | ||
|x1= <code> | |x1= <code>activateAddons ["BISOFP"];</code> | ||
|seealso= [[unitAddons]] [[activatedAddons]] | |seealso= [[unitAddons]] [[activatedAddons]] |
Revision as of 11:01, 12 May 2022
Description
- Description:
- Activates the listed addons.
- Groups:
- Mods and Addons
Syntax
- Syntax:
- activateAddons addonsList
- Parameters:
- addonsList: Array of Strings
- Return Value:
- Nothing
Examples
- Example 1:
activateAddons ["BISOFP"];
Additional Information
- See also:
- unitAddons activatedAddons
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
- Posted on Jan 21, 2009 - 12:37 (UTC)
- Be aware that addon's string is the CfgPatches class of the desired addon to preload.
- Posted on May 10, 2009 - 11:17 (UTC)
- 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.
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint: Elite version 1.00
- Operation Flashpoint: Elite: New Scripting Commands
- Operation Flashpoint: Elite: Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Mods and Addons