           Quake 3 Test Base Configuration And Scripts
                 by Russell "Essobie" O'Henly
                    essobie@planetquake.com

WARNING!: Backup any configuration files you may have in both
your demoq3 before using any of these files! Essobie is not liable for
any damage to your configuration that these files may invoke.  YOU HAVE
BEEN WARNED!

        These configuration files are meant as a template for advanced
users and players so that they can learn a quick, easy-to-manage
configuration file structure that reduces strain on the end user
when changing, rearranging, or adding to their current configuration.

        It is NOT meant as an entire replacement to your own configur-
ation, unless of course you have absolutely no configuration to begin
with (or you just really like mine as is).

The Installation:
        Again, make sure you absolutely have a backup of every single
configuration file you have ANYWHERE in your Quake 3 directory structure.
If you have any files of the same name present in these directories,
they WILL be overwritten if WinZip is given the chance.
        Now... to install everything, simply open up the zip file you
have now, and extract all files to your /q3test/ directory, whereever
that may be on your computer WITH USE FOLDER NAMES TOGGLED TO ON.  This
is important because files need to go in certain folders... if you have
an reservations about doing it this way, unzip each file one at a time
and place it where it should go on your system according to the "path"
given in Winzip.

The Structure:
	The files are set up in such a way that at all times the
end user will know exactly where to find any setting, binding, or
alias that they want to alter or delete, and also to give direction
on where to place additions.

The Files:

SOBCFG.CFG: This file has no other purpose but to list the needed
files for the entire configuration to function.  It has but a single
alias (the w10 alias).  The rest of the lines are "exec" commands which
go through and execute each and every configuration file.  This file
should be in your demoq3 folder.

SETTINGS.CFG: This is the first file that SOBCFG.CFG makes reference
to, and contains exactly what its name implies: settings.  Game settings
such as "field of vision" or "fov", and sensitivity are found in this
file, as well as video modes, framerate caps, sound and input device
settings, and anything else that would normally be changed with a "set"
command.  Alterations to this file SHOULD be made before it is executed
by yourself.  If your video card doesn't like some of my settings, it
might not be pretty fixing the problem.  Should you have a problem with it
screwing up your settings, simply delete the Q3CONFIG.CFG file in your
demoq3 directory, and start Quake 3 over again.

This file is only executed by hitting F9 after BINDS.CFG has been parsed.

ALIASES.CFG: This file contains a long list of visibly separated sections
that contain alias commands that perform functions such as changing
settings on the fly, cycling through communication bindings, and any
other external or custom commands.  Under each "script" or group of 
commands, is a "remark" statement that begins with "//" which mentions
the proper bindings needed for the script to be bound to a button or key.
There are NO ACTUAL BIND COMMANDS IN THIS FILE.  This is to keep key
bindings from ever conflicting between two configuration files.  The
commands listed in these "remarks" are then bound using bind commands
in the BINDS.CFG file, mentioned below.

TALKIE.CFG: This file is just something I threw together for Team Play
Communication bindings... it isn't very useful to me really... mainly because
I don't practice using it.  It is a good example of how to insert your own
large scripts into the configuration and intergrate the bindings needed
into your BINDS.CFG file.

FUNNAME.CFG: This is my "famous" .cfg file that contains all the needed
color code high-ascii characters and instructions on how to make a colored
name simply by cutting and pasting a few characters (instead of downloading
some complicated program).  This is where I put my actual "name" command
instead of in settings.

This file is only executed by hitting F10 after BINDS.CFG has been parsed.

MODELVIEW.CFG: This is a script written by Andy "Artist" Smith for use in
cheat mode to view the player model in 3rd person from a number of angles.
Its great for looking at skin work... and for generally seeing just how cool
some of the id models are.  All the bindings for this script are removed from
this file and placed at the bottom of BINDS.CFG.  Again... this is so that
there are no conflicting bind commands anywhere in your configuration.

BINDS.CFG: This file is also separated into groupings in a very visable
manor so as to simplify finding certain keystrokes for any configuration
changes in the future.  When making a change to a command binding, always
do a "Find" in your text editor to make sure that you don't already have
a command bound to the key in question.

Example: say you want to have another key on your keyboard for the "+moveup"
command, and you would like to place it on the "Q" key.  Use your text
editor (Notepad, Wordpad, or the like) and do a find for "bind q".  If it
does not turn up a match, place a new bind command in the appropriate place
in the BINDS.CFG file.  If it DOES turn up a match, either change the current
binding to something other than "Q" (again, doing another search) or change
the "+moveup" command to another key.

At the bottom of the BINDS.CFG file is the "Verious Other Keys" section which has,
in order, all listed bindings for all aliases in the ALIASES.CFG file.
This makes adding aliases in the future very easy to do.  In fact, all
additional files (scripts) in your configuration should keep actual bind
commands to a minimum, and have a section added to the BINDS.CFG file
specifically for that new script (see "MODELVIEW.CFG" section in the BINDS.CFG
file).

For a list of key bindings, simply open up BINDS.CFG and take a look around.
It is quite self explainatory.  Cheers!


        Any Questions?  Comments?  Feel free to drop me a line.
                       essobie@planetquake.com
