BIS fnc loadEntry: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\| *(arg|eff|mp|serverExec|gr[0-9]) *= *(.*) * *\|([^=]{12})" to "|$1=$2 |descr=$3") |
Lou Montana (talk | contribs) m (Text replacement - "| arma3 |1.00 " to "|game1= arma3 |version1= 1.00 ") |
||
Line 1: | Line 1: | ||
{{RV|type=function | {{RV|type=function | ||
| arma3 | |game1= arma3 | ||
|version1= 1.00 | |||
|1.00 | |||
|gr1= Configs | |gr1= Configs |
Revision as of 22:40, 13 June 2021
Description
- Description:
- Searches for config entry in mission, campaign and then in global config file.
- Execution:
- call
- Groups:
- Configs
Syntax
- Syntax:
- [path,defaultConfig] call BIS_fnc_loadEntry
- Parameters:
- path: Array of strings - Path
- defaultConfig: Config - Default path used in case when the original one is not found
- Return Value:
- Array, Number or String
Examples
- Example 1:
[ ["CfgWeapons","hgun_Rook40_snds_F","bullet3"], configfile >> "CfgWeapons" >> "hgun_Rook40_snds_F" >> "baseWeapon" ] call BIS_fnc_loadEntry;
Additional Information
- See also:
- BIS_fnc_loadClassconfigFile
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