diag mergeConfigFile: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
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...)
m (Text replacement - "\] +\[" to "] [")
 
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:diag_mergeConfigFile}}
{{RV|type=command
{{Command


| arma3Diag
|game1= arma3


|1.00
|branch= diag


|gr1= Diagnosis
|version1= 1.00


| 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].
|gr1= Diagnostic
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
|gr2= Config


|p1= path: [[Array]] - The path to the config on your drive ([FileName,UserDir])
|descr= Updates config without restarting. Attributes and classes can not be deleted unless {{hl|[[Class Inheritance#delete|delete]]}} is used. Changes to the config are applied to all new entities, a mission restart is not necessarily required. Spawning the vehicle again or switching weapons works too. Since {{GVI|arma3|1.70}} CfgAmmo should be mergeable as well.
{{Feature|warning|Merging a config with an [[PreProcessor_Commands#.23include|include]] statement, that points to a non existing file, will crash the game.}}


| [[Nothing]]
|s1= [[diag_mergeConfigFile]] [path, userdir]
 
|x1= <code>[[diag_mergeConfigFile]] ["O:\Arma3\A3\Stuff_F\config.cpp"]</code>


|
|p1= path: [[String]] - absolute or relative path


}}
|p2= userdir: [[Boolean]] - (Optional, default [[false]]) path is relative to the user directory, otherwise it is relative to the mission directory
 
|r1= [[Nothing]]


<h3 style="display:none">Notes</h3>
|x1= <sqf>diag_mergeConfigFile ["O:\Arma3\A3\Stuff_F\config.cpp"]</sqf>
<dl class="command_description">
<!-- Note Section BEGIN -->
<!-- Note Section END -->
</dl>


<h3 style="display:none">Bottom Section</h3>
|seealso= [[Arma 3: Diagnostics Exe]]
{{GameCategory|arma3|New Scripting Commands}}
}}
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
{{GameCategory|arma3|Scripting Commands}}

Latest revision as of 11:46, 5 May 2024

Arma 3 logo black.png1.00
Hover & click on the images for description
⚠
Only available in Diagnostic branch(es).

Description

Description:
Updates config without restarting. Attributes and classes can not be deleted unless delete is used. Changes to the config are applied to all new entities, a mission restart is not necessarily required. Spawning the vehicle again or switching weapons works too. Since Arma 3 logo black.png1.70 CfgAmmo should be mergeable as well.
⚠
Merging a config with an include statement, that points to a non existing file, will crash the game.
Groups:
DiagnosticConfig

Syntax

Syntax:
diag_mergeConfigFile [path, userdir]
Parameters:
path: String - absolute or relative path
userdir: Boolean - (Optional, default false) path is relative to the user directory, otherwise it is relative to the mission directory
Return Value:
Nothing

Examples

Example 1:
diag_mergeConfigFile ["O:\Arma3\A3\Stuff_F\config.cpp"]

Additional Information

See also:
Arma 3: Diagnostics Exe

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
Retrieved from "https://community.bistudio.com/wiki?title=diag_mergeConfigFile&oldid=364163"