id: 1a.1-discord-communication title: 1A.1 Discord Communication meta: Discord Communication guidelines for Air Traffic Controllers within Infinite Flight. order: 1 auth: ifatc #

1A.1 Discord Communication #

Tip

: Infinite Flight app related issues can be discussed within the IFATC Discord Channels for advice; however, for official support, the IFC Forum must{.red} be used

General #

1A.1.1 #

Discord is a messenger app for teams to make work simpler, more pleasant and more productive. More information on how this app works can be found here.

1A.1.2 #

The channels and their use is outlined in the table below:

Channel Purpose
#atc-schedule The ATC Schedule briefing room channel can be used to brief/plan anything related to featured airports on any given day
#announcements Official Infinite Flight updates (such as new blog updates, new versions of the ATC Manual, and Beta information) to be made in this channel by the ATC Manager, Staff and Moderators only
#botcommands All bot commands should{.red} only be used in this channel. !command can be typed in this channel to bring up a list of available commands for use (see 1A.1.3 below)
#controllers All normal Controller communications to occur in this channel. This channel should not{.red} be used unless ACTIVELY controlling. Controllers can use the abbreviations found below this table when sending opening/closing messages instead of the full facility names if they prefer to do so
#discussions This is a channel for active Controllers to engage in discussion regarding IFATC, ATC, Infinite Flight, and aviation. Controllers that are CURRENTLY open should not{.red} be conversing in this channel unless operationally critical
#events The Events briefing room channel may be used to coordinate official and unofficial events such as FF, GA Day and streams
#flights This channel is used for Controllers to coordinate group flights together. All coordination should{.red} remain in this channel
#help-request If Controllers require support that cannot be found elsewhere, they can “raise” a ticket in this channel by reacting to the relevant role (for further guidance see 1A.2.4 below)
#ifatceg This channel contains news, tips and more brought to you by the IFATC Education Group
#infinite-flight-rules Highlights where to find the rules of the IFATC Discord server
#offtopic This is a channel to discuss things unrelated to IFATC or Infinite Flight. All conversations should{.red} remain appropriate. #offtopic is a privilege and all members are subject to removal at any time if misused. This is for active members only
#readonly Day to day posts (such as housekeeping and event specific procedures) to be made in this channel by the ATC Manager, Staff and Moderators only
#role-assignments Within this channel is a “notification opt in” menu - Controllers can react with the corresponding emoji to opt in and when the mentioned phrase is used, the Controller will receive a notification. Controllers that use the mentioned phrase must{.red} only use it when necessary to avoid spamming other Controllers (see 1A.3.1 below)
#screenshots This is a place to share Infinite Flight screenshots (in moderation). No other simulator, games, or off-topic content must{.red} be shared and all screenshots should{.red} be of a high quality
#social-media Automated official Infinite Flight social media updates. Controllers must not{.red} reply to any material posted in this channel so that all Controllers can be reached effectively
#training-time Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in (see 7.1.5 below)
#training-time[1-3] All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel must{.red} be used at any one time)

When Controllers send opening/closing messages, the following letters/abbreviations can be used if Controllers find it more convenient than using the full facility names:

  • G - Ground

  • T - Tower

  • S - ATIS

  • A or App - Approach

  • D or Dep - Departure

  • C or Center - Center

e.g. “EGLL GTS open”

Bot Commands #

1A.1.3 #

Below are some of the commands that can be used in the #botcommands channel:

Commands Purpose
/atis[icao] Shows current ATIS message for that particular airport
/atc Shows all open frequencies
.brief[icao] Generates an airport briefing including weather, general info, and charts
!commands Provides a list of all available commands that can be used
.charts[icao] Gives you the latest charts of the chosen airport
!feedbackstatus Check the status of any feedback provided for the ATC Manual
/find [name] Find a controller by real name or IFC username
/find [search phrase] This can be used to find a member of IFATC within Discord
/gmt Provides the current (local) time in GMT
.info[icao] Gives you general information about the chosen airport
!lightaircraft Lists the “light” aircraft within Infinite Flight
!manual Generates a link to the latest version of the ATC Manual
!manualfeedback Generates a link to the Feedback Form for the ATC Manual
.metar[icao] Gives you the live METAR of the chosen airport
/mystats Search for your IFATC statistics
/reference Provides quick IFATC references, rules and a link to the latest version of the ATC Manual
/schedule Shows a list of scheduled training/testing sessions in the next 48 hours
.taf[icao] Gives you the TAF of the chosen airport

Voice Channels #

1A.1.4 #

Voice Channels (VCs) must{.red} only be used in accordance with the Discord Rules (see 1A.2.1 below). Controllers who are operating an airport independently without assistance should not{.red} claim a VC unless:

1A.1.5 #

The use of VCs is not required{.red} and is at the sole discretion of the Controller (there may be select events where the use of VCs is required to guarantee operational efficiency - if this is the case, Controllers that do not wish to use voice may have to control elsewhere). Controllers who wish to observe others in a VC for educational purposes may ONLY do so if ALL operational Controllers in the VC have given consent. Observers must not{.red} distract from the active ATC operation and should{.red} remain muted.

1A.1.6 #

To open a VC, the following steps are to be followed:

Step 1

: Open the IFATC Discord and using the navigation bar on the left side of the screen, find the “Controlling” tab

Step 2

: Under this, click “Select to Create VC”, a new VC will be created with you as the owner of that channel. It will automatically be titled with your Discord username

Step 3

: The VC title must{.red} then be changed to an appropriate* name so that it is clear to other Controllers what the VC purpose is (see 1A.1.7 below)

*An appropriate name is one that provides no ambiguity - the standard or preferred naming is to use the ICAO code of the airport being controlled (e.g. EGPH) however if more than one airport is being controlled in a particular VC, then a more generic title can be chosen (e.g. New York Area, Oceanic Centers, Dubai Flyout Event etc.)

Tip

: Only the owner of the VC can change the name or user limit (see 1A.1.7 below)

1A.1.7 #

Below are the commands that can be used in the #botcommands Discord channel to manage a VC:

Commands Purpose
!voice-claim @[username] Claim ownership of the VC
!voice-limit [number] Change the user limit of the VC (the default is 10)
!voice-owner Will inform you who is the current owner of the VC
!voice-rename [ICAO code] Rename the VC
!voice-transfer @[username] *Transfer ownership of the VC

*Ownership can only be transferred to Controllers that are in the VC. VC owners should{.red} ensure that ownership is transferred before leaving the VC to avoid the channel being closed (channels will automatically close when vacant for 1 minute)

1A.1.8 #

Below are some useful tips for VCs: