UNITAF Future
UNITAF

Caution

This site is a work in progress

This site is finished to different degrees. Feedback is welcome. Please bear in mind that most of what you see, if not everything, is still a work in progress.

Data from the live site is synced here every hour. Anything you do on this site stays here. It is not copied back to the live site until we switch over.

Discord and permissions are linked. Be careful with admin actions. Some of them also change Discord.

UNITAF members taking orders before an operation
Force Manual

The FM outlines our core skills, policies and guides to ensure every member stands ready for the mission ahead.

FM/BG-1667 · v1.00

Mission file naming and export

Code
FM/BG-1667
Kind
Guide
Version
v1.00 7mos ago
Views
240
Platforms
As its document
Published by
Cpl Ross 10 Mar 2026
Last material change
v1.00 Initial Version

Mission file naming and export

Mission files used by the server follow a standard naming format:

[OrbatID].[TerrainName].pbo

To achieve this format, it is recommended to save the mission project using the OrbatID as the mission name when first creating it. If a mission was created before an OrbatID was assigned, the Save As function can be used to create a correctly named folder. Any accompanying mission files should also be copied into the new mission folder.

The mission .pbo is generated using the Export to Multiplayer function in the 3DEN editor. This process packages the mission folder and its files, including description.ext and cba_settings.sqf.

Exported missions are saved in the MPMissions folder located in the Arma 3 installation directory.