Naming a Mission

When creating an F3 mission for Folk ARPS, there are certain naming standards that should be followed.

These standards apply to two instances of the mission name: the name of the mission folder, which will become the PBO name, and the name in the Mission Attributes in the in-game Editor (this name is displayed in the slotting screen). In other instances such as description.ext, just use the title in plain text.

The mission name always begins with fa3. The remainder consists of three parts: the slotting code, the title, and the version number. The parts are separated by single underscores.

Slotting Code

The slotting code indicates the CDLC requirements, type of mission, and the number of slots.

The CDLC requirements indicate whether the mission requires Global Mobilization, CSLA Iron Curtain, or other CDLCs. If a mission requires GM, prefix with gm. If it requires GM and CSLA, prefix with gc. If it requires CLSA, prefix with c. If it requires SOG Prairie Fire, use pf. The CDLC code can be omitted if the mission requires no CDLCs, or if it only requires the same CDLC as the map it's set on (e.g. a mission set on Weferlingen that only requires GM).

The mission type indicates whether the mission is a Cooperative mission (c), Adversarial (a), Co-op Zeus (cz), or Rally (r). Sometimes afterparty missions use ap.

The slot count includes all playable units, except Reporters and Virtual Spectators. If it is a Zeus mission, count one Zeus, otherwise Zeus are not counted. If it is a mission where you can choose between multiple sides, but will only play as one side at a time, only count the largest side.

Example slotting code:

fa3_gccz41_...

Mission Title

The mission title should be the title of the mission. You can condense titles if they're very long, but try not to abbreviate or change major words, since the title needs to clearly identify the mission and be searchable. Underscores are usually used to separate words, and this is how SessionBot parses separate words when announcing missions in Discord.

Example mission title:

..._i_like_missions_...

Version Number

The version number indicates which version of the mission this is. It's important to version missions correctly so hosts select the right one to play. The version number should consist of a single whole number for each version, e.g. v1, v2, v3. Sub-versions such as v1.1 should not be used, partly because adding an extra period in the folder name breaks the mission, and partly because it can get confusing. Even for minor changes, use a full number.

For intermediate test versions that will only be used on the test server, you can use the format v1t1, v1t2, v2t1, etc. in order to avoid "wasting" a version number on experimental changes. However, the version transferred to main should always have a full number.

Note: new versions of missions should always have a new number. Versions with the same number can become confused.

Folder Name: Map Name

In the folder name specifically (not the name in the Editor Attributes) you must include the internal name of the map the mission is set on, so the game knows what's up. This is common to all Arma 3 missions. The map name is added at the end of the folder name, with a period followed by the name. Note that the internal map name is not always the same as the displayed name.

Internal names of BI and CDLC maps:

Display name	Internal name
Altis	.Altis
Stratis	.Stratis
Malden	.Malden
Tanoa	.Tanoa
Livonia	.Enoch
Weferlingen (Summer)	.gm_weferlingen_summer
Weferlingen (Winter)	.gm_weferlingen_winter
Cam Lao Nam	.Cam_Lao_Nam
Gabreta	.Stozec
Khe Sanh	.vn_khe_sanh
Normandy	.spe_normandy
Sefrou-Ramal	.SefrouRamal
The Bra	.vn_the_bra

Examples

A co-op mission on Stratis with 30 slots:

fa3_c30_mission_one_v1 (Editor) fa3_c30_mission_one_v1.Stratis (folder name)

An adversarial on Gabreta that uses GM assets:

fa3_gca28_mission_two_v3 (Editor) fa3_gca28_mission_two_v3.Stozec (folder name)