Value Feature 8 No falling damage 16 Fixed field-of-view: Players' cg_fov settings will be locked at 90. 32 No footsteps 64 No item reset: When a team wins a round all the living players will not have their health and weapon ammo reset. 128 No team reset: When a team wins a round, their players will not be automatically thawed. 256 Weapon stay: Weapons will not disappear when picked up. 512 No playerclip: Players can move through so-called "clip brushes", invisible volumes which are used to close certain areas off. 1024 Nightmare mode: All weapons do mega damage with 200 starting ammo. This is mostly used to set up instagib Freeze Tag servers. Note that with weaponlimit set to 2048, the Gauntlet will not do mega damage. 2048 No self damage: Splash damage weapons will not hurt the player who fires them.

For example, if you wanted a "nightmare mode" server with no falling damage, you would set dmflags to 1032 (8 + 1024).

Value Weapon 1 Machinegun 2 Shotgun 4 Grenade Launcher 8 Rocket Launcher 16 Lightning Gun 32 Railgun 64 Plasmagun 128 BFG10K

For example, if you wanted players to spawn with a machinegun, shotgun, and railgun, you would set wpflags to 35 (1 + 2 + 32).

A number usually between 0 and 1 that is multiplied against the reload time. 0 is no reload time, 1 is normal. Settings below 0.5 are not recommended, as reload times will quickly start to become framerate-dependent for some weapons. (For example, if it is set to 0.5, the lightning gun will not fire as quickly for players whose framerates are below 40.) You can get around this by using pmove_fixed.

This setting is probably most useful in instagib mode. Here is a list of reload times for the various weapons:

Weapon Reload Time Gauntlet 0.4 (2/5) seconds Machinegun 0.1 (1/10) seconds Shotgun 1 second Grenade Launcher 0.8 (8/10) seconds Rocket Launcher 0.8 (8/10) seconds Lightning Gun 0.05 (1/20) seconds Railgun 1.5 (1 1/2) seconds Plasmagun 0.1 (1/10) seconds BFG10K 0.2 (1/5) seconds

For example, if you wanted the railgun to reload every second, you would set g_reloadFactor to 0.666.

The implementation of this has changed. Previously, having g_smoothClients set to "1" would simply prepare for extrapolation on clients that set cg_smoothClients to "1". Having g_smoothClients enabled on the server and cg_smoothClients enabled on the client was supposed to smooth out other players who would otherwise skip around because of a laggy connection. (It didn't work.)

g_smoothClients now extrapolates player positions on the server, making cg_smoothClients unnecessary and reducing network bandwidth requirements somewhat. The only downside is a nearly unappreciable amount of CPU usage. For the sake of your clients who would actually like to hit a player who would otherwise be skipping around, please leave this enabled unless you are really strapped for CPU power.

With the lightning gun being so easy to use with lag compensation turned on, there has been a big debate over whether or not it's too powerful. People who say it is contend that the damage amount was assigned after the networking was in place; therefore the weapon had to be overpowered to make it useful. People who say it isn't say that the people on the receiving end simply aren't used to having the shaft pointed at them so much by people who can use it, and haven't had a chance to learn to dodge it properly.

I lean toward the latter, which is why the default on this setting is the damage the lightning gun does normally. However, if you have a problem with its overuse on your server, you might try setting it to 7 after removing it from wpflags.

Disable specific voting options by setting these values to 0. Here is the whole list of names:

vote_capturelimit vote_timelimit vote_warmup vote_friendlyfire vote_gametype vote_grapple vote_lagcomp vote_kick vote_remove vote_putblue vote_putred vote_map vote_restart vote_nextmap vote_railjump vote_opinion vote_config

Of all these vote control variables, only vote_config's default value is "0", because it requires some configuration first.

All of the configuration files a player may vote on are in the directory votecfgs, inside the ufreeze directory. Five files are supplied as examples: casual.cfg, competition.cfg, instagib.cfg, 3bots.cfg, and nobots.cfg. The last two shouldn't need any changes, but if you want players to vote in new game types, you MUST make your votable configs match your server's config. The reason is that the configs are simply executed as if you had done an "exec votecfgs/casual.cfg" (for instance) at the server's command line, and will overwrite any settings they please. If you make them match, it won't matter.

At the end of each game type votable config is the command hard_restart. This is like map_restart, except that it forces the server to reload the map - in case items were disabled or enabled.

Use these to change the amount of ammo players start with for each gun. The gun must be given to the player upon spawning using wpflags first. Here is a list of the variables and their default values:

Variable Default Variable Default ammo_mg 100 ammo_sg 10 ammo_gl 5 ammo_rl 5 ammo_lg 60 ammo_rg 10 ammo_pg 30 ammo_bfg 15

Note that in nightmare mode (dmflags 1024), these values do nothing since players spawn in with 200 ammo for each weapon.

cg_pmove_accurate addresses framerate-dependent behavior by eliminating rounding error rather than forcing all movement into frames of constant duration - which does not create the same problems as pmove_fixed does. It also takes a little less processing time to advance a player than pmove_fixed does, both on the client and on the server.

cg_pmove_fixed feels almost exactly like pmove_fixed 1, pmove_msec 8. You should probably only disable it if you have serious incoming bandwidth issues (cg_pmove_accurate takes up to about 50 bytes/sec of bandwidth), or if the very slight difference between it and pmove_fixed (or normal, framerate-dependent movement) bothers you.

This can also be used to opt into lag compensation for certain weapons. It's a binary mask like dmflags - so add up the numbers for the weapons you want lag compensated and set cg_delag to that.

Value Weapon 1 All hitscan weapons (overrides any other setting) 2 Machinegun 4 Shotgun 8 Lightning Gun 16 Railgun

For example, if you wanted lag compensation on every weapon but the railgun, you would set cg_delag to 14 (2 + 4 + 8).