userconfig: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "{{GameCategory|{{arma3}}|Editing}}" to "{{GameCategory|arma3|Editing}}") |
Lou Montana (talk | contribs) m (Text replacement - "Category:Arma_2:_Editing" to "{{GameCategory|arma2|Editing}}") |
||
| Line 30: | Line 30: | ||
[[configFile]] is about the "global config" of unit types, vehicle types, and so on - this is the area added to by addons. | [[configFile]] is about the "global config" of unit types, vehicle types, and so on - this is the area added to by addons. | ||
{{GameCategory|arma2|Editing}} | |||
{{GameCategory|arma3|Editing}} | {{GameCategory|arma3|Editing}} | ||
Revision as of 23:38, 27 July 2020
How to make a Userconfig:
Some quick notes from what I learned while trying to use it for a mission. (a.k.a. What I wish somebody had written already) --MaHuJa
The \userconfig folder should be located in the root Arma 3 game directory, typically in your main Steam folder, \Steam\steamapps\common\Arma 3\
Description.ext
class X {
#include "\userconfig\MY_addon\Somefile.hpp"
};
\userconfig\MY_addon\Somefile.hpp
class Y {
key = value;
}
Use:
ucval = getNumber (missionConfigFile >> "X" >> "Y" >> "key")
Skipping class X means the user could introduce anything into the description.ext
Note that #include WILL fail with a CTD if the somefile.hpp doesn't exist.
missionConfigFile is used when the mission does the include from description.ext campaignConfigFile is similar but for a campaign configFile is about the "global config" of unit types, vehicle types, and so on - this is the area added to by addons.