Return to atc.doc.new CVS log

Up to [Research Unix] / researchv10no / games / atc

Annotation of researchv10no/games/atc/atc.doc.new, revision 1.1.1.1

1.1       root        1: 
                      2: 
                      3: 
                      4:                 ATC With Plans
                      5: 
                      6: Delayed commands may be specified using the "@" command:
                      7: 
                      8:        @<location>,<command>[,<command> ...]
                      9: 
                     10: The comma is required after the location and between commands.
                     11: 
                     12: The command is any normal legal airplane control command.
                     13: 
                     14: A location may be any of the unique identified points on the screen:
                     15: entries, airports, or navaids.  Note that the navaids now have different
                     16: identifiers.  The navaid command still uses a '*' or ':'.
                     17: 
                     18: Example:  @3,AA2
                     19: 
                     20: A location may be further specified by giving the number of miles in
                     21: each direction from a known fix, e.g.
                     22: 
                     23:            @#sw3s2,ARE
                     24: 
                     25: which means at the point which can be reached by going three
                     26: miles SW from fix #, then two miles S, plane A should begin
                     27: a right turn until heading E.
                     28: 
                     29: When the plane specified in the command reaches the location, the
                     30: command is executed automatically.
                     31: 
                     32: The information command shows all delayed commands pending for that plane.
                     33: 
                     34: Stored commands for plane A (for example) may be expunged with
                     35: 
                     36:        <23> A?
                     37: 
                     38: 
                     39: 
                     40: Fine points:
                     41: 
                     42:        A plane can be given commands to take effect when it
                     43:        comes onto the screen; it need not be active to get the first
                     44:        commands for its delayed list.
                     45: 
                     46:        To issue a navaid command for a later navaid, give a delayed
                     47:        command to take effect at the NEXT navaid.  Since navaids are
                     48:        now identified differently, it will recognize the point and
                     49:        issue the navaid command when it arrives at the first one.
                     50: 
                     51: 
                     52: 
                     53: Movie mode:
                     54: 
                     55:        The flag -p=filename will save the keystroke file and timing
                     56:        information for a game in the specified file.  There is enough
                     57:        information to re-create the game ASSUMING you use the same
                     58:        version of ATC.
                     59: 
                     60:        To re-play the game in movie mode, use
                     61: 
                     62:                atc -m=filename
                     63: 
                     64:        The game will use the same seed as before, and the traffic
                     65:        pattern will be identical.  At any point the observer can
                     66:        interject commands.  Probably the only useful command will
                     67:        be to request information, since the remembered commands will
                     68:        still be inserted at the remembered time.
                     69: 
                     70: 
                     71: 
                     72: Flow control:
                     73: 
                     74:        When a game is started, ATC looks for the file <airspace>.flow
                     75:        in the directory /usr/rand/jim/atc to establish a traffic pattern.
                     76:         For example, if the airspace is Apple3, it uses the file
                     77:        /usr/rand/jim/atc/Apple3.flow .
                     78: 
                     79:        The flow file contains one line for each legal path through the
                     80:        airspace.  Each line is left-adjusted, and consists of an origin,
                     81:        the symbol "->" (for "goes to"), the destination, a space, and
                     82:        the relative frequency of this path.  The expected frequency for
                     83:        this path is its relative frequency divided by the sum of the
                     84:        relative frequencies for all the paths.  Some examples are:
                     85: 
                     86:                1->5 5
                     87:                1->8 10
                     88: 
                     89:                2-># 10
                     90:                2->% 5
                     91:                2->6 5
                     92: 
                     93:                %->% 5
                     94:                #->% 10
                     95: 
                     96:        Blank lines are ignored (for spacing).
                     97: 
                     98:        Any path with no relative frequency is assumed to have frequency 0.
                     99: 
                    100: 
                    101: Things to come:
                    102: 
                    103:        (1) There will be a capability for canned procedures.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.