For a description of the available "Actions" in the Updater, please review Six Updater Suite+Commandline

Game editions

The updater supports all editions of ArmA 2 at this time. By default it tries to auto-detect the edition through the registry, as well as certain variables to determine the specific edition (OA Standalone, or Combined Ops, etc).

You can select a settings profile for A2 Any autodetect, A2 OA autodetect, and A2 Standalone (specific), A2 OA Combined Ops (specific).

However you can also set other specific types (e.g OA Standalone), or even manually enter the path to arma and the exe name.

In that case, clone or create a new settings profile, and then set the Type field to whatever edition you desire.

Depending on the type of the used settings profile, certain mods will be ignored (disabled), or enabled (depending on dependencies). For example, the CBA_OA mod is only needed for OA Standalone users.

Betas

You can switch the "Beta" checkbox on any Settings Profile, to automatically use the official beta patch.

Servers

You can switch the "Server" checkbox on any Settings Profile, to automatically use the server exe's for your edition.

Advanced usage

Reset 'skip' status

The updater sets mods to 'skip' when the local version number matches the online version.
However, it doesn't verify if all your mod files are in order.
To do a full check (and repair) of your modfolders:

• Click Main
• Select your favorite preset, server, etc
• Uncheck 'autoskip'
• Click 'reset skip status'
• When it is done, click 'execute' with autoskip still disabled.
• The updater should now run and verify & repair your modfolders
• When completed, don't forget to enable autoskip again to speed up future operations

If you have weird version issues, please check #6806 (Clean your Virtual Store, and run software always as admin!)

Cloning a Record

If you want to make an exact clone of a preset, server, mod, etc. please click "Clone" next to Edit, Delete, Show.
The record's name will be prefixed with "CUST - " 
(Video example available)

Attaching custom mods to a preset

• To add any custom/non-server required mods, you must clone your stock/mod/community preset and edit accordingly.
• Mods that are required by servers, are already automatically loaded; please do not add them individually to a Preset.
• In the updater-client site, browse in the top menu to Presets (available in the SubMenu of "Configuration")
• At the preset of your choosing, click "edit" (on the right).
• At Mods, in the empty box, click select an additional mod from the list. Repeat this for every additional mod you would like to use.
• Click "Update" to save the changes.

NOTE: Incase you add mods of which the folder already exists in your arma installation,
but was not managed by the updater (not a rsync repository), please rename or delete this folder before using the updater to install the mod.

(Video example available)

Attaching a server to a preset

• In the updater-web-client site, browse in the top menu to Presets (Available in the SubMenu of "Configuration")
• At the preset of your choosing, click "edit" (on the right) (Or create a new one).
• At Servers, in the empty box, click and select a server from the list.
  • If the server requires a password, please feel free to enter it in the Password field.
• Click "Update" to save the changes.

Synchronizing with specific login credentials

ONLY If you have received specific login credentials.

• In the updater-client site, click in the top menu on Configuration specifically
• Pplease enter the Username and Password. (You can test your credentials on the portal site)
• Click "Synchronize"
• Synchronization is finished once you see a message on screen.

Using the console directly

(Only works properly after once web-client, main, "execute" or "save" Without Autoskip)

1. Start "Six Updater - Console" 
   Check Six Updater Suite+commandline for options you can add to the shortcut / commandline usage

This will update with the settings chosen previously.

Running web-interface on public-interface for remote management

Please add --bind=0.0.0.0 behind the shortcut parameters. You can then access the web-client from remote, on external IP If allowed by firewall. Additionally, add NO_BROWSER=1 to disable the integrated Iron Chrome Browser (iron.exe) from starting automatically, since it is not desired in this enviroment.

Example start from commandline:

C:\>cd \Program Files (x86)\Six-Updater
C:\Program Files (x86)\Six-Updater>tools\ruby\bin\ruby.exe -rubygems six-updater-web.rb --bind=0.0.0.0 NO_BROWSER=1