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/G143 · Deployment execution

Assisting the Lead Game Master

Passages
3
Reading time
1 min
Views
89
Owned by
Unit Command
Platforms
Every platform
Role cards
11 cards
Published
23 Sep 2026
On this page

Act within the parameters set by the Lead Game Master

Work strictly within guidelines and constraints set by the LGM, no matter how large or small. This includes:

  • Follow the guidelines and constraints set by the LGM.
  • Avoid actions that could disrupt the mission or its objectives.
  • Seek clarification from the LGM when the parameters are unclear.

Keep the Lead Game Master informed

Keep the LGM informed about critical developments that happen during missions, including:

  • Player force progress: Provide timely updates on any advancements, setbacks, or major achievements by the player force.
  • Enemy spawning: Inform the LGM of spawned enemy forces and their locations, and for what purpose to maintain cohesive missions.
  • MASCAS events: Report mass casualty incidents quickly, including the extent and location of the event.
  • Technical issues: Communicate to them any technical issues impeding the operation, such as server performance or player connectivity problems.

Responding to pings

The general approach to responding to player pings is as follows:

  • Multiple pings: Respond to the ping for players who are pinging two or more times in quick succession; that is, three pings, or a series within 30–60 seconds, which usually means the player likely needs attention or assistance.
  • Single pings: Generally ignore single pings because these are usually accidental and require no action.

Note that wherever possible, player requests should be pushed through the chain of command rather than relying on pings. This provides better flow and does not create unnecessary interruption to the Lead Game Master or Mission Support Team. Only directly respond to pings if it's clear immediate action is required or the request cannot be serviced through the traditional command structure.

On role cards

Next in Deployment execution

FM/G153 Using the Zeus interface