![Cool 8)](./images/smilies/icon_cool.gif)
There is no sv_cvar INCLUDE, as there really is no sensible way force the value on the client. There is also no sv_cvar EXCLUDE, for the same reason.
Instead of "pb_sv_cvar cl_timenudge IN 0" you use EQ, eg "sv_cvar cl_timenudge EQ 0".
With the IN enforcement, cvars that are non compliant are snapped to the nearest IN parameter. Eg with '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.
With the OUT enforcement, cvars that are non compliant are snapped to the nearest OUT parameter. Eg with '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, eg a value equidistant from both lower and upper bounds would be snapped to the lower bound -0.015.
For both IN and OUT enforcement, the parameters must be low value first, high value second.
There are also GE and LE for 'greater than or equal' and 'less than or equal' enforcement respectively.