View on GitHub

ezQuake

Demos

Demo Handling

cl_demoPingInterval
Description:
How often to request ping updates when recording demos. This variable doesn't affect ping updates when the scoreboard is shown (they are always one update per 2 seconds).
Type:
integer
ValueDescription
0Disable automatic ping requests.
5Request every 5 seconds (default).
cl_demospeed
Description:
Controls the speed of demo playback in percentage (can be changed during demo playback if you wish).
Type:
float
cl_demoteamplay
Description:
If set, teamplay settings enabled during .dem playback.
Type:
boolean
cl_startupdemo
Description:
Demo that should be played on client's startup.
Type:
string
ValueDescription
File name of the demo.
demo_autotrack
Description:
Enables server-side autotrack to be accepted
Type:
boolean
Remarks:
Server-side autotrack is recorded in MVD demos and in QTV stream allowing all the observers of the match observe the same player at the same time
ValueDescription
false
true
demo_benchmarkdumps
Description:
Allows you to automatically dump timedemo benchmark results into $log_dir/timedemo.log file. The output is in XML markup format and contains info about your operating system, hardware configuration, client version, rendering, screen resolution and the result FPS.
Type:
boolean
Remarks:
See timedemo command description for more info. Note: The result file is not a well-formed XML file.
ValueDescription
falseDisable timedemo result dumping
trueDump results of timedemo benchmark
demo_capture_codec
Description:
Determines what codes should be used for captured video stream compression. E.g. XVID, DIVX, ...
Type:
float
demo_capture_dir
Description:
Change the default capture directory.
Type:
string
demo_capture_fps
Description:
Change the default capture fps.
Type:
float
demo_capture_mp3
Description:
When set to 1 .avi capturing captures sound compressed in MP3 format.
Type:
boolean
Remarks:
See demo_capture_mp3_kbps too.
ValueDescription
falseCaptures uncompressed sound
trueCaptures sound in MP3 format
demo_capture_mp3_kbps
Description:
Sets bitrate for captured sound stream when demo_capture_mp3 is set to 1.
Type:
float
demo_capture_quiet
Description:
Stops sound being played during demo capture
Type:
boolean
demo_capture_steadycam
Description:
Changes behaviour of keyboard/mouse input when capturing.
Type:
float
demo_capture_vid_maxlen
Description:
If set, multiple files will be created. This variable determines length in seconds of each file
Type:
integer
demo_dir
Description:
Change the demos and autorecord directory.
Type:
string
demo_format
Description:
Specifies the demo file format used when recording demo with Match tools.
Type:
enum
Remarks:
See qwdtools_dir, qizmo_dir, match_auto_record.
ValueDescription
mvdMultiView Demo, usually contains less frames per second.
qwdOriginal QuakeWorld demo format.
qwzQizmo compressed demo.
demo_getpings
Description:
This toggles whether the client should always record pings into the demo or only
when the player died and show(team)scores are being shown (QWCL default).
Type:
boolean
ValueDescription
falseonly update pings in the demo when the player died and show(team)scores
are being shown
truealways update pings
qizmo_dir
Description:
Change the default qizmo directory.
Type:
string
qwdtools_dir
Description:
Specifies the qwdtools utility placement
Type:
string
ValueDescription
Use path relative to you quakedir

Match Tools

match_auto_logconsole
Description:
When set to 1 or 2, a temp console log will automatically be created when a match starts (usually when the countdown starts).
Type:
enum
ValueDescription
0Do not auto-log console.
1Auto record console but requires manuall saving. See 'match_save'.
2Automatically saves the console log after the match is completed.
match_auto_logupload
Description:
Automatically upload match console log to remote server specified in match_auto_logurl.
Type:
boolean
ValueDescription
false
true
match_auto_logupload_token
Type:
string
match_auto_logurl
Type:
string
match_auto_minlength
Description:
When using 'match_auto_record 2', temp demo's auto recorded won't be saved automatically if they are shorter than the number of seconds match_auto_minlength' is set to.
Type:
integer
Remarks:
If a temp demo is too short to autosave, you can still save it manually with "match_save".
ValueDescription
number of seconds
match_auto_record
Description:
When set to 1 or 2, a temp demo will automatically be recorded when a match starts (usually when the countdown starts).
Type:
enum
ValueDescription
0No auto recording.
1Demo will be recorded but requires manual saving with match_save
2Automatically saves the demo after the match is completed.
match_auto_spectating
Description:
When set to 1, auto recording will also occur when in spectator mode.
Type:
boolean
ValueDescription
falseDon't auto record demos in spectator mode.
trueAuto record demos even in spectator mode.
match_auto_sshot
Description:
Set to 1 to automatically take a screenshot of the final scoreboard when a match ends. If your console is down or you are in the menus, then the client will remove the console/menu for a split second so it can take a screenshot of the scoreboard without any interference.
Type:
boolean
ValueDescription
falseDo not take auto screenshot.
trueTake auto screenshot on match end.
match_auto_unminimize
Description:
Bring client from minimized state on countdown start.
Type:
boolean
Remarks:
Only works on KT* servers.
ValueDescription
false
true
match_challenge
Description:
When enabled, sends announcements to duel ladder server about match start and match end. Can be activated by special startup *.qw file or by opening special qw: URL.
Type:
boolean
ValueDescription
false
true
match_challenge_url
Description:
Web address where POST requests announcing challenge match start and end will be sent.
Type:
string
match_format_2on2
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 2 people)
match_format_3on3
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 3 people)
match_format_4on4
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 4 people)
match_format_arena
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "arena")
match_format_coop
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", at least 2 people, deathmatch is off)
match_format_duel
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", 2 players)
match_format_ffa
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", more than 2 players, teamplay off)
match_format_multiteam
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", 3 or more teams)
match_format_race
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = qw, serverinfo "race" key present and equal to mapname)
match_format_solo
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (any gamedir, 1 player on a server, not in race mode)
match_format_tdm
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 5 people)
match_format_tf_clanwar
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "fortress", at least 2 teams)
match_format_tf_duel
Description:
Each match category has a name format variable associated with it. This variable is called match_format_<category>. For example, there is match_format_duel, match_format_2on2, etc, etc. All these variables can contain macro's that are expanded according to the macro list given below. You can also use the "match_format_macrolist" command inside the client to display a list of the macros and their meaning.
Type:
string
Remarks:
See 'match_format_macrolist' command and Match tools manual for more info.
ValueDescription
This pattern will be used in following situation: (gamedir = "fortress", 2 players)
match_ladder_id
Description:
Identification of the current duel ladder. Not used right now, always 1.
Type:
string
match_name_and
Description:
Used for separating names in %k and %l.
Type:
string
match_name_nick
Description:
%n uses this if its not "", otherwise it uses your in game name.
Type:
string
Remarks:
See match_format_macrolist.
match_name_on
Description:
Used for separating numbers in %a.
Type:
string
match_name_spec
Description:
This is placed after your nick when using %n and are in spec mode. Eg. if you use "match_name_nick foo" and leave match_name_spec default, then %n will be "foo(SPEC)" in spec mode and "foo" when not in spec mode.
Type:
string
Remarks:
See match_format_macrolist.
match_name_versus
Description:
Used for separating names in %b.
Type:
string

MultiView Demos

mvd_autohud
Description:
Will load different Head Up Display settings when watching MultiView Demos.
Type:
enum
ValueDescription
0Won't do anything
1Will load appropriate config according to current match type. Possible types: 1on1, 4on4, custom. Config is like cfg/mvdhud_4on4.cfg
2Will always load cfg/mvdhud_custom.cfg
mvd_autotrack
Description:
Turns auto-tracking function ON / OFF. This feature can be used while watching MultiView Demo. The client will choose and switch to the best player point of view using appropriate algorithm.
Type:
enum
Remarks:
You can change the switching algorithm properties using mvd_autotrack_1on1, mvd_autotrack_2on2, etc. variables. The setting no. 4. cannot be customized and is independent on other autotrack client settings, except of mvd_autotrack_lockteam
ValueDescription
0Off
1Autodetect current gametype and use the appropriate xonx settings
2Force the use of mvd_autotrack_custom* settings
3Enables the use of mvd_multitrack_1 - 4 allowing to set seperate algorthms for every window with cl_muiltiview 2-4
4Simple algorithm which prefers pent+rl over quad+rl, quad+rl over pent, quad over noquad, weapon over no weapon player; cannot be customized
mvd_autotrack_1on1
Description:
Will be used if mvd_autotrack = 1 and a 1on1 game is played. Its an algorythm for selecting the best player.
Type:
string
Remarks:
For a full description read the manual.
mvd_autotrack_1on1_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_autotrack_2on2
Description:
Will be used if mvd_autotrack = 1 and a 2on2 game is played. Its an algorythm for selecting the best player.
Type:
string
Remarks:
For a full description read the manual.
mvd_autotrack_2on2_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_autotrack_4on4
Description:
Will be used if mvd_autotrack = 1 and a 4on4 game is played. Its an algorythm for selecting the best player.
Type:
string
Remarks:
For a full description read the manual.
mvd_autotrack_4on4_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_autotrack_custom
Description:
Will be used if mvd_autotrack = 2.
Its an algorythm for selecting the best player.
Type:
string
Remarks:
For a full description read the manual.
mvd_autotrack_custom_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_autotrack_instant
Description:
Makes mvd_autotrack always find the best player and switch to him instantly.
Type:
boolean
Remarks:
In KTPro autotrack tracked player is changed only when some events happen. In instant mvd_autotrack tracked player is changed everytime a better player is found.
ValueDescription
falsemvd_autotrack will work more like ktpro autotrack
trueplayer change will happen more often
mvd_autotrack_lockteam
Description:
If set to 1, autotrack will keep switching POVs only from players within the same team.
Type:
boolean
ValueDescription
falseAutotrack will switch between all players.
trueAutotrack will stay within one team.
mvd_info
Description:
When watching Multi View Demo (.mvd) you can show a table on the screen with full info about players' status.
Type:
boolean
Remarks:
See mvd_info_setup for setting up displayed informations.
ValueDescription
falseTurned OFF
trueTurned ON
mvd_info_setup
Type:
string
mvd_info_show_header
Description:
Will show a line above the mvd_info table telling you wich column is armor/health/location etc.
Type:
boolean
ValueDescription
falseTurn Off
trueTurned ON
mvd_info_x
Description:
You can adjust horizontal placement of Players' info table
Type:
float
Remarks:
See scr_mvdinfo and scr_mvdinfo_setup description for more details.
mvd_info_y
Description:
You can adjust vertical placement of Players' info table
Type:
float
Remarks:
See scr_mvdinfo and scr_mvdinfo_setup description for more details.
mvd_moreinfo
Description:
When playing MultiView Demo (MVD), you can turn on more messages printed in the console, like those you might know from moreinfo command in ktpro. E.g.: Nabbe picked up quad.
Type:
boolean
ValueDescription
falseOff
trueOn
mvd_multitrack_1
Description:
Will be used if mvd_autotrack = 3 and cl_multiview is enabled.
Its an algorythm for selecting the best player on viewport 1
Type:
string
Remarks:
For a full description read the manual.
mvd_multitrack_1_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_multitrack_2
Description:
Will be used if mvd_autotrack = 3 and cl_multiview is enabled.
Its an algorythm for selecting the best player on viewport 2
Type:
string
Remarks:
For a full description read the manual.
mvd_multitrack_2_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_multitrack_3
Description:
Will be used if mvd_autotrack = 3 and cl_multiview is enabled.
Its an algorythm for selecting the best player on viewport 3
Type:
string
Remarks:
For a full description read the manual.
mvd_multitrack_3_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_multitrack_4
Description:
Will be used if mvd_autotrack = 3 and cl_multiview is enabled.
Its an algorythm for selecting the best player on viewport 4
Type:
string
Remarks:
For a full description read the manual.
mvd_multitrack_4_values
Description:
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
Type:
string
mvd_pc_pent_1
Description:
Describes the position and viewing angles of the p1 cam.
x y z rot_x rot_y
Type:
string
mvd_pc_pent_2
Description:
Describes the position and viewing angles of the p2 cam.
x y z rot_x rot_y
Type:
string
mvd_pc_pent_3
Description:
Describes the position and viewing angles of the p3 cam.
x y z rot_x rot_y
Type:
string
mvd_pc_quad_1
Description:
Describes the position and viewing angles of the q1 cam.
x y z rot_x rot_y
Type:
string
mvd_pc_quad_2
Description:
Describes the position and viewing angles of the q2 cam.
x y z rot_x rot_y
Type:
string
mvd_pc_quad_3
Description:
Describes the position and viewing angles of the q3 cam.
x y z rot_x rot_y
Type:
string
mvd_pc_view_1
Description:
Sets the powerup camera for viewport 1
Type:
enum
ValueDescription
p1mvd_pc_pent_1
p2mvd_pc_pent_2
p3mvd_pc_pent_3
q1mvd_pc_quad_1
q2mvd_pc_quad_2
q3mvd_pc_quad_3
mvd_pc_view_2
Description:
Sets the powerup camera for viewport 2
Type:
enum
ValueDescription
p1mvd_pc_pent_1
p2mvd_pc_pent_2
p3mvd_pc_pent_3
q1mvd_pc_quad_1
q2mvd_pc_quad_2
q3mvd_pc_quad_3
mvd_pc_view_3
Description:
Sets the powerup camera for viewport 3
Type:
enum
ValueDescription
p1mvd_pc_pent_1
p2mvd_pc_pent_2
p3mvd_pc_pent_3
q1mvd_pc_quad_1
q2mvd_pc_quad_2
q3mvd_pc_quad_3
mvd_pc_view_4
Description:
Sets the powerup camera for viewport 4
Type:
enum
ValueDescription
p1mvd_pc_pent_1
p2mvd_pc_pent_2
p3mvd_pc_pent_3
q1mvd_pc_quad_1
q2mvd_pc_quad_2
q3mvd_pc_quad_3
mvd_powerup_cam
Description:
Will enable powerupcams, cams will be enabled on every viewport 5 seconds before the powerup spawns.
Type:
boolean
Remarks:
For setting up the viewports cams look at
mvd_pc_view_1-4
and for setting the locations of the cams look at
mvd_pc_quad_1-3
mvd_pc_pent_1-3
ValueDescription
falseTurn OFF
trueTurned ON
mvd_status
Description:
Shows information of the player you are currently tracking.
Information includes.
taken/dropped items and powerups
last 3 runs (including the current one) run is from powerup-took/spawn to powerup-end/death
Type:
boolean
ValueDescription
falseTurned OFF
trueTurned ON
mvd_status_x
Description:
Adjusts the horizontal placement of mvd_status table
Type:
float
mvd_status_y
Description:
Adjusts the vertical placement of mvd_status table
Type:
float