-
Vehicles 147
-
Light vehicles
-
Armoured vehicles
-
Tiltrotor aircraft
-
Naval craft
-
Vehicle-mounted weapons
-
-
Planning and Execution 155
-
Theatres and Campaigns
-
Deployment execution 57
- FM/G146 Introduction to Mission Support
- FM/G144 Leading as the Lead Game Master
- FM/G143 Assisting the Lead Game Master
- FM/G153 Using the Zeus interface
- FM/G145 Creating a fun battlefield
- FM/G159 Zeus modules
- FM/G147 Underlying Arma mechanics
- FM/G158 Handling ARMA bugs
- FM/G148 Roleplaying
- FM/G154 Scheduling a deployment
- FM/G407 Battle Management
- FM/G408 Operational Awareness
-
-
FMDG Communications
-
Radio Comms (Staging)
-
Reports (Staging)
-
FMDG Field Leadership
-
-
FMDG Rotary Wing
-
Loadout (Temp)
-
UNIHELP
Every role card
Command & Control
Ground Operations
-
Core Infantry 13
- Assistant Automatic Rifleman Verified
- Rifleman Verified
- Ammo Bearer Verified
- Grenadier Verified
- Automatic Rifleman Verified
- Interpreter Verified
- Assistant Machinegunner Verified
- Assistant Machinegunner, Heavy Verified
- Machinegunner, Medium Verified
- Machinegunner, Heavy Verified
- SF Operator Verified
- SF Gunner Verified
- Rifleman (Leadership Observer) Verified
-
Cavalry 12
- Light Vehicle Crewman (Driver) Verified
- Light Vehicle Crewman (Gunner) Verified
- Light Vehicle Crewman (Commander) Verified
- Light Vehicle Section Commander Verified
- AFV Crewman (Driver) Verified
- AFV Crewman (Gunner) Verified
- AFV Crewman (Commander) Verified
- AFV Section Commander Verified
- MBT Crewman (Driver) Verified
- MBT Crewman (Gunner) Verified
- MBT Crewman (Commander) Verified
- MBT Section Commander Verified
Air Operations
Support Operations
Scenario Operations
-
Mission Support 11
- War Correspondent Verified
- Civillian Roleplayer Verified
- Assistant Game Master Verified
- Mission Support Observer Verified
- Game Master (≤15) Verified
- Game Master (≤32) Verified
- Game Master (≤64) Verified
- OPFOR Roleplayer Verified
- Lead Game Master (≤15) Verified
- Lead Game Master (≤32) Verified
- Lead Game Master (≤64) Verified
FM/BG-763 · v2.02
Responding to pings
- Code
- FM/BG-763
- Kind
- Guide
- Version
- v2.02 1yr ago
- Views
- 446
- Platforms
- As its document
- Published by
- SPC Vyqe 17 Mar 2025
- Last material change
- v2.00 Changed the wording to be more organised. Added a section about the chain of command.
1 word added, 0 words removed.
v2.01
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 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.
v2.02
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.
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.
Where it appears
On role cards
On 11 role cards in 1 combat area.
Named on
-
War Correspondent
Mission Support
-
Civillian Roleplayer
Mission Support
-
Assistant Game Master
Mission Support
-
Game Master (≤15)
Mission Support
-
Game Master (≤32)
Mission Support
-
Game Master (≤64)
Mission Support
-
OPFOR Roleplayer
Mission Support
-
Lead Game Master (≤15)
Mission Support
-
Lead Game Master (≤32)
Mission Support
-
Lead Game Master (≤64)
Mission Support
The other 1 role reads it through these cards.
By combat area