View source for Arma Reforger:Startup Parameters

{{TOC|side}}
{{Feature|informative|Startup parameters' ''names'' are case-insensitive - e.g {{hl|-logstats}} and {{hl|-LogSTATS}} are identical.}}
{{TOC|subtoc
|content=
* 1. {{Link|#General}}
* 2. {{Link|#Window}}
* 3. {{Link|#Workbench}}
* 4. {{Link|#Hosting}}
* 5. {{Link|#Network Tuning}}
* 6. {{Link|#Debug}}
* 7. {{Link|#Profiling}}
}}


== General ==

=== addons ===

{{hl|-addons}} takes a list of mod IDs (specified in their gproj files, without brackets) to be loaded on game start, separated by a comma {{hl|,}}.<br>
Mods are searched in {{hl|profile/addons}}, in {{hl|&lt;executableDir&gt;/addons}} and in directories specified by {{hl|-addonsDir}} (see [[#addonsDir|below]]).
{{Feature|informative|
Mod IDs can be:
* GUIDs ('''preferred''' - found in {{hl|.gproj}})
* Project ID (found in {{hl|.gproj}})
* Sub-directory name (fallback solution)
}}

; Example
 ArmaReforgerSteam.exe -addons 88037E46AD234C72,88037E46AD234C73

=== addonsDir ===

{{hl|-addonsDir}} specifies additional directories in which the game must look for mods to load, separated by a comma {{hl|,}}.
{{Feature|informative|
By default, the game looks into:
* {{hl|Documents/My Games/ArmaReforger/profile/addons}}
* {{hl|&lt;executableDir&gt;/addons}}
}}
{{Feature|important|It is recommended to use ''absolute'' paths to Mod directories even though the provided path ''can'' be relative to the executable location.}}

; Example
 ArmaReforgerSteam.exe -addonsDir D:\DownloadedMods

=== addonDownloadDir ===

{{hl|-addonDownloadDir}} specifies where the game and the Workshop should download addons. Downloaded addons will be stored in addons subfolder inside of target directory.
{{Feature|important|It is recommended to use ''absolute'' paths to Mod directories even though the provided path ''can'' be relative to the executable location.}}{{Feature|informative|It is not necessary to combine this command with '''addonsDir''' parameter}}
; Example
 ArmaReforgerSteam.exe -addonDownloadDir D:\DownloadedMods

=== GPUAdapter ===

{{hl|-GPUAdapter}} forces to use the graphic card at the provided index. GPU index can be found using {{Link|https://support.microsoft.com/en-us/windows/open-and-run-dxdiag-exe-dad7792c-2ad5-f6cd-5a37-bf92228dfd85|DxDiag}}.

; Example
 ArmaReforgerSteam.exe -GPUAdapter 0

=== language ===

{{hl|-language}} sets the game language by language code - supported language codes depends on StringTable which is set in gproj. {{armaR}} supported languages are:
{{Columns|4|
* [[File:flag_uk.gif]] {{hl|en_us}} - English
* [[File:flag_france.gif]] {{hl|fr_fr}} - French
* [[File:flag_italy.gif]] {{hl|it_it}} - Italian
* [[File:flag_germany.gif]] {{hl|de_de}} - German
* [[File:flag_spain.gif]] {{hl|es_es}} - Spanish
* [[File:flag_czechrep.gif]] {{hl|cs_cz}} - Czech
* [[File:flag_poland.gif]] {{hl|pl_pl}} - Polish
* [[File:flag_russia.gif]] {{hl|ru_ru}} - Russian
* [[File:flag_japan.gif]] {{hl|ja_jp}} - Japanese
* [[File:flag_korea.gif]] {{hl|ko_kr}} - Korean
* [[File:flag_portugal.gif]] {{hl|pt_br}} - Portuguese
* [[File:flag_china.gif]] {{hl|zh_cn}} - Mandarin
}}

; Example
 ArmaReforgerSteam.exe -language cs_cz

=== noBackend ===

{{hl|-noBackend}} disables backend-related http communication.

; Example
 ArmaReforgerSteam.exe -noBackend

=== noSound ===

{{hl|-noSound}} disables the sound system processing.

; Example
 ArmaReforgerSteam.exe -noSound

=== noSplash ===

{{hl|-noSplash}} skips splash screens on game load.

; Example
 ArmaReforgerSteam.exe -noSplash

=== noThrow ===

{{hl|-noThrow}} disables all kinds of error message dialogs. (VME's, asserts, crashes, ...).

; Example
 ArmaReforgerSteam.exe -noThrow

=== profile ===

{{hl|-profile}} defines the path to the {{hl|profile}} directory to be used, either by parent directory name or by path.

; Example
 ArmaReforgerSteam.exe -profile "David Armstrong"								// targets {{hl|%userprofile%\My Documents\My Games\David Armstrong\profile}}
 ArmaReforgerSteam.exe -profile "C:\Users\MyUserName\Documents\ArmaReforgerDir"	// targets {{hl|"C:\Users\MyUserName\Documents\ArmaReforgerDir\profile"}}


=== singleThreadedUpdate ===

{{hl|-singleThreadedUpdate}} disables multithreaded update.

; Example
 ArmaReforgerSteam.exe -singleThreadedUpdate

=== world ===

{{hl|-world}} defines the world file to be loaded on startup, both absolute and relative paths are supported although it is recommended to use path relative to created filesystems (eg. worlds/myworld.ent). Workbench ignores this parameter - for that, use [[#load|-load]] parameter instead.

; Example
 ArmaReforgerSteam.exe -world worlds/myworld.ent


== Window ==

=== window ===

{{hl|-window}} starts the game windowed (fullscreen by default).

; Example
 ArmaReforgerSteam.exe -window

=== posX ===
=== posY ===

{{hl|-posX}} and {{hl|-posY}} define the initial window position. They must be used with {{hl|-window}}.<br>
posX 0 is left of the screen,<br>
posY 0 is top of the screen.

; Example
 ArmaReforgerSteam.exe -window -posX 0 -posY 64

=== screenWidth ===
=== screenHeight ===

{{hl|-screenWidth}} and {{hl|-screenHeight}} define the window's size (and not its render ''resolution''). They must be used with {{hl|-window}}.

; Example
 ArmaReforgerSteam.exe -window -screenWidth 1024 -screenHeight 578

=== forceUpdate ===

{{hl|-forceUpdate}} forces the application to render and update even when the window is out of focus.

; Example
 ArmaReforgerSteam.exe -forceUpdate

=== noFocus ===

{{hl|-noFocus}} prevents window focus stealing on game initialization.

; Example
 ArmaReforgerSteam.exe -noFocus


== Workbench ==

{{Feature|important|These parameters apply to the Workbench executable.}}

=== wbModule ===

{{hl|-wbModule}} specifies which [[Arma Reforger:Workbench|Workbench]] module must be launched (with {{hl|[[#run|-run]]}}):
{| class="wikitable"
! Editor
! Entry (case-insensitive)
|-
| [[Arma Reforger:Resource Manager|Resource Manager]]
| resourceManager
|-
| [[Arma Reforger:World Editor|World Editor]]
| worldEditor
|-
| [[Arma Reforger:Particle Editor|Particle Editor]]
| particleEditor
|-
| [[Arma Reforger:Animation Editor|Animation Editor]]
| animEditor
|-
| [[Arma Reforger:Script Editor|Script Editor]]
| scriptEditor
|-
| [[Arma Reforger:Audio Editor|Audio Editor]]
| audioEditor
|-
| [[Arma Reforger:Behavior Editor|Behavior Editor]]
| behaviorEditor
|-
| [[Arma Reforger:Procedural Animation Editor|Procedural Animation Editor]]
| procAnimEditor
|-
| [[Arma Reforger:String Editor|String Editor]]
| localizationEditor
|}

{{Feature|informative|
* Parameters specified after the module name are considered to be parameters to the module specifically.
* The {{hl|[[#run|-run]]}} parameter must be added after each instance of {{hl|-wbmodule}} for them to launch.
}}

; Example
 ArmaReforgerWorkbenchSteam.exe -wbModule=WorldEditor -run

=== plugin ===

{{hl|-plugin}} specifies which [[Arma Reforger:Workbench|Workbench]] plugin must be launched (WorldTestPlugin, TextureImportTool, MaterialImportTool, WorldDataExport etc).

{{Feature|informative|
* Parameters specified after the plugin are considered to be parameters to the plugin specifically.
* Plugins are loaded for specific modules. Before loading a plugin specify the appropriate [[#wbmodule|wbmodule]].
}}

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=ResourceManager -plugin=ResavePlugin pluginArguments

=== run ===

{{hl|-run}} tells the executable to open the designated Workbench module (specified by {{hl|[[#wbmodule|-wbmodule]]}} usage).

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=WorldEditor -run

=== load ===

{{hl|-load}} tells the executable to open selected file in the designated Workbench module (specified by {{hl|[[#wbmodule|-wbmodule]]}} usage).
The file path can be specified either by absolute path, relative path, exact path or by resource name.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=WorldEditor -run -load "world/myworld.ent"

This will open up the [[Arma Reforger:World Editor|World Editor]] and load the {{hl|myworld.ent}} file.

=== packAddon ===

{{hl|-packAddon}} is the main parameter used for addon packing.

When no directory is specified (by using {{hl|{{Link|#packAddonDir}}}}), the directory from the last session is used.

When packing an addon for the first time, a new directory is automatically created in the same dir as {{hl|profile}}.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=ResourceManager -packAddon

=== packAddonDir ===

{{hl|-packAddonDir}}specifies the output directory where resulting PAKs will be saved.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=ResourceManager -packAddon -packAddonDir "D:\build\Green"

=== publishAddon ===

{{hl|-publishAddon}} is main parameter used for addon publishing.

It should be used only for publishing addon updates, and not for the initial publish because data from last session are used to fill in the blanks.

It can be used on its own, in combination with '''packAddon''' or in combination with parameters starting with "publishAddon".

When no directory is specified (by using '''publishAddonDir''') a directory from last session is used.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=ResourceManager -publishAddon

=== publishAddonDir ===

{{hl|-publishAddonDir}} specifies the pre-packed data directory (obtained by the {{hl|-packAddon}} parameter above).
When not specified, directory from the last session is used.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=ResourceManager -publishAddon -publishAddonDir "D:\build\Green"

=== publishAddonVersion ===

{{hl|-publishAddonVersion}} specifies the mod's version number.
When not specified, newest version found on back-end is used and it's last digit is automatically incremented.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbmodule=ResourceManager -publishAddon -publishAddonVersion "2.3.5"

=== publishAddonChangeNote ===

{{hl|-publishAddonChangeNote}} is an optional parameter that specifies a note to the provided update.

; Example
 ArmaReforgerWorkbenchSteam.exe -publishAddonChangeNote "Fix shading"

=== publishAddonPreviewImage ===

{{hl|-publishAddonPreviewImage }} is an optional parameter that which you can use to specify path to preview image file.

; Example
 ArmaReforgerWorkbenchSteam.exe -publishAddonPreviewImage "z:/mymod/my_preview_image.jpg"

=== publishAddonScreenshots ===

{{hl|-publishAddonScreenshots}} is an optional parameter that specify folder from where the screenshots should be taken. It is then automatically scanned for all valid image file types (jpg, png, bmp).

; Example
 ArmaReforgerWorkbenchSteam.exe -publishAddonScreenshots "Z:/mymod/screenshots"

=== scrDefine ===

{{hl|-scrDefine}} allows to determine a script preprocessor definition. Multiple ones can be chained using multiple {{hl|-scrDefine}}.
{{Feature|informative|This parameter also works for Client and Server executables.}}
<enforce>
#ifdef TAG_DEBUG
	Print("The TAG_DEBUG flag is defined.");
#else
	Print("The TAG_DEBUG flag is not defined.");
#endif
</enforce>

; Example
 ArmaReforgerWorkbenchSteam.exe -scrDefine TAG_DEBUG -scrDefine OTHER_FLAG
 ArmaReforgerSteam.exe -scrDefine TAG_DEBUG -scrDefine OTHER_FLAG
 ArmaReforgerServer.exe -scrDefine TAG_DEBUG -scrDefine OTHER_FLAG

=== wbBackendLogin ===

{{hl|-wbBackendLogin}} enforces a specific account to log in. Password is hidden console log.

; Example
 ArmaReforgerWorkbenchSteam.exe -wbBackendLogin myEmail@bistudio.com myPassword

=== noGameScriptsOnInit ===

{{hl|-noGameScriptsOnInit}} skips game scripts compilation on Workbench initialisation.
This results in a faster startup but with the need to recompile scripts before using any script-dependent elements (prefabs, configs, etc).

{{Feature|informative|Game scripts can be compiled in Script Editor using {{Controls|F7}}.}}

; Example
 ArmaReforgerWorkbenchSteam.exe -noGameScriptsOnInit

=== enableWARP ===

{{hl|enableWARP}} allows {{Link|https://docs.microsoft.com/en-us/windows/win32/direct3darticles/directx-warp|DirectX WARP}} (Windows Advanced Rasterization Platform) to create a virtual device for computers without a DirectX 12 device.
{{Feature|informative|This parameter does not force WARP, only allows it.}}

; Example
 ArmaReforgerWorkbenchSteam.exe -enableWARP

=== clearSettings ===

{{hl|clearSettings}}, as its name suggests, clears all Workbench user preference - window positions, preview settings, last opened files etc.

; Example
 ArmaReforgerWorkbenchSteam.exe -clearSettings


== Hosting ==

{{Feature|important|These parameters apply to the Server executable.}}

=== a2sIpAddress ===

{{hl|-a2sIpAddress}} sets Steam Query Protocol's Bind IP address.

; Example
 ArmaReforgerServer.exe -a2sIpAddress 192.168.1.10

=== a2sPort ===

{{hl|-a2sPort}} sets Steam Query Protocol's Bind port.

; Example
 ArmaReforgerServer.exe -a2sPort 7777

{{ArgTitle|3|autoreload|{{GVI|armaR|0.9.6}}}}

{{hl|-autoreload}} reloads the scenario when the session ends after the provided delay, without shutting down the server. Value is in seconds.

; Example
 ArmaReforgerServer.exe -autoreload 10

=== bindIP ===

{{hl|-bindIP}} can be used to override both [[Arma Reforger:Server Hosting#gameHostBindAddress|gameHostBindAddress]] and [[Arma Reforger:Server Hosting#gameHostRegisterBindAddress|gameHostRegisterBindAddress]] values present in [[Arma Reforger:Server Hosting#Configuration File|server config]].

; Example
 ArmaReforgerServer.exe -bindIP 192.168.1.42

=== bindPort ===

{{hl|-bindPort}} can be used to override both [[Arma Reforger:Server Hosting#gameHostBindPort|gameHostBindPort]] and [[Arma Reforger:Server Hosting#gameHostRegisterBindPort|gameHostRegisterBindPort]] values present in [[Arma Reforger:Server Hosting#Configuration File|server config]].

; Example
 ArmaReforgerServer.exe -bindPort 2302

=== config ===

{{hl|-config}} is used by servers to point to a JSON server configuration.
{{Feature|informative|See [[Arma Reforger: Server Hosting| Server Hosting]] for more information.}}

; Example
 ArmaReforgerServer.exe -config myConfigFile.json

=== listScenarios ===

{{hl|-listScenarios}} prints to game logs the scenario .conf file paths.

; Example
 ArmaReforgerServer.exe -listScenarios

; Result
{{GVI|armaR|0.9.9}} <spoiler text="Show Scenarios">
e.g:
 : --------------------------------------------------
 : Official scenarios (8 entries)
 : --------------------------------------------------
 : {ECC61978EDCC2B5A}Missions/23_Campaign.conf (Conflict - Everon)
 : {59AD59368755F41A}Missions/21_GM_Eden.conf (Game Master - Everon)
 : {90F086877C27B6F6}Missions/99_Tutorial.conf (Tutorial)
 : {2BBBE828037C6F4B}Missions/22_GM_Arland.conf (Game Master - Arland)
 : {C700DB41F0C546E1}Missions/23_Campaign_NorthCentral.conf (Conflict - Northern Everon)
 : {28802845ADA64D52}Missions/23_Campaign_SWCoast.conf (Conflict - Southern Everon)
 : {DAA03C6E6099D50F}Missions/24_CombatOps.conf (Combat Ops - Arland)
 : {C41618FD18E9D714}Missions/23_Campaign_Arland.conf (Conflict - Arland)
 : --------------------------------------------------
 : Workshop scenarios (8 entries)
 : --------------------------------------------------
 : {6EA2E454519E5869}Missions/CAH_Military_Base.conf
 : {7C491B1FCC0FF0E1}Missions/CAH_LeMoule.conf
 : {F1A1BEA67132113E}Missions/CAH_Castle.conf
 : {589945FB9FA7B97D}Missions/CAH_Concrete_Plant.conf
 : {2B4183DF23E88249}Missions/CAH_Morton.conf
 : {3F2E005F43DBD2F8}Missions/CAH_Briars_Coast.conf
 : {9405201CBD22A30C}Missions/CAH_Factory.conf
 : {1CD06B409C6FAE56}Missions/CAH_Forest.conf
 : --------------------------------------------------
</spoiler>

=== logStats ===

{{hl|-logStats}} allows to log performance statistics every (optionally) defined interval (in milliseconds).

; Example
: {{hl|ArmaReforgerServer.exe -logStats}} - logs every seconds
: {{hl|ArmaReforgerServer.exe -logStats 10000}} - only logs every 10s

; Result
: <code style="display: block">FPS: 60.0, frame time (avg: 16.7 ms, min: 9.3 ms, max: 23.7 ms), Mem: 3291106 kB, Player: 2, AI: 104, Veh: 0 (17), Proj (S: 12, M: 0, G: 0 | 12), RplItemsS: 410, RplItemsC0: 17068</code>
* FPS: <float> = Current server FPS value
* frame time (avg: <float> ms, min: <float> ms, max: <float> ms) = The average, minimum, & maximum server frame times
* Mem: <int> = The current memory usage in kilobytes as reported internally by the server
* Player: <int> = Number of current players
* AI: <int> = Number of current AI spawned on the server
* Veh <int> (<int>) = The value inside the parentheses is the current number of vehicles spawned on the server
* Proj:
** S: <int> = Number of active '''s'''hells
** M: <int> = Number of active '''m'''issiles
** G: <int> = Number of active '''g'''renades
** | <int> = Total projectiles
* RplItemsS: <int> = The number of dynamic (spawned during game) streams on the server
* RplItemsC0: <int> = The number of streams open to the client

{{Feature|important|The memory usage reported by {{hl|-logStats}} is a server approximation and is therefore not 100% accurate when compared with the operating system values.}}

=== maxFPS ===

{{hl|-maxFPS}} sets max FPS limit - useful for a server, or to force a client's max FPS.
{{Feature|informative|Also works on clients, even though the Video Settings FPS limitation option is preferred.}}

; Example
 ArmaReforgerServer.exe -maxFPS 30

=== server ===

This parameter instructs the executable to launch '''local''' server and '''load selected world'''.  When this parameter is used, config is ignored. Server parameter can be combined with {{Link|Arma Reforger:Startup Parameters#addons|addons}} & {{Link|Arma Reforger:Startup Parameters#addonsDir|addonsDir}} parameters to start a server with local mods, which can be useful when testing addon before uploading it Workshop.
 ArmaReforgerServer.exe -server "worlds/MP/MPTest.ent" -addonsDir "C:\MyModsDir" -addons MyCustomMod
{{Feature|important|These parameters apply to the Game executable.}}

=== client ===

{{hl|-client}} starts up an RplSession in local client mode. The session tries to connect to the provided IP.

; Example #1
 ArmaReforgerSteam.exe -client 127.0.0.1

; Example #2
; This will connect game to a [[Arma Reforger:Startup Parameters#server|locally hosted dedicated server]] and load the local MyCustomMod addon
 ArmaReforgerSteam.exe -client -addonsDir "C:\MyModsDir" -addons MyCustomMod


== Network Tuning ==

{{Feature|important|These parameters apply to the Server executable.}}

=== nds ===

{{hl|-nds}} Network Dynamic Simulation (nds) is a server feature that only streams in relevant replicated entities for each client. the provided value stands for diameter, or the number of cells which are being replicated - default is 2 in each direction. To turn the feature off use {{hl|-nds 0}}. A higher diameter will result in a bigger networked view range, lower server performance.

; Example
 ArmaReforgerServer.exe -nds 1

=== nwkResolution ===

{{hl|-nwkResolution}} defines what resolution Spatial Map cells should be set at in a 100..1000m range. Smaller resolution will result in less "pop-in" but lower networked view range. For high view range use high resolution, but small diameter.

; Example
 ArmaReforgerServer.exe -nwkResolution 500

=== rpl-reconnect ===

{{hl|-rpl-reconnect}} makes the replication try to reconnect instead of immediately raising connection failure.
{{Feature|important|Endless reconnection loop is designed for debug purposes only.}}

; Example
 ArmaReforgerServer.exe -rpl-reconnect

=== rpl-timeout-disable ===

{{hl|rpl-timeout-disable}} disables client/server timeout.
{{Feature|important|
If a connection stops responding, the server performance will start deteriorating until it will eventually run out of memory and crash.
This parameter is strictly for debugging purposes.
}}

; Example
 ArmaReforgerServer.exe -rpl-timeout-disable

=== rpl-timeout-ms ===

{{hl|rpl-timeout-ms}} sets the client/server timeout's value, in milliseconds.

; Example
 ArmaReforgerServer.exe -rpl-timeout-ms 10000

=== rpl-validation-rdb-disable ===

{{hl|-rpl-validation-rdb-disable}} disables the validation of clients resource database.
{{Feature|important|This should not be disabled in normal usage conditions. This is for development purpose only!}}

; Example
 ArmaReforgerServer.exe -rpl-validation-rdb-disable

=== rpl-validation-scr-disable ===

Disables the validation of clients scripts checksum.
{{Feature|important|This should not be disabled in normal usage conditions. This is for development purpose only!}}

; Example
 ArmaReforgerServer.exe -rpl-validation-scr-disable

=== rpl-validation-version-disable ===

Disables the validation of clients executable version.
{{Feature|important|This should not be disabled in normal usage conditions. This is for development purpose only!}}

; Example
 ArmaReforgerServer.exe -rpl-validation-version-disable

=== staggeringBudget ===

{{hl|-staggeringBudget}} defines how many stationary spatial map cells are allowed to be processed in one tick in 1..10201 range. If not set it uses "{{Link|#nds|-nds}}" diameter. A lower number will limit how many cells the server has to process per tick, but increase the time it takes for a client to have all relevant entities streamed in, if the server experiences significant performance drops on spawning/teleporting then the number is set too high, if you the client experiences "pop-in" of replicated items then the number is set too low.

; Example
 ArmaReforgerServer.exe -staggeringBudget 5000

=== streamingBudget ===

{{hl|-streamingBudget}} is the global streaming budget that is equally distributed between all connections. To decrement the budget, it uses the replicated hierarchy size of each entity that needs to be streamed in. It cannot go under 100 to prevent the system stalling. A lower number will limit how many entities the server has to process per tick, but increase the time it takes for a client to have that entity streamed in, if the server experiences significant performance drops on spawning/teleporting then the number is set too high, if the client experiences "pop-in" of replicated items then the number is set too low.

; Example
 ArmaReforgerServer.exe -streamingBudget 500

=== streamsDelta ===

{{hl|-streamsDelta}} is a tool to limit the amount of streams being opened for a client in range 1..1000 (default 100). If the difference between 'the number of streams the server has open' and 'the number of streams the client has open' is larger than the NUMBER then the server will not open any more streams this tick. To be adjusted based on average client networking speed.

; Example
 ArmaReforgerServer.exe -streamsDelta 200


== Debug ==

{{ArgTitle|3|AILimit|{{GVI|armaR|0.9.8}}}}

{{hl|-aiLimit}} sets the top limit of AIs. No systems will be able to spawn any AIs when this ceiling is reached (through <enforce inline>aiWorld.CanAICharacterBeAdded()</enforce> - see also {{Link/Enfusion|armaR|SCR_AIGroup}} and {{Link/Enfusion|armaR|SCR_ChimeraAIAgent}}).
{{Feature|informative|A value less than or equal to zero simply disables any possible AI.}}
{{Feature|important|This parameter applies to both hosted and singleplayer scenarios; while it can save performance, it can also break the experience!}}

; Example
 ArmaReforgerServer.exe -AILimit 32
 ArmaReforgerServer.exe -AILimit 0
 ArmaReforgerSteam.exe -AILimit 100
 ArmaReforgerSteam.exe -AILimit 0

=== debugger ===

{{hl|-debugger}} sets the script debugger to a specific address.
{{Feature|informative|The default value is localhost.}}

; Example
 ArmaReforgerServer.exe -debugger 192.168.0.5

=== debuggerPort ===

{{hl|-debuggerPort}} sets the script debugger to a specific port.
{{Feature|informative|The default value is 1000.}}

; Example
 ArmaReforgerServer.exe -debuggerPort 1040

{{ArgTitle|3|disableCrashReporter|{{GVI|armaR|0.9.7}}}}

{{hl|-disableCrashReporter}} disables the [[Arma Reforger:Crash Report#Crash Reporter|Crash Reporter]] from appearing/sending reports automatically.

; Example
 ArmaReforger.exe -disableCrashReporter

=== disableShadersBuild ===

{{hl|-disableShadersBuild}} disables shaders generation.

; Example
 ArmaReforgerServer.exe -disableShadersBuild

=== generateShaders ===

{{hl|-generateShaders}} forces shaders generation.

; Example
 ArmaReforgerServer.exe -generateShaders

{{ArgTitle|3|keepNumOfLogs|{{GVI|armaR|0.9.8}}}}

{{hl|-keepNumOfLogs}} sets the maximum amount of logs to keep (default: 10).

; Example
 ArmaReforgerServer.exe -keepNumOfLogs 3

=== log-rdb-checksum ===

{{hl|-log-rdb-checksum}} enables logging detailed information about RDB checksum computation (GUID and path in order in which they are added to checksum) for RDB checksum issues debugging.

; Example
 ArmaReforgerSteam.exe -log-rdb-checksum

=== log-scr-checksum ===

{{hl|-log-scr-checksum}} enables the logging of all script files used in compilation and their checksums.

; Example
 ArmaReforgerSteam.exe -log-scr-checksum

=== logAppend ===

{{hl|-logAppend}} makes logs to not be emptied on game start, keeping the history.

; Example
 ArmaReforgerSteam.exe -logAppend

=== logFS ===

{{hl|-logFS}} logs every ''F'''ile '''S'''ystem's read/write operation in {{hl|filesystem.log}}. This option is very demanding and can produce a big file in a short time, so it is to use with caution for debug purpose.

; Example
 ArmaReforgerSteam.exe -logFS

=== logLevel ===

{{hl|-logLevel}} allows for different log levels. Each level includes the ones below it (e.g {{hl|error}} includes error and {{hl|fatal}}).
Possible values range from {{hl|normal}} (where everything is logged) to {{hl|fatal}} (where only extreme issues are logged):
<!-- those are internal only - soz guys
* spam
* verbose
* debug
-->
* normal
* warning
* error
* fatal

; Example
 ArmaReforgerSteam.exe -logLevel warning

{{ArgTitle|3|logsDir|{{GVI|armaR|0.9.8}}}}

{{hl|-logsDir}} defines the directory by name (located in the {{Link|#profile}} directory) or {{GVI|armaR|0.9.8|size= 0.75}} by path, in which game instance specific data are stored like logs, memory dumps, temporary files etc.

; Examples
 ArmaReforgerSteam.exe -logsDir "DebugSession1337"								// targets {{hl|{{Link|#profile|&lt;profileDir&gt;}}\logs\DebugSession1337}}
 ArmaReforgerSteam.exe -logsDir "C:\Users\MyUserName\Documents\ArmaReforgerDir"	// targets {{hl|"C:\Users\MyUserName\Documents\ArmaReforgerDir"}} directly

=== noCrashDialog ===

{{hl|-noCrashDialog}} skips Crash Reporter's dialog and automatically sends crash reports.

; Example
 ArmaReforgerSteam.exe -noCrashDialog

=== keepCrashFiles ===

{{hl|-keepCrashFiles}} prevents Crash Reporter from cleaning crash files on successful crash sending.

; Example
 ArmaReforgerSteam.exe -keepCrashFiles

=== scriptAuthorizeAll ===

{{hl|-scriptAuthorizeAll}} disables the security popup about {{hl|RunCmd}}, {{hl|RunProcess}}, {{hl|KillProcess}} and (outside of profile directory) {{hl|FileIO}} operations.

; Example
 ArmaReforgerSteam.exe -scriptAuthorizeAll

=== VMErrorMode ===

{{hl|-VMErrorMode}} sets script VM's error reporting mode; possible values are:
* {{hl|silent}} - silently continues
* {{hl|log_only}} - logs the error then continues
* {{hl|full}} - shows the VME dialog, logs the error, then clicking "ignore" continues execution
* {{hl|fatal}} - logs the error then exits the game


== Profiling ==

=== checkInstance ===

{{hl|-checkInstance}} turns on script VM's memory allocations logging - see [[Arma Reforger:Script Profiling|Script Profiling]].

; Example
 ArmaReforgerSteam.exe -checkInstance
<!--
=== scriptExtProfiler ===

{{hl|-scriptExtProfiler}} turns on script VM's support for external [[Arma Reforger:Script Profiling|Script Profiling]].
{{Feature|informative|The External Profiler can also be enabled through the [[Arma Reforger:Diag Menu|Diag Menu]]: [[Arma_Reforger:Diag Menu#Statistics|Diag Menu > Statistics > Script prof. external]] set to {{hl|true}}.}}

; Example
 ArmaReforgerSteam.exe -scriptExtProfiler
-->

{{GameCategory|armaR|Support}}