Note that anything that has more than one value has a after it, indicating an array, and its values are defined inside //Something about color, just leave it like this pbo)įor example, the cfgPatches for the WWAF_USArmy_Infantry folder would look like this (without most of the classnames): Required addons (.pbo names of all files containing assets used by the. Required version (IDK what it does, I just set it to 0.1 and it works) Units (All soldiers, vehicles, and backpacks created inside the. Inside the cfgPatches section you declare the name of your file, and inside that, you declare a few things. In all parts of your mod, settings are added by declaring the class, and then changing the parameters. Generally, the first thing in your config.cpp file is the cfgPatches section. This is the only folder necessary to create the mod config.cpp structure: Each folder must contain a file called config.cpp. pbo files are created using Arma 3 Tools' Addon Builder, giving it a valid folder to start from. pbo (compressed) files and a file called mod.cpp (mentioned later) go. Strings (words) must go in quotation marksĮach mod starts in a folder labelled Inside this folder is a folder labelled 'Addons' in which the. Every line of code must end with a semicolon ( )Ģ. Assuming you know the basics of coding, there are only a few things to make sure you know:ġ.
