Aliases are handy shortcuts you can use when communicating with text pilots. They consist of a dot command, which is a period followed by any number of characters without whitespace (as in .ccvxm), followed by up to 9 optional parameters (such as .ccvxm 5,000 1a). Entering the above command will send the pilot the message "climb via SID except maintain 5,000. Departure frequency 124.500, squawk [assigned squawk].". You can see how this could save some time and hassle.
Aliases are defined in the alias file, which you should have downloaded from the controller downloads page and imported in VRC. The file consists of text only and is easy to read once you are familiar with the alias variables and functions published here. Below you can find a short list of aliases relevant to the clearance delivery position. This list is not exhaustive, so consult the alias file itself if you want to learn more.
This alias will send "clearance on request, standby...".
.cor# (sequence number)
Type ".cor# 2" to send "clearance on request, standby, you are number 2 in sequence...".
.cdt (departure) (transition)
Use this and the next two aliases for the first half of an IFR clearance (CR in CRAFT). This one is used when a pilot will follow a departure procedure with a transition. Type ".cdt padrz2 ikaye" to send "cleared to [destination] airport; PADRZ2 departure, IKAYE transition, then as filed;". This and many other aliases are case-insensitive: the alias will automatically convert the departure and transition names to uppercase.
Use this when you've given a route amendment for a full-route clearance. Whatever is currently in the route box of the aircraft's flight plan window will be sent (make sure you hit the "Amend Plan" button first!).
.ctec (TEC route code)
Type ".ctec sann4" to send "cleared to [destination] airport via the SANN4 TEC route;".
.ccv (departure sector ID)
This and the next two aliases are for the second half of an IFR clearance (the AFT in CRAFT). Use this alias when giving a "climb via SID" instruction when the SID contains a published top altitude and no intermediate altitude needs to be given. The departure sector ID can be found next to the controller's name in the controller list (for example, SCT_APP is 1A). Make sure the aircraft's cruise altitude is correct (and you've hit "Amend Plan") and that a squawk code has been assigned before using these aliases, as those items will be automatically added from the flight plan. Later on when you are controlling departure yourself, you can omit the sector ID and your frequency will automatically be used.
.ccvxm (altitude) (departure sector ID)
Use this alias for "climb via SID except maintain" instructions.
.calt (departure sector ID)
Use this alias for simple "maintain" instructions for when "climb via" is not appropriate. By default, 5,000 will be used for the initial altitude. If working an airport where a different altitude is needed, add it to the alias itself, e.g. ".calt7" at KLAS.
Add a "u" to the end of any of the above three aliases when no overlying radar controller is offline. ".ccvxmu 5,000", for example, will send "climb via SID except maintain 5,000, departure is offline, squawk [assigned squawk].".
The above aliases can be combined, as in ".cdt peble6 sxc .ccvxm 15,000 1a", for a quick one-line IFR clearance. This can be even faster than a voice clearance once you get the hang of it!
.(out/to)(lax/las/san)b and .vfrff (departure sector ID)
These are for VFR clearances. The first is for explicit bravo clearances, an example of which is ".outsanb" for "cleared out of the San Diego bravo airspace,". You'll have to type out your own departure and altitude instructions, then use ".vfrff 1a" for the departure frequency and squawk, if necessary. If departure is offline, use ".cdsu" for now until this alias is revised. If you're covering Los Angeles delivery, you can use ".laxvfrdp (left/right)" for the departure instructions, which will send "maintain VFR at or below 2,500 until clear of the BRAVO, make [left/right] crosswind departure at the shoreline,".
Type ".rbc 27" to send "readback correct, expect runway 27 for departure, advise ready to taxi.".
.rbcho (runway) (ground controller ID)
Use this during events when working delivery with a ground controller above you. It adds "contact ground on [frequency] when ready to taxi." to the end.
Add an "a" to the end of either of the above two aliases, along with the current ATIS code before the runway, when an ATIS is published. For example, ".rbca W 27".
TEC route codes
There are two ways to automatically add a TEC route to an aircraft's flight plan. Both require that the relevant flight plan window be open when the alias is sent in order to work.
The first is to use the three-letter identifier of the departure and arrival airports (ICAO code minus the "K") and the aircraft type code of p, m, or j. P and Q prop routes are nearly if not always identical, so only P is used in the aliases to avoid duplication. Examples are ".sanlaxj" or ".vnycrqm". These aliases do not (currently) work for the RNAV variants like the SANN4R. Make sure to delete the altitude information from the end of the route once you don't need it anymore.
The second option is to use the TEC route code itself, if you know it. For example, ".sann4r" or ".cstn12".