modParams: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\{\{( *)Informative( *)\|" to "{{$1Feature$2|$2Informative$2|")
m (Text replacement - "\| *((\[\[[a-zA-Z0-9_ |()]+\]\],? ?)+) * \}\}" to "|seealso= $1 }}")
Line 57: Line 57:
|x1= <code>_data = [[modParams]] ["Kart", ["name", "logo", "picture"]];</code>
|x1= <code>_data = [[modParams]] ["Kart", ["name", "logo", "picture"]];</code>


| [[configSourceModList]], [[configSourceMod]]
|seealso= [[configSourceModList]], [[configSourceMod]]
}}
}}



Revision as of 23:54, 16 February 2021

Hover & click on the images for description

Description

Description:
Description needed
Groups:
Mods and Addons

Syntax

Syntax:
Syntax needed
Parameters:
[modClass, options]: Array
modClass: String - class name of the mod
options: Array - see description
Return Value:
Return value needed

Examples

Example 1:
_data = modParams ["Kart", ["name", "logo", "picture"]];

Additional Information

See also:
configSourceModListconfigSourceMod

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 April 24, 2017 - 21:25 (UTC)
Killzone Kid
This command used to spam .rpt when queried mod didn't exist, making it little awkward to use for testing if mod is active. For example: _superDuperModEnabled = modParams ["super_duper", ["active"]] param [0, false]; Since v1.69 the command would fail silently if mod didn't exist, but would still log .rpt error if the mod name passed to the command was empty or there was an error processing one of the passed options.