Difference between revisions of "UOAF Event Checklist"

From UOAF Codex
Jump to navigation Jump to search
Line 24: Line 24:
 
#Landings at airbases follow the overhead break.
 
#Landings at airbases follow the overhead break.
 
#After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
 
#After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
 +
#We will commit as Taxi
 +
 
==Commit to 3D==
 
==Commit to 3D==
 
#Commit the server to 3D
 
#Commit the server to 3D

Revision as of 19:00, 22 April 2017

Event Start

  1. Bring up dedicated server
  2. Fill Reserved Slots
  3. Introduce Moderator/s
  4. Introduce Event
  5. Introduce Package Leader
  6. Handoff control to Package Leader

Package Leader Briefing

  1. Explain the Plan
  2. Answer Flight Leader questions

Flight Briefing

  1. Players move to Individual flight channels for briefing
  2. Flight leader explains the plan
  3. Answer questions

Pre-Flight Procedures

  1. Players return to Briefing Room
  2. Package Leader or Moderator/s answer any final questions
  3. IVC checks in flight order, as per briefing (F1)
  4. Take 3 minute break and sort out any IVC issues.

Moderator read SOPs

  1. TeamSpeak will be muted during the flight
  2. Use Shift-T to chat in game if you have technical issues
  3. If you have an issue close BMS and IVC. Get your issues sorted out, reconnect, verify that your issues are sorted and rejoin. Use Instant action to check flight controls.
  4. Landings at airbases follow the overhead break.
  5. After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
  6. We will commit as Taxi

Commit to 3D

  1. Commit the server to 3D
  2. Doubleclick your flight and your seat and save your data cartridge
  3. Commit taxi in flight order, as per briefing (F1)
  4. Mute Teamspeak