CS 1.6 Kill Feed Delay and Not Showing – Causes and Fixes

Last updated: June 9, 2026

The cs 1.6 kill feed delay – where kill icons appear several seconds after the kill, or do not appear at all – is almost always caused by wrong interpolation settings, high ping, or FPS below the recommended threshold. The kill feed not showing in Counter-Strike 1.6 is a separate issue usually caused by a disabled HUD or a corrupted config. Both are fixable. This guide covers every real fix for Steam and Non-Steam.

Fix ex_interp – the main cause of cs 1.6 kill feed delay

ex_interp controls how much the client interpolates player positions between server updates. The default value is 0.1 – meaning the game displays everything with a 100ms delay. This is why you see kills register late, players appear behind walls slightly, and the kill feed in cs 1.6 shows up delayed. Setting it to 0.01 reduces interpolation to 10ms and makes kill registration and the kill feed feel much more responsive.

Open the console with ~ and type:

ex_interp 0.01

If the value keeps reverting to 0.1, it means your cl_updaterate is too low. ex_interp cannot go below 1 / cl_updaterate – if cl_updaterate is 10, the minimum possible ex_interp is 0.1. You need to fix your rates first (see below), then set ex_interp 0.01 again.

Add to your autoexec.cfg to make it permanent:

cl_updaterate 101
cl_cmdrate 101
ex_interp 0.01

Fix network rates – cl_updaterate and cl_cmdrate

Wrong rate settings directly cause kill feed delay in Counter-Strike 1.6. Low cl_updaterate means you receive fewer updates from the server per second – kills register late, kill icons appear delayed, and player positions are inaccurate.

Standard competitive settings that fix most cs 1.6 kill feed issues:

rate 25000
cl_cmdrate 101
cl_updaterate 101
ex_interp 0.01
fps_max 101

Add all of these to your autoexec.cfg. Note: on some servers, cl_updaterate is capped by the server’s sv_maxupdaterate setting. If you see choke in net_graph 1 – yellow or orange dots – lower cl_updaterate to 80 or 60 until choke disappears.

Fix FPS – kill feed delay at low frame rates

Below 30 FPS, the GoldSrc engine starts skipping HUD updates including the cs 1.6 kill feed. At very low frame rates, kill icons either appear with a significant delay or not at all. Set a stable FPS target:

fps_max 101

Check your current FPS with net_graph 1 in console. If your FPS is consistently below 60, optimize your graphics settings – lower resolution, switch to OpenGL renderer, reduce mp_decals to 0. A stable 100 FPS eliminates kill feed timing issues entirely.

Kill feed not showing at all – HUD fix

If the kill feed is completely missing in cs 1.6 – no icons appear at all when players die – the HUD is disabled or a specific HUD setting is off.

Open console and check:

hud_draw 1
hud_deathnotice_time 3

hud_draw 0 hides the entire HUD including the kill feed. hud_deathnotice_time controls how long kill icons stay on screen – if set to 0 they disappear instantly. The default value is 3 seconds. Add both to autoexec.cfg to make them permanent.

Also check that your config does not contain con_color or custom HUD scripts that override these values.

High ping causing kill feed delay

If your ping to the server is above 100ms, the cs 1.6 kill feed will always appear with a delay equal to roughly your ping. There is no client-side fix for this – the kill event is sent from the server to your client and the delay is the round-trip time. Solutions:

• Connect to servers geographically closer to you
• Switch from Wi-Fi to a wired Ethernet connection
• Close background applications consuming bandwidth – check with net_graph 1 for packet loss
• Check for packet loss – even 1-2% packet loss causes visible kill feed delay in Counter-Strike 1.6

Server-side kill feed delay

If the kill feed delay in cs 1.6 only happens on one specific server but not others, the server itself is the cause. Some AMX Mod X plugins modify kill feed behavior – custom kill feed plugins, HUD modifiers, or poorly configured death notice settings on the server side.

As a player you cannot fix this – it is a server configuration issue. Switch to a different server or contact the server admin. If you are the server owner, check your active AMXX plugins for any that modify hud_deathnotice_time or the kill feed display.

Kill feed settings keep reverting – config file fix

If you fix ex_interp or hud_deathnotice_time in console but they revert to wrong values every time you reconnect or restart, your config.cfg or userconfig.cfg contains hardcoded values that override whatever you set manually.

1. Navigate to your cstrike/ folder
2. Open config.cfg in Notepad
3. Search for ex_interp – if you see ex_interp "0.1", change it to ex_interp "0.01"
4. Search for hud_deathnotice_time – if set to 0, change to 3
5. Do the same in userconfig.cfg if it exists
6. Save and restart the game

The safest approach is to add the correct values to autoexec.cfg – this file executes last and overrides everything else in config.cfg:

ex_interp 0.01
hud_draw 1
hud_deathnotice_time 3
cl_updaterate 101
cl_cmdrate 101
rate 25000
fps_max 101

If you need a clean Counter-Strike 1.6 client with correct default settings, download Counter-Strike 1.6 from our portal.