Fix Counter-Strike 1.6 Can’t Move After Planting Bomb

Last updated: May 16, 2026

Getting stuck after planting the bomb in CS 1.6 – where your character freezes in place for 1-3 seconds after the C4 plant animation completes – is caused by a client-server synchronization issue tied to FPS, weapon prediction settings, or server-side freeze time configuration. This guide covers every fix for CS 1.6 can’t move after planting bomb and counter-strike 1.6 bomb plant freeze.

Jump to your problem:

• FPS causing freeze after bomb plant
• Weapon prediction settings
• Server freeze time setting
• Config conflict freezing movement

FPS fix – most common cause of freezing after bomb plant

The most common cause of CS 1.6 frozen after C4 plant is unstable or uncapped FPS. The GoldSrc engine ties several animations and state transitions to frame rate. When FPS spikes or drops during the bomb plant animation, the engine can desync the player’s movement state from the server’s expected state, causing a brief freeze.

fps_max 100
fps_modem 0

Set fps_max 100 for stable frame timing that matches the standard server tick rate. Uncapped FPS or very high FPS values (300+) can cause this freeze more frequently. On Non-Steam, type developer 1 first if fps_max does not take effect above 100.

Weapon prediction settings

Client-side weapon prediction controls how movement and weapon states are handled locally before server confirmation arrives. With incorrect prediction settings the bomb plant state transition can leave the client in a frozen input state until the server sends a correction.

cl_predict 1
cl_predictweapons 1
cl_lw 1
cl_lc 1

All four must be set to 1. If any of these are 0, the client waits for server confirmation at state transitions such as bomb plant completion, causing the freeze. Add to cstrike/userconfig.cfg.

Server freeze time causing movement block

Some servers set mp_freezetime to a non-zero value between rounds but occasionally a plugin or server configuration error applies freeze time incorrectly at bomb plant moments. If you are stuck after planting CS 1.6 only on specific servers and not others, this is the cause.

Test: join an offline game with map de_dust2 in console and plant the bomb. If you can move normally offline but freeze only on specific servers, the issue is server-side and cannot be fixed from the client.

If you are a server owner, check your server.cfg and any running AMXX plugins that modify mp_freezetime or player movement states. Standard value is:

mp_freezetime 6

Config conflict freezing movement after bomb plant

A downloaded config or script may contain a bind or alias that blocks movement input during specific game states. Check if your config contains any of the following that could interfere:

• Aliases bound to the bomb plant key (default G or mouse key) that block movement
• -forward, -back, -moveleft, -moveright commands left in an incorrect state
• Scripts that hold movement keys during weapon animations

To test if a config is causing the issue, open console and type unbindall followed by exec config.cfg to reset all binds to default, then try planting the bomb again. If the freeze disappears, the problem is in your userconfig.cfg or autoexec.cfg – open those files in Notepad and look for aliases or scripts related to weapon keys.

Complete fix config for CS 1.6 bomb plant freeze

fps_max 100
fps_modem 0
cl_predict 1
cl_predictweapons 1
cl_lw 1
cl_lc 1
rate 25000
cl_cmdrate 101
cl_updaterate 101

Add to cstrike/userconfig.cfg. If the freeze persists after all client fixes, the problem is server-side. If you need a clean CS 1.6 installation, download Counter-Strike 1.6 from our site.