ck, you may want to enable this, but I highly recommend disabling it in a game with any amount of random kick/accuracy. Keeping it disabled in these games will allow you to see when you've scored a true hit. This defaults to 0 (off). cl_updaterate XX - This CVAR controls the number of network updates it requests per second from the server. It's similar to the "snaps" setting in Quake3, which the exception that you don't have to set it to divisors of 40 for optimal results. It defaults to 20. People with broadband connections might want to set this to 30-40, but in larger games, 25 or less is recommended. Modem users should find the best mix of bandwidth usage/smoothness at 20, but if you are joining large games with a 33.6 or worse connection, setting this to 15 will cut your bandwidth use enough to keep you in the game. For those of you gaming on a LAN, 50 is an optimal setting. Just to note, choppiness of average player movement is hard to notice until it's set below 13. The only times lower update rates become noticeable are when objects in game move very quickly (for example, a rocket flying towards your face). cl_cmdrate XX - This CVAR is similar to cl_updaterate, but instead of updates from the server, this controls updates to the server. The separation of these two allows you to adjust them individually for your up/downstream bandwidth. This defaults to 30. Due to the fact that your outgoing bandwidth doesn't change as much as your incoming bandwidth in large games, modem users can get away with keeping this CVAR set to 30. Broadband users will want this set to 40-50. 50 for LAN gamers. fps_max XXX - This is the new all-in-one framerate limiter CVAR for the new Half-Life. This affects LAN, Internet and Single player play modes. Due to the fact that setting this high will no longer create lag, I'd suggest that users set this to its maximum value of 100. This could be changed to a lower setting if the user wishes to reduce CPU load...
