Installation - CBATeam/CBA_A3 GitHub Wiki

What should I download?

Download the latest release of CBA from the releases

Installing the files.

Unpack the archives to a temporary folder. This will create a folder named @CBA_A3

First of all is to copy the @CBA_A3 folder into your game folder.

...\Steam\steamapps\common\Arma 3\@CBA\addons\  => contains all the PBO files.

And add the other mod editions depending on available games and editions, as listed above.

Adding CBA to the list of active mods

CBA should be added to your list of addons in the first position, so any other addons that depend on it can take advantage of it.

-mod=@CBA_A3;@anothermod;@cheeseymod

CBA will automatically start its scripts and will automatically be used by addons or missions that require it, so there is no need to do anything more than this.

Multiplayer

Server keys and signature verification

Server operators may want to control what addons and mods people may use when they connect to a server. This is done by enabling signature verification on the server itself. In short, that means you'll have this entry in the server config file:

verifySignatures = 1;

In order to allow players to connect with the CBA addons, copy the CBA server key from @CBA_A3\keys and put it in your server's "Keys" folder. Make sure to pick the correct server key for the version of CBA that you allow. For example, the CBA A3 RC7 hotfix 2 release key is named "cba_a3_rc7b.bikey".

Updating the server key

When a new version of CBA is released, there's also a new server key. For example, the v0.1.2 release comes with a server key file named CBA_v0-1-2.bikey whereas the 0.1.3 version has a new server key file - CBA_v0-1-3.bikey.

For this reason, server owners must replace the old CBA .bikey file with the newer one when an updated CBA package is released. Clients with a CBA version other than what the server allows will be rejected when they try to connect.