UOAF Event Checklist DCS

Notes and changelog

The wiki is public, I've left links out deliberately because I don't know what the access restrictions on the Google Drive are and don't want to accidentally expose something that's public but shouldn't be

TODO: Color code actions by role

• 2024-03-27: First created
  • Changed "Don't" to "DO NOT" under Pre-event actions for shutting down AWS instance
  • Stripped links, see above

Roles and Responsibilities

1. Mission Maker: Responsible for creating the scenario and briefing documents.
2. Package Leader: Leads package in-game, gives pre-flight briefing, formulates game-plan for missions requiring it.
3. Moderator: Performs checklisted items below, moderates flow of event, keeps those speaking during pre and post brief on task and professional.

Pre-event actions

These should be carried out as early as possible, ideally 7 days before the event

• Announce the event in Discord as early as possible. Sample announcement at the end of this document.
• Login to the AWS sometime before event day and accomplish the following:
  • Start DCS_Server.exe and check for updates.
  • Start SRS and check for updates.
  • Upload the .miz file to the “Missions” folder.
  • DO NOT forget to shutdown the AWS instance once you’re done.
  • Detailed instructions are available on the UOAF Google Docs
• If the package leader is not already selected ahead of time, monitor the signup sheet for package lead volunteers.
  • If required by the mission, reach out to the chosen package leader to form a game-plan by mid-week.
  • If required, distribute any updated briefing products they may produce.
  • If required, coordinate an early meeting of critical roles before event time.
  • If mission complexity doesn’t necessitate this level of pre-coordination, select package leader before briefing starts.
• Make sure a survey is ready to go for event (see Google Drive folder)
  • Make a copy of “UOAF DCS Mission Survey Template”
  • Update date and title info. DO NOT OVERWRITE TEMPLATE
  • Be ready to send a survey link via DM after the event.

Event-day actions

Pre-briefing

• 1 hour before event, ping @DCS_Events in #sunday-dcs-events channel reminding people of event time. Marshal 15 min before, brief on the hour.
• 30 min before the event, join Discord voice and start the AWS and login.
  • Once logged into the server:
    • Start DCS_Server.exe and login w/ UOAF DCS account if prompted.
    • Open DCS Server Web GUI and connect once the server is up.
    • Make sure the desired .miz is in the cue and run it.
      If you need to pause or restart the mission those controls are located at the top center of the GUI. If you need to restart the server, those controls are located in the chat window to the right.
• Instruct members in voice to connect to the server and test SRS.
  • As more members join voice, continually remind them to connect to the server and verify SRS and all keybindings are working.
• On the hour, welcome everyone to the event.
  • Welcome people to another UOAF DCS Event.
  • Introduce yourself as the moderator.
  • Introduce the package leader.
  • Introduce/thank the mission maker.
  • Give overview explaining order of days events:
    “The order of events today will be as follows:”
    • Package level brief.
    • Break into flight level briefs.
    • Reconvene in the briefing room for package level questions.
    • 5 minute bio break.
    • Play through the mission.
    • Go to the debrief channel once dead or the event is over for you.
    • Abbreviated debrief from package lead and flight leaders.
    • Announce the official end of the event.
    • Full length optional debrief with Tacview.
    • “Any questions about the order of events for today?”

Briefing

• Turn things over to the Package Lead to complete the briefing.
• Package Leader should:
  • Explain the plan to everyone.
  • Brief takeoff and landing order.
  • Brief overall package flow and contracts.
  • Make sure flight leaders understand/don’t have questions regarding tasking.
  • Footstomp critical “must complete” tasks.
• “Any package level questions regarding the game-plan?”
• Break into channels and complete Flight Level Brief.
• Flight Leaders should:
  • Explain how their flight fits into the game-plan.
  • Explain motherhood, threats, weapons, tactics, contracts.
  • Make sure any new players can do the things required of the mission.
• After flight briefs, members rejoin Briefing-Voice-Chat and Package Leader address any questions that came up during flight briefs.
• If no questions, instruct members to take a 5-minute bio-break.
• Grab a screenshot of attendees (for survey later).
• Instruct members to mute Discord voice chat microphone, but not their speakers.
  • Tell members to use in-game chat for any technical problems.
• Instruct members to join debrief when dead or finished.
• Restart server mission (if required) and the event is live!

Mission

Play the Mission