Difference between revisions of "Cvar Restrictions"
(formatting & replacement of text "Exclamation" with symbol) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 16: | Line 16: | ||
== EQ == | == EQ == | ||
| − | EQ requires one argument.< | + | '''EQ''' requires one argument.<br> |
| − | EQ is used when a cvar is supposed to | + | '''EQ''' is used when a cvar is supposed to '''EQ'''ual a certain value. |
== GE == | == GE == | ||
| − | GE requires one argument.< | + | '''GE''' requires one argument.<br> |
| − | GE is used when a cvar is supposed to be | + | '''GE''' is used when a cvar is supposed to be '''G'''reater or '''E'''qual a certain value. |
== LE == | == LE == | ||
| − | LE requires one argument.< | + | '''LE''' requires one argument.<br> |
| − | LE is used when a cvar is supposed to be | + | '''LE''' is used when a cvar is supposed to be '''L'''ower or '''E'''qual a certain value. |
== 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 |
| − | + | ||
== 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 |
| − | + | ||
== 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: | Example: | ||
| − | <pre>sv_cvar cg_fov IN 90 120 | + | <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. | ||
| Line 58: | Line 56: | ||
A player who had a cg_fov of 130 would see it snapped to 120.</pre> | A player who had a cg_fov of 130 would see it snapped to 120.</pre> | ||
| − | + | http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 1st Argument = lower limit<br> | |
| − | + | http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 2nd Argument = upper limit | |
== OUT == | == OUT == | ||
| − | OUT requires two arguments | + | '''OUT''' requires two arguments.<br> |
| − | + | 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: | Example: | ||
| − | <pre>sv_cvar m_pitch OUT -0.015 0.015 | + | <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. | ||
| Line 76: | Line 73: | ||
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> | 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> | ||
| − | + | http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 1st Argument = lower limit<br> | |
| − | + | http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 2nd Argument = upper limit | |
== INCLUDE == | == INCLUDE == | ||
| − | INCLUDE requires two arguments | + | '''INCLUDE''' requires two arguments.<br> |
| − | INCLUDE is used when a cvar is supposed to | + | '''INCLUDE''' is used when a cvar is supposed to '''INCLUDE''' a certain substring. Otherwise it will set the cvar to default. |
== EXCLUDE == | == EXCLUDE == | ||
| − | EXCLUDE requires two arguments | + | '''EXCLUDE''' requires two arguments.<br> |
| − | EXCLUDE is used when a cvar is supposed to not include a certain substring. Otherwise it will set the cvar to default. | + | '''EXCLUDE''' is used when a cvar is supposed to not include a certain substring. Otherwise it will set the cvar to default. |
| + | |||
| + | ---- | ||
| + | |||
| + | http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif If a cvar is changed that needs a vid_restart, etpro will force a vid_restart on the client after snapping them into range. | ||
| − | + | [[Category:ETPro:Server_Cvars]] | |
Latest revision as of 23:22, 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
WITHOUTBITS
WITHOUTBITS requires one argument.
WITHOUTBITS is used when a bitmask-cvar is supposed to not include a certain bitflag
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.
http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 1st Argument = lower limit
http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 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.
http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 1st Argument = lower limit
http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif 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.
http://bani.anime.net/banimod/forums/images/smiles/icon_exclaim.gif If a cvar is changed that needs a vid_restart, etpro will force a vid_restart on the client after snapping them into range.
