ezQuake Manual: Configuration manager

This client loads it's configuration on startup from config.cfg file which must be placed either in <home>/ezquake/config.cfg or in <quake>/ezquake/configs dirs (home = My Documents on Windows OS, ~ on linux).

This config is generated with cfg_save command. It is not recommended to create this config manually.

Commands

cfg_save [<filename>]

This command will dump all aliases, bindings, plus commands, msg_triggers, teamplay settings and variables to filename.cfg . User made variables (created with set/seta) are saved as well.

This command can also be called without any arguments. In such case it will create a file "config.cfg" either in quake/ezquake/configs or in ezquake subdirectory of your profile (home) directory. In windows such directory usually is in C:\documents and settings\yourname\my documents\ezquake\. In linux such directory is referred to as "~". Variable affecting this is cfg_use_home.

Note : configs saved with cfg_save are saved in quake/ezquake/configs/*.cfg

cfg_reset

This command will unbind all keys, delete all aliases, delete all msg_triggers, reset all plus commands, reset all teamplay settings and reset all variables. User made variables (created with set/seta) are deleted.

After resetting all the above, it executes default.cfg and then autoexec.cfg.

cfg_load <filename>

This will firstly do a cfg_reset and then execute filename.cfg.
When called without arguments it will attempt to read "config.cfg" first from ezquake directory in your profile directory or if it's not found in there, it will try to read it from quake/ezquake/configs directory (see cfg_save description).

Variables

cfg_use_home

Affects the behavior of cfg_save and cfg_load commands. When set to 0, it will load and save configs from/into quake/ezquake/configs. When set to 1, it will load and save configs from/into your home/ezquake/, where home is your profile dir (My Documents on Windows, ~ in linux).

cfg_save_unchanged

• 'cfg_save_unchanged 1' makes cfg_save write all variables to the config file.
• 'cfg_save_unchanged 0' makes cfg_save only write variables that are not default valued to the config file.

cfg_save_userinfo

• 'cfg_save_userinfo 2' makes cfg_save save all userinfo variables like name/team/teamcolor/rate/msg/skin/w_switch/b_switch/... .
• 'cfg_save_userinfo 1' makes cfg_save save all userinfo variables except spectator/name/topcolor/bottomcolor/skin/team .
• 'cfg_save_userinfo 0' makes cfg_save not save userinfo variables.

Note : 'cfg_save_userinfo 1' is best for teamfortress so you dont get kicked for changing bottom color.

Note : cfg_save will never save the password variable, even though technically it is a userinfo variable.

cfg_save_aliases

Toggles whether cfg_save saves aliases.

cfg_save_binds (default is 1)

Toggles whether cfg_save saves binds.

cfg_save_cmds (default is 1)

Toggles whether cfg_save saves commands.

cfg_save_cvars (default is 1)

Toggles whether cfg_save saves variables.

cfg_legacy_write (default 0)

• 'cfg_legacy_write 1' will write a small config.cfg to your gamedir when quitting just like qw 2.33.
• 'cfg_legacy_write 0' will not write config.cfg.

cfg_legacy_exec (default 1)

• 'cfg_legacy_exec 0' = Do not execute config.cfg and frontend.cfg in gamedir ever.
• 'cfg_legacy_exec 1' = Execute config.cfg and frontend.cfg in gamedir (unless gamedir = qw) like qw 2.33.
• 'cfg_legacy_exec 2' = Execute config.cfg and frontend.cfg even if gamedir = qw.
• 'cfg_legacy_exec 3' = Execute config.cfg and frontend.cfg even if gamedir = qw.
  If there is no config.cfg or frontend.cfg in gamedir, and gamedir != qw then try executing config.cfg and frontend.cfg in qw.

cfg_save_cmdline (default 1)

Writes your command line in configs made with cfg_save (commented out of course).

cfg_save_sysinfo

Not implemented yet.

cfg_backup (default 0)

Backs up your old config before overwriting it with cfg_save.
For example, 'cfg_save foo' will backup foo.cfg to foo.bak and then update foo.cfg .

Last update: 20.09.2007 13:47 UTC
ezQDocs