CFG: Difference between revisions
m (added a note: if the game is naturally quit (so, not crashed) the player's keybindings will overwrite the binds in the config file (if you used a navmesh keybind before closing the game, you will have it on next launch) (it was painful finding out :( )) |
(serious clean up) |
||
Line 1: | Line 1: | ||
{{lang|CFG}} | {{lang|CFG}} | ||
'''.cfg''' | The '''.cfg''' file extension can be found everywhere and is not specific to [[Source]]. It is an abbreviation of ''configuration''. In [[Source]] games, a configuration file executes a list of [[console command | console commands]]. | ||
Source games usually have a folder dedicated to CFG files. Inside, the file <code>autoexec.cfg</code> is run when the game starts up, so you can easily put any commands that you don't want to enter each time into that. They can also be ran from the console using the {{ent|exec}} command: "<code>exec <cfgname></code>" where filename is the name of the configuration file, with or without the extension. Sometimes people put exec lines into the [[autoexec]], so that other CFG files are executed when the game starts up. | |||
CFG files can be further organized in subdirectories in the CFG folder, and referred to by [https://en.wikipedia.org/relative_path relative path]. | |||
{{tip|You can add comments to .cfg files by using // .}} | {{tip|You can add comments to .cfg files by using // .}} |
Revision as of 16:37, 22 October 2021
The .cfg file extension can be found everywhere and is not specific to Source. It is an abbreviation of configuration. In Source games, a configuration file executes a list of console commands.
Source games usually have a folder dedicated to CFG files. Inside, the file autoexec.cfg
is run when the game starts up, so you can easily put any commands that you don't want to enter each time into that. They can also be ran from the console using the exec command: "exec <cfgname>
" where filename is the name of the configuration file, with or without the extension. Sometimes people put exec lines into the autoexec, so that other CFG files are executed when the game starts up.
CFG files can be further organized in subdirectories in the CFG folder, and referred to by relative path.


Common CFGs
This is a table listing common .cfg files found in mods and games alike.
CFG | Description |
---|---|
autoexec.cfg | Ran on game start up. |
modsettings.cfg | Ran on game start up, unless not found in mod folder. |
config.cfg | Ran on game start up, this is created automatically when the player runs the game/mod for the first time. ![]() |
config_default.cfg | Ran when no config.cfg is present or the player clicks the 'Use Defaults' button in the keyboard tab in the options panel, see Customizing Options: Keyboard. |
chapter#.cfg | Ran when the player picks the chapter, with # being the chapter number, see Adding chapters to your mod. |
game.cfg | Ran every time a map is loaded. |
sourcevr_modfoldername.cfg | Template:2013 add Ran when the player enables VR, replace modfoldername with the name of your folder that gameinfo.txt is in. |
skill_manifest.cfg | Runs every time the map is changed, used to list the skill.cfgs to execute. |
360controller.cfg | Used for players using XBox 360 controllers, lists the controls for the controller. Todo: Find out when this is executed.
|
360controller-linux.cfg | Used for players using XBox 360 controllers on Linux systems, lists the controls for the controller. ![]() |
undo360controller.cfg | Used for players using XBox 360 controllers when they want to undo the effects of the controller. Todo: Find out when this is executed.
|
listenserver.cfg | Ran when a listen server is being started, and runs every time the map is changed. |
server.cfg | Ran when a dedicated server is being started, and runs every time the map is changed. |
valve.rc | Special cfg file with the .rc extension, it's ran on game start up and executes autoexec.cfg along with a few other commands. |
See also
- Mini-mod tutorial
- vtest - Alternative to cfg files.