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-1668 · v1.00

Testing a mission

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

Testing a mission

Before a mission is played, key elements should be tested to ensure the scenario functions as intended.

Areas commonly checked include:

  • Player spawning in the correct location, ensuring clutter around respawn points does not cause incorrect spawn positions
  • Correct loadouts and Zeus access on spawn
  • 3DEN placed objects spawning correctly and not appearing rotated, misplaced, or destroyed
  • Headless clients connecting and spawning in their intended positions
  • Intended enemy and friendly factions available for spawning
  • Mission specific CBA settings applied correctly in the Mission tab of Addon Settings
  • Mission scripts functioning as intended, including testing with another player connected to confirm correct global and local behaviour