2002-10-03 21:00:35 +00:00
|
|
|
/*
|
|
|
|
Copyright (C) 1996-1997 Id Software, Inc.
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or
|
|
|
|
modify it under the terms of the GNU General Public License
|
|
|
|
as published by the Free Software Foundation; either version 2
|
|
|
|
of the License, or (at your option) any later version.
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
2012-05-21 23:23:22 +00:00
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
See the included (GNU.txt) GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with this program; if not, write to the Free Software
|
|
|
|
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
|
|
|
|
|
*/
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
# include "config.h"
|
|
|
|
#endif
|
2003-01-15 15:31:36 +00:00
|
|
|
|
2002-10-03 21:00:35 +00:00
|
|
|
#ifdef HAVE_STRING_H
|
|
|
|
# include "string.h"
|
|
|
|
#endif
|
|
|
|
#ifdef HAVE_STRINGS_H
|
|
|
|
# include "strings.h"
|
|
|
|
#endif
|
|
|
|
#ifdef HAVE_UNISTD_H
|
|
|
|
# include "unistd.h"
|
|
|
|
#endif
|
2007-03-22 23:20:57 +00:00
|
|
|
#ifdef HAVE_SYS_TIME_H
|
2002-10-03 21:00:35 +00:00
|
|
|
#include <sys/time.h>
|
2007-03-22 23:20:57 +00:00
|
|
|
#endif
|
2002-10-03 21:00:35 +00:00
|
|
|
#include <time.h>
|
|
|
|
|
|
|
|
#include "QF/cmd.h"
|
|
|
|
#include "QF/cvar.h"
|
|
|
|
#include "QF/dstring.h"
|
|
|
|
#include "QF/info.h"
|
|
|
|
#include "QF/msg.h"
|
|
|
|
#include "QF/qargs.h"
|
|
|
|
#include "QF/qendian.h"
|
|
|
|
#include "QF/quakefs.h"
|
|
|
|
#include "QF/sys.h"
|
|
|
|
#include "QF/va.h"
|
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
#include "compat.h"
|
2020-06-21 14:15:17 +00:00
|
|
|
|
2005-05-02 04:09:15 +00:00
|
|
|
#include "qw/pmove.h"
|
2020-06-21 14:15:17 +00:00
|
|
|
#include "qw/include/server.h"
|
|
|
|
#include "qw/include/sv_demo.h"
|
|
|
|
#include "qw/include/sv_progs.h"
|
|
|
|
#include "qw/include/sv_recorder.h"
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
static QFile *demo_file;
|
|
|
|
static byte *demo_mfile;
|
|
|
|
static qboolean demo_disk;
|
|
|
|
static dstring_t *demo_name; // filename of mvd
|
|
|
|
static dstring_t *demo_text; // filename of description file
|
|
|
|
static void *demo_dest;
|
2005-05-01 09:07:20 +00:00
|
|
|
static double demo_time;
|
|
|
|
|
|
|
|
static recorder_t *recorder;
|
2005-05-05 11:46:29 +00:00
|
|
|
static int delta_sequence;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
#define MIN_DEMO_MEMORY 0x100000
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
#define USECACHE (sv_demoUseCache && svs.demomemsize)
|
2003-03-21 21:25:44 +00:00
|
|
|
#define DWRITE(a,b,d) dwrite((QFile *) d, a, b)
|
2002-10-04 02:29:03 +00:00
|
|
|
|
|
|
|
static int demo_max_size;
|
|
|
|
static int demo_size;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
float sv_demofps;
|
|
|
|
static cvar_t sv_demofps_cvar = {
|
|
|
|
.name = "sv_demofps",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Minimum frame rate of packets written to the demo",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "20",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = &cexpr_float, .value = &sv_demofps },
|
|
|
|
};
|
|
|
|
float sv_demoPings;
|
|
|
|
static cvar_t sv_demoPings_cvar = {
|
|
|
|
.name = "sv_demoPings",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Time in seconds between player ping updates. 0 disables.",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "3",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = &cexpr_float, .value = &sv_demoPings },
|
|
|
|
};
|
2022-04-24 11:04:06 +00:00
|
|
|
int sv_demoMaxSize;
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
static cvar_t sv_demoMaxSize_cvar = {
|
|
|
|
.name = "sv_demoMaxSize",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "20480",
|
|
|
|
.flags = CVAR_NONE,
|
2022-04-24 11:04:06 +00:00
|
|
|
.value = { .type = &cexpr_int, .value = &sv_demoMaxSize },
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
};
|
|
|
|
static int sv_demoUseCache;
|
|
|
|
static cvar_t sv_demoUseCache_cvar = {
|
|
|
|
.name = "sv_demoUseCache",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "0",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = &cexpr_int, .value = &sv_demoUseCache },
|
|
|
|
};
|
2022-04-24 11:04:06 +00:00
|
|
|
int sv_demoCacheSize;
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
static cvar_t sv_demoCacheSize_cvar = {
|
|
|
|
.name = "sv_demoCacheSize",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = 0,
|
|
|
|
.flags = CVAR_ROM,
|
2022-04-24 11:04:06 +00:00
|
|
|
.value = { .type = &cexpr_int, .value = &sv_demoCacheSize },
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
};
|
2022-04-24 11:04:06 +00:00
|
|
|
int sv_demoMaxDirSize;
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
static cvar_t sv_demoMaxDirSize_cvar = {
|
|
|
|
.name = "sv_demoMaxDirSize",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "102400",
|
|
|
|
.flags = CVAR_NONE,
|
2022-04-24 11:04:06 +00:00
|
|
|
.value = { .type = &cexpr_int, .value = &sv_demoMaxDirSize },
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
};
|
|
|
|
static char *sv_demoDir;
|
|
|
|
static cvar_t sv_demoDir_cvar = {
|
|
|
|
.name = "sv_demoDir",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Name of subdirectory in which demos will be saved",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "demos",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = 0, .value = &sv_demoDir },
|
|
|
|
};
|
2022-04-24 11:04:06 +00:00
|
|
|
int sv_demoNoVis;
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
static cvar_t sv_demoNoVis_cvar = {
|
|
|
|
.name = "sv_demoNoVis",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "1",
|
|
|
|
.flags = CVAR_NONE,
|
2022-04-24 11:04:06 +00:00
|
|
|
.value = { .type = &cexpr_int, .value = &sv_demoNoVis },
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
};
|
|
|
|
static char *sv_demoPrefix;
|
|
|
|
static cvar_t sv_demoPrefix_cvar = {
|
|
|
|
.name = "sv_demoPrefix",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Prefix for demo file names",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = 0, .value = &sv_demoPrefix },
|
|
|
|
};
|
|
|
|
static char *sv_demoSuffix;
|
|
|
|
static cvar_t sv_demoSuffix_cvar = {
|
|
|
|
.name = "sv_demoSuffix",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Suffix for demo file names",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = 0, .value = &sv_demoSuffix },
|
|
|
|
};
|
|
|
|
static char *sv_onrecordfinish;
|
|
|
|
static cvar_t sv_onrecordfinish_cvar = {
|
|
|
|
.name = "sv_onrecordfinish",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Command to execute when recording has finished. FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = 0, .value = &sv_onrecordfinish },
|
|
|
|
};
|
|
|
|
static char *sv_ondemoremove;
|
|
|
|
static cvar_t sv_ondemoremove_cvar = {
|
|
|
|
.name = "sv_ondemoremove",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Command to execute when a demo is removed. FIXME not used",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "",
|
|
|
|
.flags = CVAR_NONE,
|
2022-04-24 11:04:06 +00:00
|
|
|
.value = { .type = 0, .value = &sv_ondemoremove },
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
};
|
|
|
|
static int sv_demotxt;
|
|
|
|
static cvar_t sv_demotxt_cvar = {
|
|
|
|
.name = "sv_demotxt",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Write brief description of demo to text file",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "1",
|
|
|
|
.flags = CVAR_NONE,
|
|
|
|
.value = { .type = &cexpr_int, .value = &sv_demotxt },
|
|
|
|
};
|
|
|
|
static char *serverdemo;
|
|
|
|
static cvar_t serverdemo_cvar = {
|
|
|
|
.name = "serverdemo",
|
|
|
|
.description =
|
2022-10-15 05:47:53 +00:00
|
|
|
"Cvar for passing server demo file name to progs",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
.default_value = "",
|
|
|
|
.flags = CVAR_SERVERINFO,
|
|
|
|
.value = { .type = 0, .value = &serverdemo },
|
|
|
|
};
|
2005-05-01 09:07:20 +00:00
|
|
|
|
|
|
|
static int (*dwrite) (QFile * file, const void *buf, int count);
|
2004-03-06 04:42:43 +00:00
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
#define HEADER ((int) &((header_t *) 0)->data)
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static int
|
2003-08-05 01:45:52 +00:00
|
|
|
memwrite (QFile *_mem, const void *buffer, int size)
|
2002-10-03 21:00:35 +00:00
|
|
|
{
|
|
|
|
byte **mem = (byte **) _mem;
|
|
|
|
|
2003-08-05 01:45:52 +00:00
|
|
|
memcpy (*mem, buffer, size);
|
|
|
|
*mem += size;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
return size;
|
|
|
|
}
|
|
|
|
|
2004-03-06 04:42:43 +00:00
|
|
|
static void
|
2005-05-05 07:31:31 +00:00
|
|
|
demo_write (void *unused, sizebuf_t *msg, int unused2)
|
2002-10-03 21:00:35 +00:00
|
|
|
{
|
2005-05-01 09:07:20 +00:00
|
|
|
DWRITE (msg->data, msg->cursize, demo_dest);
|
2004-03-06 04:42:43 +00:00
|
|
|
}
|
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
static int
|
2005-05-05 07:31:31 +00:00
|
|
|
demo_frame (void *unused)
|
2004-03-06 04:42:43 +00:00
|
|
|
{
|
2005-05-01 09:07:20 +00:00
|
|
|
double min_fps;
|
2004-03-06 04:42:43 +00:00
|
|
|
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
if (!sv_demofps)
|
2005-05-01 09:07:20 +00:00
|
|
|
min_fps = 20.0;
|
|
|
|
else
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
min_fps = sv_demofps;
|
2005-05-01 09:07:20 +00:00
|
|
|
min_fps = max (4, min_fps);
|
|
|
|
if (sv.time - demo_time < 1.0 / min_fps)
|
|
|
|
return 0;
|
|
|
|
demo_time = sv.time;
|
|
|
|
return 1;
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
|
2005-05-05 11:46:29 +00:00
|
|
|
static void
|
|
|
|
demo_end_frame (recorder_t *r, void *unused)
|
|
|
|
{
|
|
|
|
SVR_SetDelta (r, ++delta_sequence, -1);
|
|
|
|
}
|
|
|
|
|
2005-05-01 22:13:10 +00:00
|
|
|
static void
|
2005-05-05 07:31:31 +00:00
|
|
|
demo_finish (void *unused, sizebuf_t *msg)
|
2005-05-01 22:13:10 +00:00
|
|
|
{
|
|
|
|
// write a disconnect message to the demo file
|
|
|
|
MSG_WriteByte (msg, svc_disconnect);
|
|
|
|
MSG_WriteString (msg, "EndOfDemo");
|
|
|
|
recorder = 0;
|
2010-01-13 06:44:29 +00:00
|
|
|
sv.recording_demo = 0;
|
2005-05-01 22:13:10 +00:00
|
|
|
}
|
|
|
|
|
2002-10-03 21:00:35 +00:00
|
|
|
/*
|
|
|
|
SV_Stop
|
|
|
|
|
|
|
|
stop recording a demo
|
|
|
|
*/
|
|
|
|
void
|
|
|
|
SV_Stop (int reason)
|
|
|
|
{
|
2005-05-01 09:07:20 +00:00
|
|
|
if (!recorder) {
|
2007-11-06 10:17:14 +00:00
|
|
|
Sys_Printf ("Not recording a demo.\n");
|
2002-10-03 21:00:35 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
SVR_RemoveUser (recorder);
|
2005-05-01 22:13:10 +00:00
|
|
|
|
2012-07-13 05:41:10 +00:00
|
|
|
//if (demo_disk)
|
2005-05-01 22:13:10 +00:00
|
|
|
Qclose (demo_file);
|
|
|
|
demo_file = NULL;
|
2005-05-01 09:07:20 +00:00
|
|
|
recorder = 0;
|
2010-01-13 06:44:29 +00:00
|
|
|
sv.recording_demo = 0;
|
2012-07-13 05:41:10 +00:00
|
|
|
switch (reason) {
|
|
|
|
case 0:
|
|
|
|
SV_BroadcastPrintf (PRINT_CHAT, "Server recording completed\n");
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
SV_BroadcastPrintf (PRINT_CHAT,
|
|
|
|
"Server recording canceled, demo removed\n");
|
|
|
|
Sys_Printf ("%s %s\n", demo_name->str, demo_text->str);
|
|
|
|
QFS_Remove (demo_name->str);
|
|
|
|
QFS_Remove (demo_text->str);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
SV_BroadcastPrintf (PRINT_CHAT, "Server recording stoped\n"
|
|
|
|
"Max demo size exceeded\n");
|
|
|
|
break;
|
|
|
|
}
|
2002-10-03 21:00:35 +00:00
|
|
|
/*
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
if (sv_onrecordfinish[0]) {
|
2002-10-03 21:00:35 +00:00
|
|
|
extern redirect_t sv_redirected;
|
|
|
|
int old = sv_redirected;
|
|
|
|
char path[MAX_OSPATH];
|
|
|
|
char *p;
|
|
|
|
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
if ((p = strstr (sv_onrecordfinish, " ")) != NULL)
|
2002-10-03 21:00:35 +00:00
|
|
|
*p = 0; // strip parameters
|
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
strcpy (path, demo_name->str);
|
|
|
|
strcpy (path + strlen (demo_name->str) - 3, "txt");
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
sv_redirected = RD_NONE; // onrecord script is called always
|
|
|
|
// from the console
|
2021-01-31 07:01:20 +00:00
|
|
|
Cmd_TokenizeString (va (0, "script %s \"%s\" \"%s\" \"%s\" %s",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
sv_onrecordfinish, demo.path->str,
|
|
|
|
serverdemo,
|
2002-10-03 21:00:35 +00:00
|
|
|
path, p != NULL ? p + 1 : ""));
|
|
|
|
if (p)
|
|
|
|
*p = ' ';
|
|
|
|
SV_Script_f ();
|
|
|
|
|
|
|
|
sv_redirected = old;
|
|
|
|
}
|
|
|
|
*/
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
Cvar_Set ("serverdemo", "");
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
|
2004-03-06 03:18:14 +00:00
|
|
|
static void
|
2002-10-03 21:00:35 +00:00
|
|
|
SV_Stop_f (void)
|
|
|
|
{
|
|
|
|
SV_Stop (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
SV_Cancel_f
|
|
|
|
|
|
|
|
Stops recording, and removes the demo
|
|
|
|
*/
|
2003-01-06 18:28:13 +00:00
|
|
|
static void
|
2002-10-03 21:00:35 +00:00
|
|
|
SV_Cancel_f (void)
|
|
|
|
{
|
|
|
|
SV_Stop (2);
|
|
|
|
}
|
|
|
|
|
2004-03-06 04:42:43 +00:00
|
|
|
static qboolean
|
|
|
|
SV_InitRecord (void)
|
|
|
|
{
|
2005-04-30 23:25:50 +00:00
|
|
|
if (!USECACHE) {
|
2004-03-06 04:42:43 +00:00
|
|
|
dwrite = &Qwrite;
|
2005-05-01 04:27:05 +00:00
|
|
|
demo_dest = demo_file;
|
|
|
|
demo_disk = true;
|
2004-03-06 04:42:43 +00:00
|
|
|
} else {
|
|
|
|
dwrite = &memwrite;
|
2005-05-01 04:27:05 +00:00
|
|
|
demo_mfile = svs.demomem;
|
|
|
|
demo_dest = &demo_mfile;
|
2004-03-06 04:42:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
demo_size = 0;
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
SV_WriteRecordDemoMessage
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
Dumps the current net message, prefixed by the length and view angles
|
|
|
|
*/
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static void
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (sizebuf_t *msg)
|
2002-10-03 21:00:35 +00:00
|
|
|
{
|
|
|
|
int len;
|
|
|
|
byte c;
|
|
|
|
|
|
|
|
c = 0;
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&c, sizeof (c), demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
c = dem_read;
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&c, sizeof (c), demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
len = LittleLong (msg->cursize);
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&len, 4, demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (msg->data, msg->cursize, demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
if (demo_disk)
|
|
|
|
Qflush (demo_file);
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static void
|
2002-10-03 21:00:35 +00:00
|
|
|
SV_WriteSetDemoMessage (void)
|
|
|
|
{
|
|
|
|
int len;
|
|
|
|
byte c;
|
|
|
|
|
|
|
|
c = 0;
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&c, sizeof (c), demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
c = dem_set;
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&c, sizeof (c), demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
|
|
|
|
len = LittleLong (0);
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&len, 4, demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
len = LittleLong (0);
|
2005-05-01 09:07:20 +00:00
|
|
|
/*demo.size +=*/ DWRITE (&len, 4, demo_dest);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
if (demo_disk)
|
|
|
|
Qflush (demo_file);
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static const char *
|
2002-10-03 21:00:35 +00:00
|
|
|
SV_PrintTeams (void)
|
|
|
|
{
|
2003-08-05 01:45:52 +00:00
|
|
|
const char *teams[MAX_CLIENTS];
|
2002-10-03 21:00:35 +00:00
|
|
|
char *p;
|
|
|
|
int i, j, numcl = 0, numt = 0;
|
|
|
|
client_t *clients[MAX_CLIENTS];
|
2002-10-04 03:36:51 +00:00
|
|
|
const char *team;
|
2003-08-05 01:45:52 +00:00
|
|
|
static dstring_t *buffer;
|
|
|
|
|
|
|
|
if (!buffer)
|
|
|
|
buffer = dstring_new ();
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
// count teams and players
|
|
|
|
for (i = 0; i < MAX_CLIENTS; i++) {
|
2004-04-06 22:02:45 +00:00
|
|
|
if (svs.clients[i].state != cs_spawned
|
|
|
|
&& svs.clients[i].state != cs_server)
|
2002-10-03 21:00:35 +00:00
|
|
|
continue;
|
|
|
|
if (svs.clients[i].spectator)
|
|
|
|
continue;
|
|
|
|
|
2002-10-04 03:36:51 +00:00
|
|
|
team = Info_ValueForKey (svs.clients[i].userinfo, "team");
|
2002-10-03 21:00:35 +00:00
|
|
|
clients[numcl++] = &svs.clients[i];
|
2003-08-05 01:45:52 +00:00
|
|
|
|
2002-10-03 21:00:35 +00:00
|
|
|
for (j = 0; j < numt; j++)
|
2002-10-04 03:36:51 +00:00
|
|
|
if (!strcmp (team, teams[j]))
|
2002-10-03 21:00:35 +00:00
|
|
|
break;
|
|
|
|
if (j != numt)
|
|
|
|
continue;
|
|
|
|
|
2003-08-05 01:45:52 +00:00
|
|
|
teams[numt++] = team;
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// create output
|
|
|
|
|
2004-02-24 20:58:30 +00:00
|
|
|
if (numcl == 2) { // duel
|
2003-08-05 01:45:52 +00:00
|
|
|
dsprintf (buffer, "team1 %s\nteam2 %s\n", clients[0]->name,
|
|
|
|
clients[1]->name);
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
} else if (!teamplay) { // ffa
|
2003-08-05 01:45:52 +00:00
|
|
|
dsprintf (buffer, "players:\n");
|
2002-10-03 21:00:35 +00:00
|
|
|
for (i = 0; i < numcl; i++)
|
2003-08-05 01:45:52 +00:00
|
|
|
dasprintf (buffer, " %s\n", clients[i]->name);
|
2002-10-03 21:00:35 +00:00
|
|
|
} else { // teamplay
|
|
|
|
for (j = 0; j < numt; j++) {
|
2003-08-05 01:45:52 +00:00
|
|
|
dasprintf (buffer, "team %s:\n", teams[j]);
|
2002-10-04 03:36:51 +00:00
|
|
|
for (i = 0; i < numcl; i++) {
|
|
|
|
team = Info_ValueForKey (svs.clients[i].userinfo, "team");
|
|
|
|
if (!strcmp (team, teams[j]))
|
2003-08-05 01:45:52 +00:00
|
|
|
dasprintf (buffer, " %s\n", clients[i]->name);
|
2002-10-04 03:36:51 +00:00
|
|
|
}
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!numcl)
|
|
|
|
return "\n";
|
2003-08-05 01:45:52 +00:00
|
|
|
for (p = buffer->str; *p; p++)
|
2002-10-04 02:29:03 +00:00
|
|
|
*p = sys_char_map[(byte) * p];
|
2003-08-05 01:45:52 +00:00
|
|
|
return buffer->str;
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
make_info_string_filter (const char *key)
|
|
|
|
{
|
|
|
|
return *key == '_' || !Info_FilterForKey (key, client_info_filters);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
SV_Record (char *name)
|
|
|
|
{
|
|
|
|
sizebuf_t buf;
|
2005-06-08 06:35:48 +00:00
|
|
|
byte buf_data[MAX_MSGLEN];
|
2002-10-03 21:00:35 +00:00
|
|
|
int n, i;
|
2003-01-06 18:28:13 +00:00
|
|
|
const char *info;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
client_t *player;
|
|
|
|
const char *gamedir, *s;
|
|
|
|
|
|
|
|
SV_InitRecord ();
|
|
|
|
|
2012-07-13 05:41:10 +00:00
|
|
|
dstring_copystr (demo_name, name);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2003-08-05 01:45:52 +00:00
|
|
|
SV_BroadcastPrintf (PRINT_CHAT, "Server started recording (%s):\n%s\n",
|
2012-07-13 05:41:10 +00:00
|
|
|
demo_disk ? "disk" : "memory",
|
|
|
|
QFS_SkipPath (demo_name->str));
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
Cvar_Set ("serverdemo", demo_name->str);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
dstring_copystr (demo_text, name);
|
|
|
|
strcpy (demo_text->str + strlen (demo_text->str) - 3, "txt");
|
2002-10-03 21:00:35 +00:00
|
|
|
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
if (sv_demotxt) {
|
2002-10-03 21:00:35 +00:00
|
|
|
QFile *f;
|
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
f = QFS_Open (demo_text->str, "w+t");
|
2002-10-03 21:00:35 +00:00
|
|
|
if (f != NULL) {
|
|
|
|
char date[20];
|
|
|
|
time_t tim;
|
|
|
|
|
|
|
|
time (&tim);
|
2003-08-05 01:45:52 +00:00
|
|
|
strftime (date, sizeof (date), "%Y-%m-%d-%H-%M", localtime (&tim));
|
|
|
|
Qprintf (f, "date %s\nmap %s\nteamplay %d\ndeathmatch %d\n"
|
2002-10-03 21:00:35 +00:00
|
|
|
"timelimit %d\n%s",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
date, sv.name, teamplay,
|
|
|
|
deathmatch, timelimit,
|
2003-08-05 01:45:52 +00:00
|
|
|
SV_PrintTeams ());
|
2002-10-03 21:00:35 +00:00
|
|
|
Qclose (f);
|
|
|
|
}
|
|
|
|
} else
|
2005-05-01 04:27:05 +00:00
|
|
|
QFS_Remove (demo_text->str);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2005-05-05 11:46:29 +00:00
|
|
|
recorder = SVR_AddUser (demo_write, demo_frame, demo_end_frame,
|
|
|
|
demo_finish, 1, 0);
|
2010-01-13 06:44:29 +00:00
|
|
|
sv.recording_demo = 1;
|
2005-05-05 11:46:29 +00:00
|
|
|
delta_sequence = -1;
|
2005-05-01 09:07:20 +00:00
|
|
|
demo_time = sv.time;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
/*-------------------------------------------------*/
|
|
|
|
|
|
|
|
// serverdata
|
|
|
|
// send the info about the new client to all connected clients
|
|
|
|
memset (&buf, 0, sizeof (buf));
|
|
|
|
buf.data = buf_data;
|
|
|
|
buf.maxsize = sizeof (buf_data);
|
|
|
|
|
|
|
|
// send the serverdata
|
|
|
|
|
|
|
|
gamedir = Info_ValueForKey (svs.info, "*gamedir");
|
|
|
|
if (!gamedir[0])
|
|
|
|
gamedir = "qw";
|
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_serverdata);
|
|
|
|
MSG_WriteLong (&buf, PROTOCOL_VERSION);
|
|
|
|
MSG_WriteLong (&buf, svs.spawncount);
|
|
|
|
MSG_WriteString (&buf, gamedir);
|
|
|
|
|
|
|
|
|
|
|
|
MSG_WriteFloat (&buf, sv.time);
|
|
|
|
|
|
|
|
// send full levelname
|
|
|
|
MSG_WriteString (&buf, PR_GetString (&sv_pr_state,
|
|
|
|
SVstring (sv.edicts, message)));
|
|
|
|
|
|
|
|
// send the movevars
|
|
|
|
MSG_WriteFloat (&buf, movevars.gravity);
|
|
|
|
MSG_WriteFloat (&buf, movevars.stopspeed);
|
|
|
|
MSG_WriteFloat (&buf, movevars.maxspeed);
|
|
|
|
MSG_WriteFloat (&buf, movevars.spectatormaxspeed);
|
|
|
|
MSG_WriteFloat (&buf, movevars.accelerate);
|
|
|
|
MSG_WriteFloat (&buf, movevars.airaccelerate);
|
|
|
|
MSG_WriteFloat (&buf, movevars.wateraccelerate);
|
|
|
|
MSG_WriteFloat (&buf, movevars.friction);
|
|
|
|
MSG_WriteFloat (&buf, movevars.waterfriction);
|
|
|
|
MSG_WriteFloat (&buf, movevars.entgravity);
|
|
|
|
|
|
|
|
// send music
|
|
|
|
MSG_WriteByte (&buf, svc_cdtrack);
|
|
|
|
MSG_WriteByte (&buf, 0); // none in demos
|
|
|
|
|
|
|
|
// send server info string
|
|
|
|
MSG_WriteByte (&buf, svc_stufftext);
|
2021-01-31 07:01:20 +00:00
|
|
|
MSG_WriteString (&buf, va (0, "fullserverinfo \"%s\"\n",
|
2002-10-03 21:00:35 +00:00
|
|
|
Info_MakeString (svs.info, 0)));
|
|
|
|
|
|
|
|
// flush packet
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
|
|
|
|
// soundlist
|
|
|
|
MSG_WriteByte (&buf, svc_soundlist);
|
|
|
|
MSG_WriteByte (&buf, 0);
|
|
|
|
|
|
|
|
n = 0;
|
|
|
|
s = sv.sound_precache[n + 1];
|
|
|
|
while (s) {
|
|
|
|
MSG_WriteString (&buf, s);
|
|
|
|
if (buf.cursize > MAX_MSGLEN / 2) {
|
|
|
|
MSG_WriteByte (&buf, 0);
|
|
|
|
MSG_WriteByte (&buf, n);
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
MSG_WriteByte (&buf, svc_soundlist);
|
|
|
|
MSG_WriteByte (&buf, n + 1);
|
|
|
|
}
|
|
|
|
n++;
|
|
|
|
s = sv.sound_precache[n + 1];
|
|
|
|
}
|
|
|
|
|
|
|
|
if (buf.cursize) {
|
|
|
|
MSG_WriteByte (&buf, 0);
|
|
|
|
MSG_WriteByte (&buf, 0);
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
}
|
|
|
|
// modellist
|
|
|
|
MSG_WriteByte (&buf, svc_modellist);
|
|
|
|
MSG_WriteByte (&buf, 0);
|
|
|
|
|
|
|
|
n = 0;
|
|
|
|
s = sv.model_precache[n + 1];
|
|
|
|
while (s) {
|
|
|
|
MSG_WriteString (&buf, s);
|
|
|
|
if (buf.cursize > MAX_MSGLEN / 2) {
|
|
|
|
MSG_WriteByte (&buf, 0);
|
|
|
|
MSG_WriteByte (&buf, n);
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
MSG_WriteByte (&buf, svc_modellist);
|
|
|
|
MSG_WriteByte (&buf, n + 1);
|
|
|
|
}
|
|
|
|
n++;
|
|
|
|
s = sv.model_precache[n + 1];
|
|
|
|
}
|
|
|
|
if (buf.cursize) {
|
|
|
|
MSG_WriteByte (&buf, 0);
|
|
|
|
MSG_WriteByte (&buf, 0);
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
}
|
|
|
|
// prespawn
|
|
|
|
|
|
|
|
for (n = 0; n < sv.num_signon_buffers; n++) {
|
|
|
|
SZ_Write (&buf, sv.signon_buffers[n], sv.signon_buffer_size[n]);
|
|
|
|
|
|
|
|
if (buf.cursize > MAX_MSGLEN / 2) {
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_stufftext);
|
2021-01-31 07:01:20 +00:00
|
|
|
MSG_WriteString (&buf, va (0, "cmd spawn %i 0\n", svs.spawncount));
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
if (buf.cursize) {
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
}
|
|
|
|
// send current status of all other players
|
|
|
|
|
|
|
|
for (i = 0; i < MAX_CLIENTS; i++) {
|
|
|
|
player = svs.clients + i;
|
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_updatefrags);
|
|
|
|
MSG_WriteByte (&buf, i);
|
|
|
|
MSG_WriteShort (&buf, player->old_frags);
|
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_updateping);
|
|
|
|
MSG_WriteByte (&buf, i);
|
|
|
|
MSG_WriteShort (&buf, SV_CalcPing (player));
|
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_updatepl);
|
|
|
|
MSG_WriteByte (&buf, i);
|
|
|
|
MSG_WriteByte (&buf, player->lossage);
|
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_updateentertime);
|
|
|
|
MSG_WriteByte (&buf, i);
|
|
|
|
MSG_WriteFloat (&buf, realtime - player->connection_started);
|
|
|
|
|
|
|
|
info = player->userinfo ? Info_MakeString (player->userinfo,
|
|
|
|
make_info_string_filter)
|
2003-03-12 16:34:26 +00:00
|
|
|
: "";
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
MSG_WriteByte (&buf, svc_updateuserinfo);
|
|
|
|
MSG_WriteByte (&buf, i);
|
|
|
|
MSG_WriteLong (&buf, player->userid);
|
|
|
|
MSG_WriteString (&buf, info);
|
|
|
|
|
|
|
|
if (buf.cursize > MAX_MSGLEN / 2) {
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
SZ_Clear (&buf);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// send all current light styles
|
|
|
|
for (i = 0; i < MAX_LIGHTSTYLES; i++) {
|
|
|
|
MSG_WriteByte (&buf, svc_lightstyle);
|
|
|
|
MSG_WriteByte (&buf, (char) i);
|
|
|
|
MSG_WriteString (&buf, sv.lightstyles[i]);
|
|
|
|
}
|
|
|
|
|
|
|
|
// get the client to check and download skins
|
|
|
|
// when that is completed, a begin command will be issued
|
|
|
|
MSG_WriteByte (&buf, svc_stufftext);
|
2021-01-31 07:01:20 +00:00
|
|
|
MSG_WriteString (&buf, va (0, "skins\n"));
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2004-03-06 04:42:43 +00:00
|
|
|
SV_WriteRecordDemoMessage (&buf);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
SV_WriteSetDemoMessage ();
|
|
|
|
// done
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
SV_CleanName
|
|
|
|
|
|
|
|
Cleans the demo name, removes restricted chars, makes name lowercase
|
|
|
|
*/
|
|
|
|
|
2003-08-05 01:45:52 +00:00
|
|
|
static char *
|
2005-06-08 06:35:48 +00:00
|
|
|
SV_CleanName (const char *name)
|
2002-10-03 21:00:35 +00:00
|
|
|
{
|
2003-08-05 01:45:52 +00:00
|
|
|
static char *text;
|
|
|
|
static size_t text_len;
|
|
|
|
char *out, c;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2003-08-05 01:45:52 +00:00
|
|
|
if (text_len < strlen (name)) {
|
|
|
|
text_len = (strlen (name) + 1023) & ~1023;
|
|
|
|
text = realloc (text, text_len);
|
|
|
|
}
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2003-08-05 01:45:52 +00:00
|
|
|
out = text;
|
|
|
|
do {
|
2005-06-08 06:35:48 +00:00
|
|
|
c = sys_char_map[(byte) *name++];
|
2003-08-05 01:45:52 +00:00
|
|
|
if (c != '_')
|
|
|
|
*out++ = c;
|
|
|
|
} while (c);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
return text;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
SV_Record_f
|
|
|
|
|
|
|
|
record <demoname>
|
|
|
|
*/
|
2003-01-06 18:28:13 +00:00
|
|
|
static void
|
2002-10-03 21:00:35 +00:00
|
|
|
SV_Record_f (void)
|
|
|
|
{
|
|
|
|
dstring_t *name = dstring_newstr ();
|
|
|
|
|
|
|
|
if (Cmd_Argc () != 2) {
|
2007-11-06 10:17:14 +00:00
|
|
|
Sys_Printf ("record <demoname>\n");
|
2002-10-03 21:00:35 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (sv.state != ss_active) {
|
2007-11-06 10:17:14 +00:00
|
|
|
Sys_Printf ("Not active yet.\n");
|
2002-10-03 21:00:35 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
if (recorder)
|
2004-03-06 03:18:14 +00:00
|
|
|
SV_Stop (0);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
dsprintf (name, "%s/%s/%s%s%s", qfs_gamedir->dir.def, sv_demoDir,
|
|
|
|
sv_demoPrefix, SV_CleanName (Cmd_Argv (1)),
|
|
|
|
sv_demoSuffix);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
// open the demo file
|
2010-08-24 07:20:07 +00:00
|
|
|
QFS_DefaultExtension (name, ".mvd");
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2022-03-31 08:27:04 +00:00
|
|
|
demo_file = QFS_Open (name->str, "wb");
|
|
|
|
if (!demo_file) {
|
|
|
|
Sys_Printf ("ERROR: couldn't open %s\n", name->str);
|
|
|
|
} else {
|
|
|
|
SV_Record (name->str);
|
|
|
|
}
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
dstring_delete (name);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
SV_EasyRecord_f
|
|
|
|
|
|
|
|
easyrecord [demoname]
|
|
|
|
*/
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static int
|
|
|
|
Dem_CountPlayers (void)
|
2002-10-03 21:00:35 +00:00
|
|
|
{
|
|
|
|
int i, count;
|
|
|
|
|
|
|
|
count = 0;
|
|
|
|
for (i = 0; i < MAX_CLIENTS; i++) {
|
|
|
|
if (svs.clients[i].name[0] && !svs.clients[i].spectator)
|
|
|
|
count++;
|
|
|
|
}
|
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static const char *
|
2002-10-03 21:00:35 +00:00
|
|
|
Dem_Team (int num)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
static const char *lastteam[2];
|
|
|
|
qboolean first = true;
|
|
|
|
client_t *client;
|
|
|
|
static int index = 0;
|
2002-10-04 03:36:51 +00:00
|
|
|
const char *team;
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
index = 1 - index;
|
|
|
|
|
|
|
|
for (i = 0, client = svs.clients; num && i < MAX_CLIENTS; i++, client++) {
|
|
|
|
if (!client->name[0] || client->spectator)
|
|
|
|
continue;
|
|
|
|
|
2002-10-04 03:36:51 +00:00
|
|
|
team = Info_ValueForKey (svs.clients[i].userinfo, "team");
|
|
|
|
if (first || strcmp (lastteam[index], team)) {
|
2002-10-03 21:00:35 +00:00
|
|
|
first = false;
|
|
|
|
num--;
|
2002-10-04 03:36:51 +00:00
|
|
|
lastteam[index] = team;
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (num)
|
|
|
|
return "";
|
|
|
|
|
|
|
|
return lastteam[index];
|
|
|
|
}
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static const char *
|
2002-10-03 21:00:35 +00:00
|
|
|
Dem_PlayerName (int num)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
client_t *client;
|
|
|
|
|
|
|
|
for (i = 0, client = svs.clients; i < MAX_CLIENTS; i++, client++) {
|
|
|
|
if (!client->name[0] || client->spectator)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
if (!--num)
|
|
|
|
return client->name;
|
|
|
|
}
|
|
|
|
|
|
|
|
return "";
|
|
|
|
}
|
|
|
|
|
2003-01-06 18:28:13 +00:00
|
|
|
static void
|
2002-10-03 21:00:35 +00:00
|
|
|
SV_EasyRecord_f (void)
|
|
|
|
{
|
|
|
|
dstring_t *name = dstring_newstr ();
|
|
|
|
dstring_t *name2 = dstring_newstr ();
|
|
|
|
int i;
|
|
|
|
|
|
|
|
if (Cmd_Argc () > 2) {
|
2007-11-06 10:17:14 +00:00
|
|
|
Sys_Printf ("easyrecord [demoname]\n");
|
2002-10-03 21:00:35 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2005-05-01 09:07:20 +00:00
|
|
|
if (recorder)
|
2004-03-06 03:18:14 +00:00
|
|
|
SV_Stop (0);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
if (Cmd_Argc () == 2)
|
|
|
|
dsprintf (name, "%s", Cmd_Argv (1));
|
|
|
|
else {
|
|
|
|
// guess game type and write demo name
|
|
|
|
i = Dem_CountPlayers ();
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
if (teamplay && i > 2) {
|
2002-10-03 21:00:35 +00:00
|
|
|
// Teamplay
|
|
|
|
dsprintf (name, "team_%s_vs_%s_%s",
|
|
|
|
Dem_Team (1), Dem_Team (2), sv.name);
|
|
|
|
} else {
|
|
|
|
if (i == 2) {
|
|
|
|
// Duel
|
|
|
|
dsprintf (name, "duel_%s_vs_%s_%s",
|
|
|
|
Dem_PlayerName (1), Dem_PlayerName (2), sv.name);
|
|
|
|
} else {
|
|
|
|
// FFA
|
2003-03-21 21:25:44 +00:00
|
|
|
dsprintf (name, "ffa_%s (%d)", sv.name, i);
|
2002-10-03 21:00:35 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Make sure the filename doesn't contain illegal characters
|
2012-05-21 23:23:22 +00:00
|
|
|
dsprintf (name2, "%s/%s%s%s%s%s",
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
qfs_gamedir->dir.def, sv_demoDir,
|
|
|
|
sv_demoDir[0] ? "/" : "",
|
|
|
|
sv_demoPrefix, SV_CleanName (name->str),
|
|
|
|
sv_demoSuffix);
|
2002-10-03 21:00:35 +00:00
|
|
|
|
2022-03-31 08:27:04 +00:00
|
|
|
if ((demo_file = QFS_NextFile (name, name2->str, ".mvd"))) {
|
2003-05-24 02:03:17 +00:00
|
|
|
SV_Record (name->str);
|
2022-03-31 08:27:04 +00:00
|
|
|
}
|
2002-10-03 21:00:35 +00:00
|
|
|
|
|
|
|
dstring_delete (name);
|
|
|
|
dstring_delete (name2);
|
|
|
|
}
|
|
|
|
|
2002-10-04 02:29:03 +00:00
|
|
|
void
|
|
|
|
Demo_Init (void)
|
|
|
|
{
|
|
|
|
int p, size = MIN_DEMO_MEMORY;
|
|
|
|
|
|
|
|
p = COM_CheckParm ("-democache");
|
|
|
|
if (p) {
|
|
|
|
if (p < com_argc - 1)
|
|
|
|
size = atoi (com_argv[p + 1]) * 1024;
|
|
|
|
else
|
2021-02-03 04:19:19 +00:00
|
|
|
Sys_Error ("Demo_Init: you must specify a size in KB after "
|
2002-10-04 02:29:03 +00:00
|
|
|
"-democache");
|
|
|
|
}
|
|
|
|
|
|
|
|
if (size < MIN_DEMO_MEMORY) {
|
2007-11-06 10:17:14 +00:00
|
|
|
Sys_Printf ("Minimum memory size for demo cache is %dk\n",
|
2002-10-04 02:29:03 +00:00
|
|
|
MIN_DEMO_MEMORY / 1024);
|
|
|
|
size = MIN_DEMO_MEMORY;
|
|
|
|
}
|
|
|
|
|
2005-05-01 04:27:05 +00:00
|
|
|
demo_name = dstring_newstr ();
|
|
|
|
demo_text = dstring_newstr ();
|
2002-10-04 02:29:03 +00:00
|
|
|
|
2021-07-28 06:01:45 +00:00
|
|
|
svs.demomem = Hunk_AllocName (0, size, "demo");
|
2002-10-04 02:29:03 +00:00
|
|
|
svs.demomemsize = size;
|
|
|
|
demo_max_size = size - 0x80000;
|
[cvar] Make cvars properly typed
This is an extremely extensive patch as it hits every cvar, and every
usage of the cvars. Cvars no longer store the value they control,
instead, they use a cexpr value object to reference the value and
specify the value's type (currently, a null type is used for strings).
Non-string cvars are passed through cexpr, allowing expressions in the
cvars' settings. Also, cvars have returned to an enhanced version of the
original (id quake) registration scheme.
As a minor benefit, relevant code having direct access to the
cvar-controlled variables is probably a slight optimization as it
removed a pointer dereference, and the variables can be located for data
locality.
The static cvar descriptors are made private as an additional safety
layer, though there's nothing stopping external modification via
Cvar_FindVar (which is needed for adding listeners).
While not used yet (partly due to working out the design), cvars can
have a validation function.
Registering a cvar allows a primary listener (and its data) to be
specified: it will always be called first when the cvar is modified. The
combination of proper listeners and direct access to the controlled
variable greatly simplifies the more complex cvar interactions as much
less null checking is required, and there's no need for one cvar's
callback to call another's.
nq-x11 is known to work at least well enough for the demos. More testing
will come.
2022-04-23 03:22:45 +00:00
|
|
|
sv_demoCacheSize_cvar.default_value = nva ("%d", size / 1024);
|
|
|
|
Cvar_Register (&serverdemo_cvar, Cvar_Info, &serverdemo);
|
|
|
|
Cvar_Register (&sv_demofps_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoPings_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoNoVis_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoUseCache_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoCacheSize_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoMaxSize_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoMaxDirSize_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoDir_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoPrefix_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demoSuffix_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_onrecordfinish_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_ondemoremove_cvar, 0, 0);
|
|
|
|
Cvar_Register (&sv_demotxt_cvar, 0, 0);
|
2002-10-04 02:29:03 +00:00
|
|
|
|
|
|
|
Cmd_AddCommand ("record", SV_Record_f, "FIXME");
|
|
|
|
Cmd_AddCommand ("easyrecord", SV_EasyRecord_f, "FIXME");
|
|
|
|
Cmd_AddCommand ("stop", SV_Stop_f, "FIXME");
|
|
|
|
Cmd_AddCommand ("cancel", SV_Cancel_f, "FIXME");
|
|
|
|
}
|