Miscellany: Spawn protection, Jump height, Deathmatch Podiums, Export & Debug commands

 

Setting Spawn Protection

Coliseum2 allows for spawn protection that gives players a brief time that they are invulnerable after spawning/respawning.  This safety period will last for a specified period of time or until the player fires a weapon.  Firing the hook will not remove the spawn safety.  Also, spawn protection will not protect against telefrags.

CVAR:  g_spawnsafety

Default is zero(0) and is measured in seconds.
Example:  To set a 5 second spawn protection period, set g_spawnsafety "5".

 

Setting Jump Height

Coliseum2 allows server admins to adjust how high a player can jump.

CVAR:  g_jumpheight

Default is 270.

 

Turning Off Deathmatch Podiums

Some server may have a map rotation scheme with some typos that may cause the deathmatch podiums to "artifact" after a map restarts. This is, the deathmatch poduims may hang around and still be visible during play.  This problem has been determined to be caused by some rare typos in the map rotation command portion of config files.  You may turn off deathmatch podiums completely.

CVAR:  g_dmpodium

0 - Off
1 - On - default

 

Exporting Server Game Variables

Server admins invariably spend large amounts of time tweaking variables and other settings to make the perfect Quake3 server.  It can get rather cumbersome jotting down variable settings on paper and have to manually edit config files later.  Enter the export command:

Command Usage:

export <filename>
!export <filename>

Server admins may, at anytime, use the export command to dump out all server game variables to a designated file.  Simply enter the export command followed by the filename with any extension and all variable settings and command permissions will be written out to that file.  It's as easy as that.  An error will be returned if the filename already exists and an override may be issued with the !export command.  The filename q3config.cfg is reserved and can never be used with the export or !export command, for obvious reasons.

Latched variable changes are not effective until after a map restart.  Make sure you have properly restarted a map before you use the export command.  Otherwise, exported latched variables may not reflect the correct desired values.

Currently, variables g_password and g_ref_password are not exported.

 

Debug Commands

There are two commands available to the server and one on the client that will hopefully assist in reporting bugs.  These commands are entered at the console and must be preceded by the "/".

Command Usage:  /runestatus

If you should suspect that runes are not spawning correctly for any reason, this command will tell you the min, max, total and allowed runes.

 

Command Usage:  /clients, /players, /who

This command is available to both the server and clients and will tell you what version other clients are playing with, their client number, the type of code they're using (VM, DLL or Linux LIB), the name of the player, their team and roles.  Players playing with versions older than 1.8 will show a version number of zero (0).  Role indicators are [R]eferee and/or team [C]aptain.

 


Table of Contents Enhanced IP Banning Role:  Referee