
                                                         
                                               
                   Flying Muffin Enterprises presents
      
      
                            Strategic FALCON
                         
                           Version 1.22 Update
                          Play-by-Email Support

  Preps & Cautions:
    
    For this to work, PKZIP and PKUNZIP must be available on your 
    computer--somewhere in your path.  Also, the DOS "ATTRIB"
    command must be available in your path.
    
    Also, this will OVERWRITE current campaigns in your FALCON 
    directory.  Make sure you back up any campaigns you have going 
    on!
    
  Background:
    
    This feature gives you the ability to set up campaign missions 
    for email distribution.  The actual implementation of play-by-email 
    rules is left up to you and your group.
    
    Whenever you save your files, StratFalc creates 6 new files in 
    your \STRAT directory. These are:
    
                             EMAIL0.CAM
                             EMAIL0.MIS
                             EMAIL0.SQU     
                             EMAIL0.MTV
                             EMAIL0.WAR
                             EISSION.0                         
              
    The "0" in the above file names will be replaced by the 
    proper number for the current squadron.          
                
    In addition, there are three new batch files included, also in 
    your \STRAT directory:  PACK, UNPACK, and RETURN.  These 
    will be explained by example:
    
    (1) The commander modifies the mission (if desired) in 
        StratFalc and saves his changes.  
        
    (2) The commander runs "PACK 0" (replace "0" with the 
        appropriate squad number. If necessary, run DIR EMAIL*.* 
        /OD; the newest files will be at the end of the list) to 
        package the files for transmittal. 
    
    (3) The resultant file (FALCMAIL.ZIP) is emailed to the 
        flier. 
    
    (4) The flier runs "UNPACK C:\FALCONCD\", which          
        installs the proper files into his Falcon directory. 
        The "C:\FALCONCD\" must be altered if necessary.
    
    (5) The flier attempts the mission in Falcon. 
    
    (6) After finishing the mission and generating the next 
        one (getting into the cockpit), the flier runs 
        "RETURN 0" from his Falcon directory. 
        
    (7) The RTRNFALC.ZIP file is then emailed back to the 
        commander, who unzips into his Falcon directory and 
        again modifies the file.
 
    This assumes a "central command" type of role.  This 
    is only one possibility.  Also possible would be an 
    "enemy command," which would receive the files before 
    the flier and modify them to make the mission more
    interesting.  
    
    Or, a "chain" type of campaign is possible, where the 
    commander modifies the mission; the flier flies it but 
    instead of returning the files directly to the commander 
    he then modifies the next mission using StratFalc and 
    either returns these files for his "commander" to fly, 
    or passes them to the next pilot in the squadron.
    
    Also, if you wish to include extra instructions or comments 
    with the file, you may create a file named "EMISSION.TXT." If 
    this file exists in your STRAT directory, the PACK script will 
    automatically include it in the resulting zip file.

