diag mergeConfigFile: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "_{10,} " to "") |
Lou Montana (talk | contribs) m (Text replacement - " *\| *([Cc]omments|COMMENTS|Game|[Gg]ame [Nn]ame|Game [Vv]ersion|Game Version \(number surrounded by NO SPACES\)|Multiplayer Arguments( \("local" or "global"\))?|Effects|Multiplayer Effects( \("local" or "global"\))?|Multiplayer Exe...) |
||
Line 1: | Line 1: | ||
{{DISPLAYTITLE:diag_mergeConfigFile}} | {{DISPLAYTITLE:diag_mergeConfigFile}} | ||
{{Command | {{Command | ||
| arma3Diag | | arma3Diag | ||
|1.00 | |1.00 | ||
|gr1= Diagnosis | |gr1= Diagnosis | ||
| Adjust configs on-the-fly without the need of restarting the game (by merging the given config file into the main config in memory). Location is relative to the Userdir (default) or mission directory depending on the the value of UserDir [FileName,UserDir]. | | Adjust configs on-the-fly without the need of restarting the game (by merging the given config file into the main config in memory). Location is relative to the Userdir (default) or mission directory depending on the the value of UserDir [FileName,UserDir]. | ||
Doesn't work with cfgAmmo & few other classes. (Since 1.69, cfgAmmo should be mergeable!) Merging config file means also that you can't delete parameters through diag_mergeConfigFile. Changes applied by diag_mergeConfigFile are applied to all new entities so restart of mission is not necessarily required - spawning vehicle again or changing back forth weapon should usually do the trick. | Doesn't work with cfgAmmo & few other classes. (Since 1.69, cfgAmmo should be mergeable!) Merging config file means also that you can't delete parameters through diag_mergeConfigFile. Changes applied by diag_mergeConfigFile are applied to all new entities so restart of mission is not necessarily required - spawning vehicle again or changing back forth weapon should usually do the trick. | ||
| '''diag_mergeConfigFile''' path | | '''diag_mergeConfigFile''' path | ||
|p1= path: [[Array]] - The path to the config on your drive ([FileName,UserDir]) | |p1= path: [[Array]] - The path to the config on your drive ([FileName,UserDir]) | ||
| [[Nothing]] | | [[Nothing]] | ||
|x1= <code>[[diag_mergeConfigFile]] ["O:\Arma3\A3\Stuff_F\config.cpp"]</code> | |x1= <code>[[diag_mergeConfigFile]] ["O:\Arma3\A3\Stuff_F\config.cpp"]</code> | ||
| | | | ||
}} | }} |
Revision as of 00:27, 18 January 2021
Description
- Description:
- Adjust configs on-the-fly without the need of restarting the game (by merging the given config file into the main config in memory). Location is relative to the Userdir (default) or mission directory depending on the the value of UserDir [FileName,UserDir]. Doesn't work with cfgAmmo & few other classes. (Since 1.69, cfgAmmo should be mergeable!) Merging config file means also that you can't delete parameters through diag_mergeConfigFile. Changes applied by diag_mergeConfigFile are applied to all new entities so restart of mission is not necessarily required - spawning vehicle again or changing back forth weapon should usually do the trick.
- Groups:
- Diagnosis
Syntax
- Syntax:
- diag_mergeConfigFile path
- Parameters:
- path: Array - The path to the config on your drive ([FileName,UserDir])
- Return Value:
- Nothing
Examples
- Example 1:
diag_mergeConfigFile ["O:\Arma3\A3\Stuff_F\config.cpp"]
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
[[Category:Introduced with arma3Diag version 1.00]][[ Category: arma3Diag: New Scripting Commands | DIAG MERGECONFIGFILE]][[ Category: arma3Diag: Scripting Commands | DIAG MERGECONFIGFILE]]