this document has been taken from standard Quake console but as SOF uses the quake engine there is little or no difference and as yet I have been unable to find a similar document specifically for SOF
This is the complete list of console commands, console variables, and command line parameters for Quake. All console commands and variables are identified, documented, tagged, and classified. This document has been designed to help out all those people who want to customize the game to their liking or just learn more about the console.
Click here to download this entire document in wordpad form
To use this document read and understand the following:
Console Command Lists “+,- & _” “A to F” “G to P” “Q to R” “S” “T to Z”
Trademarks and Servicemarks
All trademarks and servicemarks used in this work are acknowledged and are the property of their rightful owners. Quake is a trademark of id Software.
Warranty Disclaimer
THIS WORK IS PROVIDED "AS IS" WITHOUT ANY WARRANTY; WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE AUTHOR IS NOT LIABLE FOR ANY RESULTS ARRISING FROM THE USE OF THIS WORK. ALL RISKS AND RESULTS THEREOF FALL ON THE USER.
(this document was originally created by JakFrost)
Below there are explanations to all of the different fields which are used to describe each command. It is good to know what the information in each field contains and refers to. The fields that I have used to describe each command and variable are a way of standardizing information among each command and to make sure that all of the information is given in an orderly fashion.
I have also taken upon myself to classify all of those console commands and console variables. These classifications are in no way related to how the game feels about the various types of commands and variables. The game only distinguishes between commands and variables. The names of each class are only meant to identify the different type of a command or variable, and give some insight into it's syntax and what type of parameters it accepts. Basically if a user knows that a given variable is classified as a toggle, he won't try to use negative numbers or fractions as input, or if a command is classified as an operation he will know not to use any parameters. These classifications are just here to help you with the syntax recognition and to remove unnecessary syntax fields.
Status:
This field only appears for some of the commands and variables. This field holds the information about the status of the command. A status of Disabled will identify the command as still existing in the game but the command is no longer used, does not serve any function, or is broken. A status of Unknown means that the function of the command is not known. A status of Internal means that the command exist in the console but is only used internally by the game and it does not work when used by itself.
Game:
This field only appears for some of the commands and variables. This field is used to inform that the command is used only for the certain version of the game. In case of this document a value of GLQuake is used to identify commands which are only used for the GLQuake version of the game. A value of WinQuake is used to identify the command as only to be found in the WinQuake version of the game. If this field is omitted, then the command appears in both versions of the game.
Type:
This field appears for all commands and variables. The information in this field classifies the command or variable based on it's syntax. The inclusion of this field also allows for the shortening of this document by specifying one syntax for a whole class of commands or variables and not having to display the identical syntax for each command or variable. Further explanation about all of the different types of commands and variables that have been classified is included in the section below.
Syntax:
This field only appears for the class of function commands since each of those commands has it's own syntax. It displays the parameters that the command accepts and any other special characters. The convention of using words in parenthesis, i.e. (filename), designates that a single value should be specified which is described by the phrase inside the parenthesis and that it is necessary for the proper execution of a command, i.e. base1.bsp. When a parameter is in brackets, i.e. [relative path] then this parameter is optional for the execution of a the command. A syntax such as 'play [relative path/](sound file)[.wav]' can be expanded into a command such as 'play misc/water3' or 'play sndfile.wav'. Also, when the syntax includes the [relative path/] parameter the / character can also be substituted by the \ character.
Default:
This field only appears for the variables. It displays the default value that is used by the game when it is started for the first time. The information in this field displays the default value for any given variable which can be referenced when it is necessary to restore that variable to it's original setting.
Range:
This field only appears for register variables. It displays the minimum and maximum values that a given register is able to accept. This field will only appear for special registers which have a preset range for values which they can accept. Also, sometimes an interval value will appear after the number range. If this field does not appear then it means that the given register is able to accept all values or that the range for that variable cannot be determined. A range might look like '30 - 120' meaning that the variable is able to take a value which is between 30 and 120.
Binding:
This field appears for all commands which are bound to keys when the game is started for the first time. The information in this field lists the keys to which the commands are bound. The information about the default bindings is contained inside the default.cfg file inside the pak0.pak file.
Description:
This field appears for all commands and variables. It displays a short description of the command or variable. This is just a reference field for a quick glance at what the command or variable does and it's general purpose. For a more detailed description and some other information refer to the Note: field if it exists for a given command.
Note:
This field appears for some commands and variables. It displays a long, detailed description of the command or variable. Usually a lot of background information is displayed in this field if the command or variable has some special functions or special syntax is necessary. Sometimes I also include some personal recommendations about commands or the recommendations of other players.
Example:
This field only appears for the class of function commands since each of those commands has it's own syntax. It displays some examples of how the syntax should be used. For some commands this field is very necessary because some function commands have a very weird syntax.
List:
This field only appears for some of the commands. It displays a listing of all parameters that the command is able to use. This field will also be used for all toggle commands which have more settings than 0 and 1. Sometimes a description of each item is provided for each item and sometimes the items are just listed in a comma separated format if the items do not require a description.
Output:
This field only appears for certain commands which produce output to the console. It is sometimes necessary to show the output of the command to allow for a better visualization of the dCommands
Action:
An action command performs an action when the +action part of the command is executed and terminates that action when the -action part of the command is executed. When an action command is bound to a key, the +action is executed when the key is pressed, and the -action is executed when the key is released. The default syntax for an action is '+command' or '-command'. The syntax field is skipped for all action commands.
Function:
A function command performs a single function based on the parameters included for that operation. A function usually has extra parameters and they are usually necessary for proper execution. The default syntax for a function is 'command (parameter)'. The syntax field is present for all function commands since each one has it's own unique syntax.
Operation:
An operation command performs a single function in the game every time the command is executed. It does not use any parameters. The default syntax for an operation is 'command'. The syntax field is skipped for all operation commands.
Parameter:
A command line parameter is a variable which is set from a command line. The reason for setting a variable from the command line, is that some settings can only be used before the game actually loads up. Command line parameters are usually used to enable or disable a handful of features before loading up the game. The default syntax is 'game.exe -parameter' and the syntax field will be skipped for all parameters which do not accept any values. Sometimes the command line parameter requires a value then the syntax will be displayed.
Register:
A register variable is able to store any type of numeric information. Register variables are used for numeric data which does not have clearly defined boundaries. The default syntax for a register variable is 'variable (value)'. Allowable values for a register variable include integers, fractions, and negative values.
String:
A string variable is able to store any type of text information. The default syntax for a string variable is 'variable "(text)"'. Allowable values for a string variable include all numbers and all text characters.
Toggle:
A toggle variable is able to turn a feature on, off, or set it to an alternative setting. The values for a toggle are usually only 0 and 1. Sometimes there are alternative settings for a toggle, in which case subsequent numbers are used such as 2, 3, 4, and so on. The default syntax is 'variable (value)'. Allowable values for a toggle variable include integers only in increments of 1.