Startup Parameters Config File
The config file can be used to put startup parameters in, instead of specifying them at a shortcut/commandline.
Note
.par file does not (and will not) support some low level parameters, namely:
- -cpuCount
- -malloc
- -exthreads
- -maxMem=
- -profiles= (unconfirmed, but seems to not work for Arma 3)
The reason is those need to be initialized before any file operations are done.
Pre build 86060
Location
Inside game folder
Naming
Depending on game:
- ArmA2.par
- ArmA2OA.par
- TakeOnH.par
Format
class Arg
{
startupParameter="-startupParameter"
startupParameter2="-startupParameter2=value1;value2"
};
Example
class Arg
{
nosplash="-nosplash";
skipIntro="-skipIntro";
world="-world=none";
mod="-mod=Expansion;Expansion\beta;Expansion\beta\Expansion;@cwr2";
};
Post build 86060
Location
Location can be defined with -par=parameterFileName startup parameter. If file extension is .par the formatting described previously is required. With any other extension (like .txt) a plain text is assumed, with one command line option per line. In both cases the file is preprocessed before parsing, allowing C++ style comments and #define-s to be used.
Format
The file should be named "something.txt" using the .TXT extension, and not use the ".PAR" file extension. The ".PAR" file extension is apparently no longer read correctly on a dedicated server. The file can be located either inside or outside of the game folder for organizational purposes. Whitespace is ignored.
-startupParameter -startupParameter2=value1;value2 MissionFileToOpenInTheEditor
Example
-nosplash -skipIntro -world=none -mod=Expansion;Expansion\beta;Expansion\beta\Expansion;@cwr2 "c:\arma2\Users\USERNAME\missions\MissionName.Desert_E\mission.sqm"