best 3 cs 1.6 configs updated

HeatoN config for counter strike 1.6:

unbindall
bind "TAB" "+showscores"
bind "ENTER" "+attack"
bind "ESCAPE" "cancelselect"
bind "SPACE" "+duck"
bind "'" "+moveup"
bind "*" "chooseteam"
bind "+" "sizeup"
bind "," "buyammo1"
bind "-" "sizedown"
bind "." "buyammo2"

bind "/" "+movedown"
bind "0" "slot10"
bind "1" "slot1"
bind "2" "slot2"
bind "3" "slot3"
bind "4" "slot4"
bind "5" "slot5"
bind "6" "slot6"
bind "7" "slot7"
bind "8" "slot8"
bind "9" "slot9"
bind ";" "+mlook"
bind "=" "sizeup"
bind "[" "/slap"
bind "]" "/slay"
bind "`" "toggleconsole"
bind "a" "+moveleft"
bind "b" "buyammo2"
bind "d" "+moveright"
bind "e" "+attack2"
bind "f" "+jump"
bind "g" "drop"
bind "j" "buyequip"
bind "l" "say 92.61.37.93:27015 CSDM"
bind "m" "buy"
bind "n" "buyammo1"
bind "p" "amx_aiosmenu"
bind "r" "+reload"
bind "s" "+back"
bind "t" "impulse 201"
bind "u" "messagemode2"
bind "v" "+use"
bind "w" "+forward"
bind "y" "messagemode"
bind "~" "toggleconsole"
bind "UPARROW" "+forward"
bind "DOWNARROW" "+back"
bind "LEFTARROW" "+left"
bind "RIGHTARROW" "+right"
bind "ALT" "+strafe"
bind "CTRL" "+duck"
bind "SHIFT" "+speed"
_cl_autowepswitch "1"
_snd_mixahead "0.1"
ati_npatch "0"
ati_subdiv "0"
bgmvolume "1.000000"
bottomcolor "0"
brightness "10"
cl_allowdownload "1"
cl_allowupload "1"
cl_backspeed "400"
cl_cmdbackup "20"
cl_cmdrate "101"
cl_corpsestay "600"
cl_crosshair_color "50 250 50"
cl_crosshair_size "3"
cl_crosshair_translucent "0"
cl_dlmax "96"
cl_download_ingame "1"
cl_dynamiccrosshair "0"
cl_forwardspeed "400"
cl_himodels "0"
cl_idealpitchscale "0.8"
cl_lc "1"
cl_logocolor "#Valve_Red"
cl_logofile "skull"
cl_lw "1"
cl_minmodels "0"
cl_radartype "0"
cl_righthand "1"
cl_shadows "1"
cl_timeout "35"
cl_updaterate "101"
cl_vsmoothing "0.05"
cl_weather "1"
con_color "255 180 30"
console "0.000000"
crosshair "1.000000"

fastsprites "0"
fps_max "101"
fps_modem "0.0"
gamma "3"
gl_dither "1"
gl_flipmatrix "0"
gl_fog "1"
gl_monolights "0"
gl_overbright "0"
gl_polyoffset "0.1"
hisound "1"
hpk_maxsize "4"
hud_capturemouse "1"
hud_centerid "1"
hud_draw "1"
hud_fastswitch "1"
hud_saytext_internal "1"
hud_takesshots "0"
joystick "0"
lookspring "0"
lookstrafe "0"
m_filter "0"
m_forward "1"
m_pitch "0.022"
m_side "0.8"
m_yaw "0.022"
model "arctic"
MP3FadeTime "2.0"
MP3Volume "0.110000"
mp_decals "300"
name "HeatoN"
net_graph "3"
net_graphpos "1"
net_scale "5"
r_bmodelhighfrac "5.0"
r_detailtextures "0"
s_a3d "0.0"
s_automax_distance "30"
s_automin_distance "2"
s_bloat "2.0"
s_distance "60"
s_doppler "0.0"
s_eax "0.0"
s_leafnum "0"
s_max_distance "1000"
s_min_distance "5"
s_numpolys "200"
s_polykeep "1000000000"
s_polysize "10000000"
s_refdelay "4"
s_refgain "0.4"
s_rolloff "1.0"
s_verbwet "0.25"
sensitivity "1.5"
skin ""
spec_autodirector_internal "1"
spec_drawcone_internal "1"
spec_drawnames_internal "1"
spec_drawstatus_internal "1"
spec_mode_internal "4"
spec_pip "0"
suitvolume "0.25"
sv_aim "0"
sv_voiceenable "1"
team ""
topcolor "0"
viewsize "110"
voice_enable "1"
voice_forcemicrecord "1"
voice_modenable "0"
voice_scale "2"
volume "0.1"
setinfo "_ah" "0"
setinfo "_vgui_menus" "0"
setinfo "lang" "sv"
+mlook
exec userconfig.cfg

  navi markeloff config for counter strike 1.6:

unbindall
bind "TAB" "+showscores"
bind "ENTER" "+attack"
bind "ESCAPE" "cancelselect"
bind "SPACE" "+jump"
bind "'" "+moveup"
bind "+" "sizeup"
bind "," "buyammo1"
bind "-" "sizedown"
bind "." "buyammo2"
bind "/" "+movedown"
bind "0" "slot10"
bind "1" "slot1"
bind "2" "slot2"
bind "3" "slot3"
bind "4" "slot4"
bind "5" "slot5"
bind "6" "slot6"
bind "7" "slot7"
bind "8" "slot8"
bind "9" "slot9"
bind ";" "+mlook"
bind "=" "pb menu"
bind "[" "invprev"
bind "]" "invnext"
bind "`" "toggleconsole"
bind "a" "+moveleft"
bind "b" "buy"
bind "c" "radio3"
bind "d" "+moveright"
bind "e" "+use"
bind "g" "drop"
bind "i" "showbriefing"
bind "j" "cheer"
bind "k" "+voicerecord"
bind "l" "+commandmenu"
bind "m" "chooseteam"
bind "n" "nightvision"
bind "o" "buyequip"
bind "q" "lastinv"
bind "r" "+reload"
bind "s" "+back"
bind "t" "impulse 201"
bind "u" "messagemode2"
bind "v" "buyequip"
bind "w" "+forward"
bind "x" "radio2"
bind "y" "messagemode"
bind "z" "radio1"
bind "~" "toggleconsole"
bind "UPARROW" "+forward"
bind "DOWNARROW" "+back"
bind "LEFTARROW" "+left"
bind "RIGHTARROW" "+right"
bind "ALT" "+strafe"
bind "CTRL" "+speed"
bind "SHIFT" "+duck"
bind "F1" "+score"
bind "F5" "snapshot"
bind "F6" "save quick"
bind "F7" "load quick"
bind "F10" "quit prompt"
bind "F12" "snapshot"
bind "INS" "+klook"
bind "PGDN" "+lookdown"
bind "PGUP" "+lookup"
bind "END" "centerview"
bind "MWHEELDOWN" "+jump"
bind "MWHEELUP" "invprev"
bind "MOUSE1" "+attack"
bind "MOUSE2" "+attack2"
bind "PAUSE" "pause"
_cl_autowepswitch "0"
_snd_mixahead "0.1"
ati_npatch "1.0"
ati_subdiv "2.0"
bgmvolume "1.000000"
bottomcolor ""
brightness "2"
cl_allowdownload "0"
cl_allowupload "1"
cl_backspeed "400"
cl_cmdbackup "2"
cl_cmdrate "100"
cl_corpsestay "0.000000"
cl_crosshair_color "50 100 250"
cl_crosshair_size "large"
cl_crosshair_translucent "0"
cl_dlmax "128"
cl_download_ingame "1"
cl_dynamiccrosshair "0"
cl_forwardspeed "400"
cl_himodels "0"
cl_idealpitchscale "0.8"
cl_lc "1"
cl_logocolor "#Valve_Orange"
cl_logofile "lambda"
cl_lw "1"
cl_minmodels "0"
cl_radartype "1"
cl_righthand "0"
cl_shadows "0"
cl_timeout "300"
cl_updaterate "100"
cl_vsmoothing "0.05"
cl_weather "0"
con_color "50 150 250"
console "1.000000"
crosshair "1.000000"
fastsprites "0"
fps_max "101"
fps_modem "0.0"
gamma "3"
gl_dither "1"
gl_flipmatrix "0"
gl_fog "1"
gl_monolights "0"
gl_overbright "0"
gl_polyoffset "0.1"
hisound "1"
hpk_maxsize "4"
hud_capturemouse "1"
hud_centerid "1"
hud_draw "1"
hud_fastswitch "1"
hud_saytext_internal "1"
hud_takesshots "0"
joystick "0"
lookspring "0.000000"
lookstrafe "0.000000"
m_filter "1"
m_forward "1"
m_pitch "0.022"
m_side "0.8"
m_yaw "0.022"
model "gordon"
MP3FadeTime "2.0"
MP3Volume "0.800000"
mp_decals "0"
name "marKeloN~~~~~"
net_graph "0"
net_graphpos "1"
net_scale "5"
r_bmodelhighfrac "5.0"
r_detailtextures "0"
s_a3d "0.0"
s_automax_distance "30.0"
s_automin_distance "2.0"
s_bloat "2.0"
s_distance "60"
s_doppler "0.0"
s_eax "0.0"
s_leafnum "0"
s_max_distance "1000.0"
s_min_distance "8.0"
s_numpolys "200"
s_polykeep "1000000000"
s_polysize "10000000"
s_refdelay "4"
s_refgain "0.4"
s_rolloff "1.0"
s_verbwet "0.25"
sensitivity "2.45"
skin ""
spec_autodirector_internal "1"
spec_drawcone_internal "1"
spec_drawnames_internal "1"
spec_drawstatus_internal "1"
spec_mode_internal "2"
spec_pip "0"
suitvolume "0.250000"
sv_aim "0"
sv_voiceenable "1"
team ""
topcolor ""
viewsize "110"
voice_enable "1"
voice_forcemicrecord "1"
voice_modenable "1"
voice_scale "2"
volume "0.08"
setinfo "_ah" "0"
setinfo "_pw" "2F1"
setinfo "_vgui_menus" "0"
setinfo "_rpgm_cfg" "11"
setinfo "_pw-pcw" "zdarova332"
+mlook
+jlook
exec userconfig.cfg

SpawN orginal config for cs1.6:

// This file is overwritten whenever you change your user settings in the game.
// Add custom configurations to the file "userconfig.cfg".

unbindall
bind "TAB" "+showscores"
bind "ENTER" "+attack"
bind "ESCAPE" "cancelselect"
bind "SPACE" "+attack2"
bind "'" "+moveup"
bind "+" "sizeup"
bind "," "buyammo1"
bind "-" "sizedown"
bind "." "buyammo2"
bind "/" "+movedown"
bind "0" "slot10"
bind "1" "slot1"
bind "2" "slot2"
bind "3" "slot3"
bind "4" "slot4"
bind "5" "slot5"
bind "6" "slot6"
bind "7" "slot7"
bind "8" "slot8"
bind "9" "slot9"
bind ";" "+mlook"
bind "=" "sizeup"
bind "[" "invprev"
bind "]" "invnext"
bind "`" "toggleconsole"
bind "a" "+moveleft"
bind "b" "buy"
bind "c" "radio3"
bind "d" "+moveright"
bind "e" "+use"
bind "f" "impulse 100"
bind "g" "drop"
bind "h" "+commandmenu"
bind "i" "showbriefing"
bind "j" "cheer"
bind "k" "+voicerecord"
bind "l" "showbriefing"
bind "m" "chooseteam"
bind "n" "nightvision"
bind "o" "buyequip"
bind "p" "stopsound"
bind "q" "lastinv"
bind "r" "+reload"
bind "s" "+back"
bind "t" "impulse 201"
bind "u" "messagemode2"
bind "w" "+forward"
bind "x" "radio2"
bind "y" "messagemode"
bind "z" "radio1"
bind "~" "toggleconsole"
bind "UPARROW" "+forward"
bind "DOWNARROW" "+back"
bind "LEFTARROW" "+left"
bind "RIGHTARROW" "+right"
bind "ALT" "+strafe"
bind "CTRL" "+duck"
bind "SHIFT" "+speed"
bind "F1" "autobuy"
bind "F2" "rebuy"
bind "F5" "snapshot"
bind "F6" "save quick"
bind "F7" "load quick"
bind "F8" "amx_menu"
bind "F10" "pb menu"
bind "F11" "host_framerate 0"
bind "F12" "host_framerate 0.1"
bind "MWHEELDOWN" "+jump"
bind "MWHEELUP" "+jump"
bind "MOUSE1" "+attack"
bind "MOUSE2" "+jump"
bind "PAUSE" "pause"

Mostly played map in cs 1.6 and information

de_dust2 :

Pistol Round:

Most professional teams play it by spawn and have a basic setup. The strategy I’ve always used is a defensive long, 1 agro short, 2 middle, 1 b defensive. The main goal for the CT is to get the players low by using grenades and slow down rushes with flashes. (The basic buy is Defuse Kit + Nade + Flash)

Long Player – 

Picks and counts players as they enter ct side of long. Makes a quick call and players rotate by how many the player calls. The long player is determined by the spawn, closest long will take this position. (This player is required to boost the short player up to short for the quick agro pick)

Short Player – 

2nd closest to A and must be extremely fast with the boosting if they are to make the strat work. (this player must buy NADE + SMOKE + FLASH) Once up onto short stairs he will flash it then smoke lower dark then push up catwalk n spot the players rushing short/middle if seen grenades and falls back to stairs waiting for a rush. (makes a fast call counting the players)

B Player – 

Closest to B. This player uses the basic buy. This player picks b from the window. He will run in pre flash b then fall back to window and hold. This players main goal is to get a early call for the quick rotate to retake B. MUST GET THE NADE INTO THE BACK MID OF B BOX TO LOWER PLAYERS.

2 Middle players –

 The two middle spawned players will hold mid. 1 will spot cat walk n try get binks n get the early pick for the short player. The other player with stand close to the doors trying to pick the guy picking middle. (Glock vs USP = USP Winner.) This player is the rotater so if a call is made he is first there to backup and will get the nade into them. The other player who is spotting cat walk needs to be sharp n precise so I recommend the sharpest aimer to take this position.

Retakes -

Retaking Long –

The player holding long MUST count the players n try spot the bomb to make the rotate work well… you don’t want them to goblin plant B. It is so easy to kill them while crossing long. You just need to all stand in CT Spawn strafing n binking n just nade into the site easy kills. You must remember it may be a split so the short player needs to always be watching short so he isnt “gayed.”

Retaking B –

The close middle player will firstly go until 5 players are spotted or the bomb is then all players will gren into site then all flash over and force the retake, first player checking gay spot (left of B) 2nd going for behind middle b box and the other 3 going random positions. (Don’t retake from dark)

Retaking short –

You cant do much in this situation but have the long player still hold long and the guy in middle try bink them all and the player holding short nade and try spam them with the usp. The middle close player can easily push up middle and anal them while the other players flash/nade them from ct spawn.

This is a pretty advanced strat that will need to be dry ran, but once its known and everyone knows how to retake you will find your self winning those pistol rounds you were losing previously. As most of you know the pistol strat is a must win for any competitions as it can lead to winning the next 2 rounds

 

For t's :

T's move from there spawn must  buy NADE + SMOKE + FLASH be close together and nade / flash on ct at sites and clear the site then  plant  c4 . Hold the site till ct's rush into site to defuse c4 , then by hiding and taking cover pick them and ur guns for next round by leaving site while blast.

Basic things to know about cs 1.6

* cl_cmdrate - this should apparently be approximately equal to the FPS you're getting (check netgraph). Too much above or too much below and you'll get choke.

* cl_updaterate - you should set this as high as it will go without causing ANY packet loss - if you're getting any loss, that's BAD.

* rate - capped at 20000 for online play (25000 at LAN). Setting it too low will cause choke. Setting it too high will cause choke.

* ex_interp - the "ideal" is supposed to be 1/cl_updaterate. NEVER set this to zero because CS uses your current cl_updaterate, not the server's. Basically, the higher ex_interp, the smoother play will appear, but true player positions will be less accurate on your screen. Some people prefer to just set this low and leave it there. (0.01)

There will be 2 parts to this guide;
Part1- I will list the rates and will explain some of them
Part2- I will give you the optimum settings for best play
Part3- Will answer common questions

PART 1

ms- When you have net_graph 3 on you will be able your ms. Ms stands for millisecond. Ms is your delay from when you click the button to fire to when it actually does this. Your ping is what effects your ms. 0 is best but anything under 50 is really fine.

choke- Choke effects your shot registration. You always want 0 but a little is alright, nothing above 20. To check your choke net_graph 3.

loss- As with Choke you check it with net_graph 3. It also effects shot registration and you want it at 0. However you never want any loss as it makes a lot more of a difference.

rate- The # of packets of information you send to the server.

cl_cmdrate-This is the number of updates clients(you) send to the server and can contribute to choke.

cl_updaterate-This is a request value and a lot of the times not the actual # of updates received by the client from the server. The actual number is capped by the server side fps.

fps_max 101- Allows for 101 frames per second, anything higher is worthless as the eyes cant tell the difference and cs's max is 101 (inless using 3rd party program).

ex_interp- When playing counter-strike you may notice that when you shoot someone it does not kill them. This is partly due to the rates mentioned above and a lot to do with your ex_interp setting. The two choices for this setting are ex_interp .1 and ex_interp .01. When playing cs it may say you are getting 100 fps but you are really getting x amount of real frames and x amount of guessed frames. Putting your interp at .1 increases the amount of real frames you get and consequently reduces your amount of guessed frames. At .01 you guess more frames and shot registration is less accurate. However some people think that .01 is best for AWP since you shoot far less and sometimes the guess frame can hit the target when you really missed. Inless your running on a old computer i suggest using .1 especially for rifles.

PART 2

rate- 20,000, some say 25,000 but servers are maxed out at 20,000 so it does'nt matter.
cl_cmdrate- 101
cl_updaterate- 101
ex_interp- This is an opinion but i suggest .1(.1 is required at all lan tournaments also).

PART 3

Where do i enter the commands? You enter these commands in the console. To open your console press the ~ button. I am not sure but in source you have to activate it by going into options->advanced settings and check the box for enabling the console.

How come ex_interp is locked at .01? I am not exactly sure but i know .001 is considered to be hacking by VAC. If you own a server you can change the server.cfg file to allow .001 and more but its not advised.

I used your suggested rates but i have lots of choke and loss. The rates i provided are the best rates for most servers, however for some servers you will need to change them to lower your choke etc. Remember your goal is 0 choke/loss/ms.

How are you so cool? Some people are just born that way what can i say :smile:

Final Verdict: If you can have your rates as i suggest and get 0 loss/choke then use them, otherwise you can alter them to however you like!

-Scott Tschida

Recommendations for online play:

rate:
I’ve been assured that rate is capped at 20000. Using anything above 20000 has no benefit, and could potentially lower performance.

Recommendation:
rate 20000.

sv_maxrate:
This value will most likely be set to 0. I’ll explain why this might not be the optimal value for online play. sv_maxrate 0 will detect each clients’ rate setting and fulfill each players’ need. Assume for a second that the half-life engine did allow players to use a rate value of over 20000. If a player had rate set to an insanely high value (i.e. 999999999), the server would try to fulfill that need. This could potentially waste bandwidth and put more load on the server than needed. I suggest a safer, but equally well performing value of sv_maxrate 20000. In reality, sv_maxrate 0 and sv_maxrate 20000 may behave exactly the same, but added precautions never hurt.

Recommendation:
sv_maxrate 20000.

cl_cmdrate:
Ideally, this value should equal the server’s fps (NOT the client fps as some people originally thought). If you update the server more times than the server calculates frames over the same time period, the extra updates are most likely just dropped by the server. Therefore, too high of a cl_cmdrate shouldn’t be too harmful, but will waste your bandwidth.

Recommendation:
cl_cmdrate equal to or higher than the server’s fps.

ex_interp:
Set this variable to 0 and nothing else. Counter-Strike will automatically set your ex_interp to 1/cl_updaterate (i.e. your console will say: “ex_interp forced up to xx msec”). This is because the time in between each packet is exactly 1/(the # of updates per second), so this is how long you want your client to interpolate. Adjusting your cl_updaterate will automatically adjust your ex_interp (when ex_interp is set to 0). I recommend only changing your cl_updaterate, and letting Counter-Strike set your ex_interp. You cannot set this command lower than 1/cl_updaterate anymore, and setting it higher is an exploit. Using a value above 1/cl_updaterate forces you to shoot behind the actual model displayed on your screen, which should be considered an exploit. For example, if you use cl_updaterate 101, the correct value for ex_interp would be 1/101 = 0.009 (9 milliseconds), but by using the default value of ex_interp 0.1 with this high cl_updaterate, the aforementioned exploit appears.
Recommendation:

ex_interp 0.

cl_updaterate:
It has long been thought that the prescription for cl_updaterate was to start at 101 and work your way down until you receive and acceptable amount of “choke.” Choke can be viewed by using the command net_graph 3. Personally, choke is the last thing on my mind. The best value for cl_updaterate is much more complicated. The CAL server side config provides for an sv_maxupdaterate of 101, so one may conclude that your cl_updaterate should be set to 101. Ideally, this is correct, but in reality is not very useful. Most servers you will play on in North America won’t be able to calculate 100 frames per second; this means that there is no way the server can send out 100 updates per second. Therefore, a value of cl_updaterate 101 will tell your client to use ex_interp 0.009, but you won’t actually be receiving 100 updates per second, so the players will appear choppy. Since there is no way to determine a server’s fps without rcon (again use rcon stats), the optimum value is somewhat of a guessing game. You might say, “Well, just set cl_updaterate to 101 anyway and I’ll receive the maximum number of packets the server can send.” The problem here is the disregard of cl_updaterate’s effect on ex_interp and the delicate balance that must be maintained between them.
To find your optimum value of cl_updaterate (remember to set ex_interp to 0), start at 101 and work your way down until the models only slightly skip around. “Slightly skip around” is a matter of preference, as long as ex_interp equals 1/cl_updaterate, the models will be in the right place. You will need to readjust your cl_updaterate on a per-server basis. Don’t be afraid to use a value under 50, if necessary. The prediction engine will do its job. Note: most public servers will be using the default sv_maxupdaterate value of 30, so cl_updaterate 30 will work best in that situation.

Please note that starting from a low value of cl_updaterate (such as 20) and working your way up will not work. Once you increment cl_updaterate to a higher value, the ex_interp will not reset itself automatically; you will have to manually type ex_interp 0 again and again. Here is a convenient script I’ve written for adjusting cl_updaterate easily:

Update Rate Config File

Recommendation:
cl_updaterate should equal the server’s fps, and shouldn’t exceed the server’s sv_maxupdaterate value.

sys_ticrate:
Finding the optimum value for sys_ticrate involves some experimentation. First, recall that if your server is not boosted, raising this value above 100 will have absolutely no effect. If you happen to rent from a high performance server provider (read: your server is boosted), then you have some room to work. While generally more fps is a good thing, the effects of increasing sys_ticrate over about 200 (probably even lower) are almost non-existent. If you set sys_ticrate to 9999, your server’s fps may fluctuate between say 150-1000 depending on the complexity of the current situation. Setting sys_ticrate to a value under 200 would provide a more consistent environment with a minimal (if any) loss in performance. Also, every server host out there runs multiple instances of HLDS (Half-Life Dedicated Server) on one physical server (computer), so if every instance of HLDS is set on sys_ticrate 10000, the load on the CPU(s) could become too great. This type of situation could potentially degrade the playing experience for every server hosted on that computer (and raise your monthly rent).
Finally, server fps only works in multiples of certain numbers. For example, my server will only run at 85, 102, 128, 170, 256, etc. fps and not in-between. If you set sys_ticrate to 100, your server will run at the highest multiple that is under 100 (ex. 85), so try setting sys_ticrate 20-50 above your target fps.

Recommendation:
sys_ticrate 110-180, depending on the quality of your server.

Notes about LAN play:
The reason LAN organizations, such as the CPL, use cl_updaterate 101 has to do with the quality of servers they host. Usually on LAN, only a few servers will be running on any given box, so the servers use up fewer resources. If the servers are boosted to over 100fps, then cl_updaterate 101 becomes a realistic value. For a quick way to determine if a LAN server is boosted, look at the average ping of the players. A default server running at 50 or 64fps will yield pings above 15ms, while a boosted server will produce much lower pings, on the order of 5ms. To my knowledge, the CPL, ESWC and WCG all use boosted servers.