Difference between revisions of "Cvar Restrictions"
| Line 16: | Line 16: | ||
== EQ == | == EQ == | ||
| − | EQ requires one argument | + | EQ requires one argument.<BR> |
EQ is used when a cvar is supposed to EQual a certain value. | EQ is used when a cvar is supposed to EQual a certain value. | ||
| Line 22: | Line 22: | ||
== GE == | == GE == | ||
| − | GE requires one argument | + | GE requires one argument.<BR> |
GE is used when a cvar is supposed to be Greater or Equal a certain value. | GE is used when a cvar is supposed to be Greater or Equal a certain value. | ||
| Line 28: | Line 28: | ||
== LE == | == LE == | ||
| − | LE requires one argument | + | LE requires one argument.<BR> |
LE is used when a cvar is supposed to be Lower or Equal a certain value. | LE is used when a cvar is supposed to be Lower or Equal a certain value. | ||
| Line 34: | Line 34: | ||
== WITHBITS == | == WITHBITS == | ||
| − | WITHBITS requires one argument | + | WITHBITS requires one argument<BR> |
| − | WITHBITS is used when a bitmask-cvar is supposed to include a certain bitflag | + | WITHBITS is used when a bitmask-cvar is supposed to include a certain bitflag<BR> |
Exclamation For further information regarding bitmask-cvars look here | Exclamation For further information regarding bitmask-cvars look here | ||
| Line 41: | Line 41: | ||
== WITHOUTBITS == | == WITHOUTBITS == | ||
| − | WITHOUTBITS requires one argument | + | WITHOUTBITS requires one argument<BR> |
| − | WITHOUTBITS is used when a bitmask-cvar is supposed to not include a certain bitflag | + | WITHOUTBITS is used when a bitmask-cvar is supposed to not include a certain bitflag<BR> |
| − | Exclamation For further information regarding bitmask-cvars look here | + | Exclamation For further information regarding bitmask-cvars look here<BR> |
== IN == | == IN == | ||
| − | IN requires two arguments | + | IN requires two arguments<BR> |
With the IN enforcement, cvars that are non compliant are snapped to the nearest IN parameter. | With the IN enforcement, cvars that are non compliant are snapped to the nearest IN parameter. | ||
| − | Example: sv_cvar cg_fov IN 90 120 | + | |
| + | Example: | ||
| + | <pre>sv_cvar cg_fov IN 90 120 | ||
| + | |||
A player who had a cg_fov of 40 would see it snapped to 90. | A player who had a cg_fov of 40 would see it snapped to 90. | ||
| − | A player who had a cg_fov of 130 would see it snapped to 120. | + | |
| + | A player who had a cg_fov of 130 would see it snapped to 120.</pre> | ||
| + | |||
Exclamation 1st Argument = lower limit | Exclamation 1st Argument = lower limit | ||
Exclamation 2nd Argument = upper limit | Exclamation 2nd Argument = upper limit | ||
| Line 60: | Line 65: | ||
OUT requires two arguments | OUT requires two arguments | ||
| + | |||
With the OUT enforcement, cvars that are non compliant are snapped to the nearest OUT parameter. | With the OUT enforcement, cvars that are non compliant are snapped to the nearest OUT parameter. | ||
| − | Example: sv_cvar m_pitch OUT -0.015 0.015 | + | |
| + | Example: | ||
| + | <pre>sv_cvar m_pitch OUT -0.015 0.015 | ||
| + | |||
A player who had a m_pitch of -0.010 would see it snapped to -0.015. | A player who had a m_pitch of -0.010 would see it snapped to -0.015. | ||
| + | |||
A player who had an m_pitch of 0.04 would see it snapped to 0.015. | A player who had an m_pitch of 0.04 would see it snapped to 0.015. | ||
| − | A player who had an m_pitch of 0.00 (a value equidistant from both lower and upper bounds) would be snapped to the lower bound -0.015. | + | |
| + | A player who had an m_pitch of 0.00 (a value equidistant from both lower and upper bounds) would be snapped to the lower bound -0.015.</pre> | ||
Exclamation 1st Argument = lower limit | Exclamation 1st Argument = lower limit | ||
Exclamation 2nd Argument = upper limit | Exclamation 2nd Argument = upper limit | ||
Revision as of 16:11, 5 November 2005
The sv_cvar setting is for the etpro cvar range enforcement mechanism. Its similar to PunkBuster's cvar range checking in that it uses nearly the same syntax. However it is different in that instead of simply warning the user that their cvars are out of range, it actually forces them to server-enforced values. This is used as it is better than having players scrambling to type in the console trying to get their cvars into compliance before they get kicked by PunkBuster.
Possibilities:
- sv_cvar cvarname EQ value
- sv_cvar cvarname GE value
- sv_cvar cvarname LE value
- sv_cvar cvarname WITHBITS bitflag
- sv_cvar cvarname WITHOUTBITS bitflag
- sv_cvar cvarname IN low_value high_value
- sv_cvar cvarname OUT low_value high_value
- sv_cvar cvarname INCLUDE substring default
- sv_cvar cvarname EXCLUDE substring default
EQ
EQ requires one argument.
EQ is used when a cvar is supposed to EQual a certain value.
GE
GE requires one argument.
GE is used when a cvar is supposed to be Greater or Equal a certain value.
LE
LE requires one argument.
LE is used when a cvar is supposed to be Lower or Equal a certain value.
WITHBITS
WITHBITS requires one argument
WITHBITS is used when a bitmask-cvar is supposed to include a certain bitflag
Exclamation For further information regarding bitmask-cvars look here
WITHOUTBITS
WITHOUTBITS requires one argument
WITHOUTBITS is used when a bitmask-cvar is supposed to not include a certain bitflag
Exclamation For further information regarding bitmask-cvars look here
IN
IN requires two arguments
With the IN enforcement, cvars that are non compliant are snapped to the nearest IN parameter.
Example:
sv_cvar cg_fov IN 90 120 A player who had a cg_fov of 40 would see it snapped to 90. A player who had a cg_fov of 130 would see it snapped to 120.
Exclamation 1st Argument = lower limit Exclamation 2nd Argument = upper limit
OUT
OUT requires two arguments
With the OUT enforcement, cvars that are non compliant are snapped to the nearest OUT parameter.
Example:
sv_cvar m_pitch OUT -0.015 0.015 A player who had a m_pitch of -0.010 would see it snapped to -0.015. A player who had an m_pitch of 0.04 would see it snapped to 0.015. A player who had an m_pitch of 0.00 (a value equidistant from both lower and upper bounds) would be snapped to the lower bound -0.015.
Exclamation 1st Argument = lower limit Exclamation 2nd Argument = upper limit
INCLUDE
INCLUDE requires two arguments INCLUDE is used when a cvar is supposed to include a certain substring. Otherwise it will set the cvar to default.
EXCLUDE
EXCLUDE requires two arguments EXCLUDE is used when a cvar is supposed to not include a certain substring. Otherwise it will set the cvar to default.
Exclamation If a cvar is changed that needs a vid_restart, etpro will force a vid_restart on the client after snapping them into range.
