|  
             Here are some strategies for the nine classes in 
              Team Fortress. Engineer, Heavy 
              Weapons Guy, Medic, Scout, 
              Sniper, Soldier, 
              Spy, Pyro 
              and Demoman. 
            Thank Bard and his TF 
              Handbook for the most informative and concise class strategies 
              i've ever come across. 
            At the bottom of each page, you'll find class specific 
              aliases, config settings (all have keys bound to "X", 
              its up to you to decide what keys you want to use, read below) and 
              links to other resources concerning that class.  
              If you don't know what a config, script or alias is, be sure to 
              read the short tutorial below. 
             The 
              TF config 
            Occasionally you'll hear someone talking about 
              their config or .cfg files, to see what a cfg file looks like, fire 
              up notepad (Or use the best all around text editor in existance 
              and download EditPad) 
              and open up your config.cfg, its in your Quake/Fortress dir.  
              Don't change anything, save it as normal.cfg to your Quake/id dir, 
              NOT your Quake/Fortress dir! 
              Now, your normal.cfg should never be changed, for you'll use this 
              file as the basis for all your scripts, and if you ever screw up 
              your settings, just pull down console and type "EXEC NORMAL.CFG" 
              and VOILA, you have all your default settings back! 
            Since your config.cfg loads automatically at startup 
              from Quake/Fortress/ dir, this is the only .cfg file that should 
              be in your Quake/Fortress dir. Config files can be placed anywhere 
              and the directory can be selected through the user, with the Basdir 
              command or a proxy such as NF that allows you to select it. If you 
              have one file in Quake/ID1 directory and another in Quake/Fortress, 
              they will both execute.. 
            Before you make your class configs, its a good 
              idea to map out what keys are bound to what. Make a complete list 
              of your keys, A, K, S, F2, END etc. Now print off your config.cfg, 
              scratch out the keys that are used by the default binds in the config.cfg, 
              when your done...your left with a list of keys that are not bound 
              to anything, these will be the keys you will use for your class 
              configs & aliases. 
            This is the basic syntax for making binds in 
              a game:  
              Hit the ~key to bring down console, type bind X "command" where 
              X is the key you want bound, and "command" is the command 
              you want, then hit enter. The quotation marks are needed. 
            Whats an "alias"?! 
              Aliases are a combination of commands strung together, for example 
              lets bind a zooming function to mouse2 in an alias, allowing for 
              an on/off by simply hitting/releasing the mouse2 button. here goes: 
              alias +zooming "fov 22;sensitivity 4" alias -zooming "fov 90;sensitivity 
              14" bind mouse2 +zooming 
            Be sure to save your configs with the .cfg extension, 
              otherwise, you'll get a "COULDN'T EXEC .CFG" error, because 
              the .cfg file doesn't exist. 
              
            Other resources: 
              FTN's Config Tutorial 
              Quake 
              Console Tutorial 
              Team 
              Fortress Command List 
              TF 
              Handbook Config Files Explained 
              
             |