As with previous CS games, CS: GO is tweak-able, provided one has the understanding of the commands and variables involved.
The tweaks have a variety of advantages, such as increasing frame-rates, improving hit-registration, providing better view, customizing the HUD to your requirement, and much more.
The autoexec.cfg is your configuration file with all the customized in-game visual and background variables of your desire. This file will either be present in \csgo\cfg or will have to be created there to run.
The autoexec.cfg gives so much variety that it can be difficult to list each and every possible variable that can be used in it. Many autoexec configuration files are shared by players in CS: GO, and there are tons of websites with generous people sharing them (I would recommend sticking to the official forms for the sake of safety though).
Binds are commands that associate a certain action with a button on the keyboard or mouse. These can vary vastly in application, and generally change from player to player, according to preference. For example, I like to have my grenades on mouse button 5 (Mouse 5), so I would write a command like:
- bind Mouse 5 “use weapon_hegrenade”
Similarly, you could come up with tons of different binds according to your need. A few examples are as follows:
- bind MWHEELUP “invnext”
- bind MWHEELDOWN “invprev”
- bind / “toggleconsole”
- bind ALT +voicerecord
- bind backspace “toggleconsole”
- bind f “drop”
- bind g “show_loadout_toggle”
- bind j “messagemode”
- bind k “messagemode2”
- bind y “use weapon_decoy”
- bind x “use weapon_molotov; use weapon_incgrenade”
- bind v “toggle voice_scale 0 0.5 1”
- bind o “toggle mat_monitorgamma 1.6 1.8 2.0 2.2”
- bind n “toggle net_graph 0 1 3”
You can check out more binds in the sample configuration file at the end of this tweak.
There are various cl commands that can be used in the autoexec.cfg that will change various tangible settings in your HUG, display, or gameplay. CL commands vary greatly in overall application, and it takes a long time and some thorough experimentation with them to understand what each and everyone does.
Some common CL commands are:
- cl_autowepswitch 0 //Automatically switch to a weapon that you pick up – ‘0’ for disable and ‘1’ for enable.
- cl_disablefreezecam 1 //Disable the freezecam after you get killed.
- Some more advanced cl commands that alter your HUD are:
- cl_teamid_overhead_name_alpha 250 //The amount of alpha or transparency of the overhead ID names. Default value is 240
- cl_teamid_overhead_name_fadetime 0.5 //The amount of time for the overhead to fade out once your crosshair has left. Default value is 0.5
- For the rare folks who prefer playing with the weapon on the left (left-handed), you might want to consider the following command:
- cl_righthand “0” //Change to 1 for right-hand.
CL commands can be particularly useful if you feel you need to get rid of the weapon-bobbing. Some people (like me) don’t mind the visual effect, but others prefer to play without it for more stability. To do this, use the following commands:
- cl_bob_lower_amt “5” //minimum value
- cl_bobamt_lat “0.1” //minimum value
- cl_bobamt_vert “0.1” //minimum value
- cl_bobcycle “2” //maximum value = less cycle
Simiarly, if you wish to remove arm-shifting while crouching or firing the weapon, here’s a set of cl commands you might want to try out (these are a mixture of cl commands and the viewmodels command, discussed next):
- cl_viewmodel_shift_left_amt “0”
- cl_viewmodel_shift_right_amt “0”
The viewmodel commands alter the position of models on your screen. This can range from weapons and other peripherals to HUD, though generally they are used for positioning of the weapon and adjusting the field of vision.
For field of vision, consider the following command:
- viewmodel_fov 65 //Replace 65 with your desired amount – the fov should be kept according to player preference. 65 is the max value.
If you played CSS, you might want to consider the following weapon-positioning commands, which resemble Source. This can be very useful for those looking to get the old feeling back:
- viewmodel_offset_x “2”
- viewmodel_offset_y “2”
- viewmodel_offset_z “-2”
If you have any questions, or would like to share some additional tweaking and configuration techniques, please do so by commenting below.