Jump to content

Console variables: Difference between revisions

3.1 is released, so Devfeature templates have been removed
m (Added "cl_protectcvars".)
(3.1 is released, so Devfeature templates have been removed)
Line 96: Line 96:
|CL_BackupCommands
|CL_BackupCommands
CL_BackupCommands 0
CL_BackupCommands 0
|{{Devfeature|3.1|alpha}} Specifies how many backup copies of old move or weapon select commands (up to three) the client will send to the server per tic. This is useful if the client is suffering from noticeable packet loss, but due to the increased outbound net traffic, it's recommended that it only be enabled in those cases.
|Specifies how many backup copies of old move or weapon select commands (up to three) the client will send to the server per tic. This is useful if the client is suffering from noticeable packet loss, but due to the increased outbound net traffic, it's recommended that it only be enabled in those cases.
|-
|-
|CL_CapFPS
|CL_CapFPS
Line 136: Line 136:
|CL_ProtectCVars
|CL_ProtectCVars
CL_ProtectCVars True
CL_ProtectCVars True
|{{Devfeature|3.1|alpha}} When true, any CVars that were modified by [[ConsoleCommand]] will be restored to their original values upon exiting the game. This is used to prevent mods from changing a user's settings permanently, even maliciously. Note that manually changing a CVar's value still archives the new value, as expected.
|When true, any CVars that were modified by [[ConsoleCommand]] will be restored to their original values upon exiting the game. This is used to prevent mods from changing a user's settings permanently, even maliciously. Note that manually changing a CVar's value still archives the new value, as expected.
|-
|-
|CL_RespawnOnFire
|CL_RespawnOnFire