ezQuake

Appearance

Return to top
On this page

Demo Settings

Demo Handling

cl_demo_qwd_delta boolean default: 1
Whether or not to write delta packets for entities into .qwd files. Older clients may not be able to play these back.
cl_demoPingInterval integer default: 5
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).
  • 0: Disable automatic ping requests.
  • 5: Request every 5 seconds (default).
cl_demospeed float default: 1
Controls the speed of demo playback in percentage (can be changed during demo playback if you wish).
cl_demoteamplay boolean default: 0
If set, teamplay settings enabled during .dem playback.
cl_startupdemo string
Demo that should be played on client's startup.
  • *: File name of the demo.
demo_autotrack boolean default: 0
Enables server-side autotrack to be accepted.
  • false:
  • true:
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.
demo_benchmarkdumps boolean default: 1
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.
  • false: Disable timedemo result dumping
  • true: Dump results of timedemo benchmark
See timedemo command description for more info. Note: The result file is not a well-formed XML file.
demo_capture_background_threads integer default: 0
Determines how many background threads should be used writing images to disk.
demo_capture_codec float default: 0
Determines what codes should be used for captured video stream compression. E.g: xvid, divx, x264, ...
demo_capture_dir string default: capture
Change the default capture directory.
demo_capture_fps float default: 30.0
Change the default capture fps.
demo_capture_mp3 boolean default: 0
When set to 1 .avi capturing captures sound compressed in MP3 format.
  • false: Captures uncompressed sound
  • true: Captures sound in MP3 format
See demo_capture_mp3_kbps too.
demo_capture_mp3_kbps float default: 128
Sets bitrate for captured sound stream when demo_capture_mp3 is set to 1.
demo_capture_quiet boolean
Stops sound being played during demo capture.
demo_capture_steadycam float default: 0
Changes behaviour of keyboard/mouse input when capturing.
demo_capture_vid_maxlen integer default: 0
If set, multiple files will be created. This variable determines length of each file in MB.
The .avi format has issues with files over 2GB in size.
demo_dir string
Change the demos and autorecord directory.
demo_format enum default: qwz
Specifies the demo file format used when recording demo with Match tools.
  • mvd: MultiView Demo, usually contains less frames per second.
  • qwd: Original QuakeWorld demo format.
  • qwz: Qizmo compressed demo.
See qwdtools_dir, qizmo_dir, match_auto_record.
demo_getpings boolean default: 1
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).
  • false: only update pings in the demo when the player died and show(team)scores are being shown
  • true: always update pings
qizmo_dir string default: qizmo
Change the default qizmo directory.
qwdtools_dir string default: qwdtools
Specifies the qwdtools utility placement.
  • *: Use path relative to your quakedir

Match Tools

match_auto_logconsole enum default: 1
When set to 1 or 2, a temp console log will automatically be created when a match starts (usually when the countdown starts).
  • 0: Do not auto-log console.
  • 1: Auto record console but requires manuall saving. See 'match_save'.
  • 2: Automatically saves the console log after the match is completed.
match_auto_logupload boolean default: 0
Automatically upload match console log to remote server specified in match_auto_logurl.
  • false:
  • true:
match_auto_logupload_token string
match_auto_logurl string default: http://stats.quakeworld.nu/logupload
match_auto_minlength integer default: 30
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.
  • *: number of seconds
If a temp demo is too short to autosave, you can still save it manually with "match_save".
match_auto_record enum default: 0
When set to 1 or 2, a temp demo will automatically be recorded when a match starts (usually when the countdown starts).
  • 0: No auto recording.
  • 1: Demo will be recorded but requires manual saving with match_save
  • 2: Automatically saves the demo after the match is completed.
match_auto_spectating boolean default: 0
When set to 1, auto recording will also occur when in spectator mode.
  • false: Don't auto record demos in spectator mode.
  • true: Auto record demos even in spectator mode.
match_auto_sshot boolean default: 0
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.
  • false: Do not take auto screenshot.
  • true: Take auto screenshot on match end.
match_auto_unminimize boolean default: 1
Bring client from minimized state on countdown start.
  • false:
  • true:
Only works on KT* servers.
match_challenge boolean default: 0
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.
  • false:
  • true:
match_challenge_url string default: http://stats.quakeworld.nu/post-challenge
Web address where POST requests announcing challenge match start and end will be sent.
match_format_2on2 string default: 2on2/%n - [%k%v%l] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 2 people)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_3on3 string default: tdm/%n - [%Oon%E_%t%v%e] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 3 people)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_4on4 string default: tdm/%n - [%Oon%E_%t%v%e] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 4 people)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_arena string default: arena/%n - %p%v%e - [%F_frags] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "arena")
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_coop string default: coop/%n - [%C_player_coop] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", at least 2 people, deathmatch is off)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_duel string default: duel/%n - %p%v%e - [dmm%D] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", 2 players)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_ffa string default: ffa/%n - [%C_player_ffa] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", more than 2 players, teamplay off)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_multiteam string default: tdm/%n - [%a_%b] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", 3 or more teams)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_race string default: race/%n - [race] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = qw, serverinfo "race" key present and equal to mapname)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_solo string default: solo/%n - [%M]
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.
  • *: This pattern will be used in following situation: (any gamedir, 1 player on a server, not in race mode)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_tdm string default: tdm/%n - [%Oon%E_%t%v%e] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 5 people)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_tf_clanwar string default: tfwar/%n - [%Oon%E_%t%v%e] - [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "fortress", at least 2 teams)
See 'match_format_macrolist' command and Match tools manual for more info.
match_format_tf_duel string default: tfduel/%n - %p%v%e [%M]
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.
  • *: This pattern will be used in following situation: (gamedir = "fortress", 2 players)
See 'match_format_macrolist' command and Match tools manual for more info.
match_ladder_id string default: 1
Identification of the current duel ladder. Not used right now, always 1.
match_name_and string default: _&_
Used for separating names in %k and %l.
match_name_nick string
%n uses this if its not "", otherwise it uses your in game name.
See match_format_macrolist.
match_name_on string default: on
Used for separating numbers in %a.
match_name_spec string default: (SPEC)
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.
See match_format_macrolist.
match_name_versus string default: _vs_
Used for separating names in %b.

MultiView Demos

mvd_autohud enum default: 0
Will load different Head Up Display settings when watching MultiView Demos.
  • 0: Won't do anything
  • 1: Will load appropriate config according to current match type. Possible types: 1on1, 4on4, custom. Config is like cfg/mvdhud_4on4.cfg
  • 2: Will always load cfg/mvdhud_custom.cfg
mvd_autotrack enum default: 0
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.
  • 0: Off
  • 1: Autodetect current gametype and use the appropriate xonx settings
  • 2: Force the use of mvd_autotrack_custom* settings
  • 3: Enables the use of mvd_multitrack_1 - 4 allowing to set seperate algorthms for every window with cl_muiltiview 2-4
  • 4: Simple algorithm which prefers pent+rl over quad+rl, quad+rl over pent, quad over noquad, weapon over no weapon player Cannot be customized
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.
mvd_autotrack_1on1 string default: %a * %A + 50 * %W + %p + %f
Will be used if mvd_autotrack = 1 and a 1on1 game is played. Its an algorythm for selecting the best player.
For a full description read the manual.
mvd_autotrack_1on1_values string default: 1 2 3 2 3 5 8 8 1 2 3 0 0 0
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_autotrack_2on2 string default: %a * %A + 50 * %W + %p + %f
Will be used if mvd_autotrack = 1 and a 2on2 game is played. Its an algorythm for selecting the best player.
For a full description read the manual.
mvd_autotrack_2on2_values string default: 1 2 3 2 3 5 8 8 1 2 3 500 900 1000
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_autotrack_4on4 string default: %a * %A + 50 * %W + %p + %f
Will be used if mvd_autotrack = 1 and a 4on4 game is played. Its an algorythm for selecting the best player.
For a full description read the manual.
mvd_autotrack_4on4_values string default: 1 2 4 2 4 6 10 10 1 2 3 500 900 1000
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_autotrack_custom string default: %a * %A + 50 * %W + %p + %f
Will be used if mvd_autotrack = 2. Its an algorythm for selecting the best player.
For a full description read the manual.
mvd_autotrack_custom_values string default: 1 2 3 2 3 4 6 6 1 2 3 500 900 1000
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_autotrack_instant boolean default: 0
Makes mvd_autotrack always find the best player and switch to him instantly.
  • false: mvd_autotrack will work more like ktpro autotrack
  • true: player change will happen more often
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.
mvd_autotrack_lockteam boolean default: 0
If set to 1, autotrack will keep switching POVs only from players within the same team.
  • false: Autotrack will switch between all players.
  • true: Autotrack will stay within one team.
mvd_info boolean default: 0
When watching Multi View Demo (.mvd) you can show a table on the screen with full info about players' status.
  • false: Turned OFF
  • true: Turned ON
See mvd_info_setup for setting up displayed informations.
mvd_info_setup string default: %p%n %l %h/%a %w
mvd_info_show_header boolean default: 0
Will show a line above the mvd_info table telling you wich column is armor/health/location etc.
  • false: Turn Off
  • true: Turned ON
mvd_info_x float default: 0
You can adjust horizontal placement of Players' info table.
See scr_mvdinfo and scr_mvdinfo_setup description for more details.
mvd_info_y float default: 0
You can adjust vertical placement of Players' info table.
See scr_mvdinfo and scr_mvdinfo_setup description for more details.
mvd_moreinfo boolean default: 0
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.
  • false: Off
  • true: On
mvd_multitrack_1 string default: %f
Will be used if mvd_autotrack = 3 and cl_multiview is enabled. Its an algorythm for selecting the best player on viewport 1.
For a full description read the manual.
mvd_multitrack_1_values string default: 1 2 3 2 3 5 8 8 1 2 3 0 0 0
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_multitrack_2 string default: %W
Will be used if mvd_autotrack = 3 and cl_multiview is enabled. Its an algorythm for selecting the best player on viewport 2.
For a full description read the manual.
mvd_multitrack_2_values string default: 1 2 3 2 3 5 8 8 1 2 3 0 0 0
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_multitrack_3 string default: %h
Will be used if mvd_autotrack = 3 and cl_multiview is enabled. Its an algorythm for selecting the best player on viewport 3.
For a full description read the manual.
mvd_multitrack_3_values string default: 1 2 3 2 3 5 8 8 1 2 3 0 0 0
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_multitrack_4 string default: %A
Will be used if mvd_autotrack = 3 and cl_multiview is enabled. Its an algorythm for selecting the best player on viewport 4.
For a full description read the manual.
mvd_multitrack_4_values string default: 1 2 3 2 3 5 8 8 1 2 3 0 0 0
Allows you to customize autotrack algoritm. See autotrack manual page for more info.
mvd_pc_pent_1 string
Describes the position and viewing angles of the p1 cam. x y z rot_x rot_y
mvd_pc_pent_2 string
Describes the position and viewing angles of the p2 cam. x y z rot_x rot_y
mvd_pc_pent_3 string
Describes the position and viewing angles of the p3 cam. x y z rot_x rot_y
mvd_pc_quad_1 string
Describes the position and viewing angles of the q1 cam. x y z rot_x rot_y
mvd_pc_quad_2 string
Describes the position and viewing angles of the q2 cam. x y z rot_x rot_y
mvd_pc_quad_3 string
Describes the position and viewing angles of the q3 cam. x y z rot_x rot_y
mvd_pc_view_1 enum
Sets the powerup camera for viewport 1.
  • : (disabled)
  • p1: mvd_pc_pent_1
  • p2: mvd_pc_pent_2
  • p3: mvd_pc_pent_3
  • q1: mvd_pc_quad_1
  • q2: mvd_pc_quad_2
  • q3: mvd_pc_quad_3
mvd_pc_view_2 enum
Sets the powerup camera for viewport 2.
  • : (disabled)
  • p1: mvd_pc_pent_1
  • p2: mvd_pc_pent_2
  • p3: mvd_pc_pent_3
  • q1: mvd_pc_quad_1
  • q2: mvd_pc_quad_2
  • q3: mvd_pc_quad_3
mvd_pc_view_3 enum
Sets the powerup camera for viewport 3.
  • : (disabled)
  • p1: mvd_pc_pent_1
  • p2: mvd_pc_pent_2
  • p3: mvd_pc_pent_3
  • q1: mvd_pc_quad_1
  • q2: mvd_pc_quad_2
  • q3: mvd_pc_quad_3
mvd_pc_view_4 enum
Sets the powerup camera for viewport 4.
  • : (disabled)
  • p1: mvd_pc_pent_1
  • p2: mvd_pc_pent_2
  • p3: mvd_pc_pent_3
  • q1: mvd_pc_quad_1
  • q2: mvd_pc_quad_2
  • q3: mvd_pc_quad_3
mvd_powerup_cam boolean default: 0
Will enable powerupcams, cams will be enabled on every viewport 5 seconds before the powerup spawns.
  • false: Turn OFF
  • true: Turned ON
For setting up the viewports cams look at mvd_pc_view_1-4. For setting the locations of the cams look at mvd_pc_quad_1-3 and mvd_pc_pent_1-3.
mvd_status boolean default: 0
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.
  • false: Turned OFF
  • true: Turned ON
mvd_status_x float default: 0
Adjusts the horizontal placement of mvd_status table.
mvd_status_y float default: 0
Adjusts the vertical placement of mvd_status table.