ezQuake Manual: Demos

Demo Handling

cl_demoPingInterval [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 5

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).

Value

value description
0 Disable automatic ping requests.

Remarks

cl_demospeed [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 1

Description

Controls the speed of demo playback in percentage (can be changed during demo playback if you wish).

Remarks

demo_capture_codec [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

Description

Determines what codes should be used for captured video stream compression. E.g. XVID, DIVX, ...

demo_capture_dir [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: capture

Description

Change the default capture directory.

demo_capture_fps [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 30.0

Description

Change the default capture fps.

demo_capture_mp3 [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

Description

When set to 1 .avi capturing captures sound compressed in MP3 format.

Value

value description
0 Captures uncompressed sound
1 Captures sound in MP3 format

Remarks

See demo_capture_mp3_kbps too.

demo_capture_mp3_kbps [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 128

Description

Sets bitrate for captured sound stream when demo_capture_mp3 is set to 1.

demo_capture_steadycam [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

Description

Changes behaviour of keyboard/mouse input when capturing.

demo_dir [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default:

Description

Change the demos and autorecord directory.

demo_getpings [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 1

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).

Value

value description
0 only update pings in the demo when the player died and show(team)scores are being shown
1 always update pings

Remarks

qizmo_dir [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: qizmo

Description

Change the default qizmo directory.

Match Tools

match_auto_logconsole [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

Description

When set to 1 or 2, a temp console log will automatically be created when a match starts (usually when the countdown starts).

Value

value description
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_minlength [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 30

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.

Value

Integer. number of seconds

Remarks

If a temp demo is too short to autosave, you can still save it manually with "match_save".

match_auto_record [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

Description

When set to 1 or 2, a temp demo will automatically be recorded when a match starts (usually when the countdown starts).

Value

value description
0 No auto recording.
1 Demo will be recorded but requires manuall saving.
2 Automatically saves the demo after the match is completed.

Remarks

See 'match_save' for manuall demo saving.

match_auto_spectating [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

Description

When set to 1, auto recording will also occur when in spectator mode.

Value

value description
0 = False Don't auto record demos in spectator mode.
1 = True Auto record demos even in spectator mode.

match_auto_sshot [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 0

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.

Value

value description
0 = False Do not take auto screenshot.
1 = True Take auto screenshot on match end.

match_format_2on2 [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: 2on2/%n - [%k%v%l] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 2 people)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_3on3 [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: tdm/%n - [%Oon%E_%t%v%e] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 3 people)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_4on4 [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: tdm/%n - [%Oon%E_%t%v%e] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 4 people)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_arena [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: arena/%n - %p%v%e - [%F_frags] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "arena")

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_coop [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: coop/%n - [%C_player_coop] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", at least 2 people, deathmatch is off)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_duel [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: duel/%n - %p%v%e - [dmm%D] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", 2 players)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_ffa [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: ffa/%n - [%C_player_ffa] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", more than 2 players, teamplay off)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_multiteam [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: tdm/%n - [%a_%b] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", 3 or more teams)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_race [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: race/%n - [race] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = qw, serverinfo "race" key present and equal to mapname)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_solo [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: solo/%n - [%M]

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.

Value

String. This pattern will be used in following situation: (any gamedir, 1 player on a server, not in race mode)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_tdm [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: tdm/%n - [%Oon%E_%t%v%e] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "qw", 2 teams with at least 1 team having 5 people)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_tf_clanwar [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: tfwar/%n - [%Oon%E_%t%v%e] - [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "fortress", at least 2 teams)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_format_tf_duel [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: tfduel/%n - %p%v%e [%M]

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.

Value

String. This pattern will be used in following situation: (gamedir = "fortress", 2 players)

Remarks

See 'match_format_macrolist' command and Match tools manual for more info.

match_name_and [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: _&_

Description

Used for separating names in %k and %l.

Value

String.

match_name_nick [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default:

Description

%n uses this if its not "", otherwise it uses your in game name.

Value

String.

Remarks

See match_format_macrolist.

match_name_on [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: on

Description

Used for separating numbers in %a.

Value

String.

match_name_spec [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: (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.

Value

String.

Remarks

See match_format_macrolist.

match_name_versus [#]

Support: Windows: Software Windows: OpenGL Linux: X11 Linux: GLX Linux: SVGA

Default: _vs_

Description

Used for separating names in %b.

Value

String.

Last update: 22.07.2005 17:55 CET (GMT+01:00)