Why Are CS2 Bots Not Moving?
In most cases, frozen bots in CS2 aren't the result of a game-breaking bug, but rather an intentional feature triggered by practice configurations. When you load up custom warm-up scripts or offline servers, console commands like bot_stop 1 or bot_zombie 1 are often enabled by default. These settings are designed to give you stationary targets so you can practice spray transfers, line up smoke grenades, or test weapon damage without the AI shooting back.
However, if these commands linger in your autoexec file or you forget to toggle them off, your bots will remain completely paralyzed at spawn. Occasionally, the issue can also happen on brand-new workshop maps that lack a generated navigation mesh (nav mesh) — the invisible pathing system that tells the AI where it can and cannot walk.
How to Fix Bots Not Moving in CS2
Getting your bots moving again is a quick fix that happens entirely inside the CS2 developer console. Depending on why they are stuck, you'll need to clear out residual practice commands or generate a new pathing file for the map.
Here is the exact troubleshooting process to get them running again:
Open the Developer Console
Before you can enter any commands, make sure the console is actually enabled. Go to Settings > Game and set Enable Developer Console (~) to Yes. Press the tilde (~) key during your match to open the command window.
Disable Bot Restrictions:
Type the following commands into the console one by one, pressing Enter after each. This overrides any practice scripts that are freezing the AI:
bot_stop 0 (Restores normal movement and behavior)
bot_zombie 0 (Ensures bots will aggressively react to and shoot at you)
bot_mimic 0 (Stops bots from simply mirroring your keyboard inputs
Generate a Navigation Mesh
If the commands above didn't work and you are playing on a custom community map, the bots might be stuck because the map lacks a pathing file. Type sv_cheats 1 and press Enter, then type nav_generate and press Enter. Your game will freeze for a few seconds while it calculates the walkable surfaces, then the server will restart with fully functioning bots.
If you still don’t know how to open the developer console, check out our special guide.
CS2 Bots Not Moving Commands Explained
While simply typing bot_stop 0 is usually enough to unfreeze your lobby, understanding the specific commands that control bot AI can drastically improve your offline practice sessions. Valve provides several distinct console commands to manipulate how bots behave, allowing you to tailor them for specific training scenarios—whether you are practicing wide swings, testing flashbangs, or warming up your crosshair tracking.
Here is a breakdown of the commands that affect bot movement and what they actually do:
bot_stop <1/0>: This is the master switch for bot movement. Setting it to 1 instantly freezes all bots exactly where they are standing. They will not walk, turn, or shoot. Setting it to 0 restores their default AI logic.
bot_zombie <1/0>: When set to 1, bots will run around the map normally but completely ignore your presence. They won't shoot back or try to take cover, making them excellent moving targets for aim tracking. Set it to 0 to make them hostile again.
bot_mimic <1/0>: Setting this to 1 forces the bots to mirror your exact keyboard and mouse inputs. This is incredibly useful for placing a bot at a chokepoint and testing how your character model looks to an enemy when you jiggle-peek an angle.
bot_crouch <1/0>: Setting this to 1 forces all bots to crouch indefinitely, whether they are frozen or moving. This is perfect for practicing headshot angles against players holding tight, crouched angles.
How to Enable Bot Movement in Practice Mode
If you are using CS2's built-in Practice Mode from the main menu, bot behavior is heavily influenced by the lobby settings you toggle before loading in, as well as any custom .cfg files you run. Many players execute a dedicated practice config (like typing exec prac in the console) to enable infinite ammo and grenade trajectories, which almost universally includes the bot_stop 1 command to set up static grenade lineups.
To enable bot movement while keeping your other practice settings active, simply open your console after the map loads and input bot_stop 0. If you want the bots to run around the map so you can practice tracking without the annoyance of them shooting back, be sure to pair it with bot_zombie 1.
CS2 Add Bot but Bot Won't Move
Sometimes you might successfully spawn a new enemy into the lobby using bot_add_t or bot_add_ct, only to find that the new arrival is just as paralyzed as the rest of the team. This happens because AI behavioral commands in CS2 apply globally to the entire server, rather than to individual bots. If a practice config or a previous console entry set the server to bot_stop 1, any new bot that joins the match will automatically inherit that frozen state the moment they spawn.
To fix this, you don't need to kick and re-add the bots; simply type bot_stop 0 into the console to wake up the entire lobby. Additionally, if you used the bot_place command to teleport a bot directly to your crosshair, they may occasionally get stuck inside map geometry. If they are twitching but unable to walk, try placing them again in a slightly more open space to free them.
CS2 Competitive Bots Not Moving
In CS2, console commands often persist until the game is fully restarted. If you were recently practicing grenade lineups with bot_stop 1 enabled and then switched directly to an offline Competitive match, that command will still be active. Similarly, if you have an autoexec.cfg file that automatically forces bots to halt upon launching the game, they will remain paralyzed at the start of every local lobby, regardless of the game mode. Finally, if you are running a community workshop map in Competitive mode, the bots might be stuck simply because the map is missing its navigation mesh. A quick bot_stop 0 or a nav_generate command will immediately get your simulated 5v5 match back on track.
CS2 Wingman Bots Not Moving
Playing an offline Wingman match presents a unique set of challenges for bot AI, primarily due to the restricted 2v2 map layouts. While residual commands like bot_stop 1 carrying over from your autoexec or a previous practice session will freeze them just like in other modes, Wingman introduces pathing complications. Official Wingman maps use invisible walls and blockades to cut standard defusal maps down to a single bombsite. If the server's navigation mesh hasn't updated properly to account for these artificial boundaries, which frequently happens on community workshop maps or custom server configs, the bots will become confused by the blocked paths, resulting in them either hugging invisible walls endlessly or freezing completely at spawn.
To fix this, first ensure bot_stop 0 is active. If they remain stuck against the Wingman barriers, enable sv_cheats 1 and run nav_generate to force the game to recalculate the walkable pathways specifically for the 2v2 layout.
CS2 Server Bots Not Moving
Furthermore, if you are hosting a custom workshop map, the bots may fail to move simply because the server lacks a calculated navigation mesh (nav mesh) for that specific map geometry. Server operators can resolve pathing failures by enabling sv_cheats 1 and running nav_generate to build the invisible walkways the AI needs to navigate. To prevent these issues from recurring on map changes, ensure your server's base configuration explicitly executes bot_stop 0 and that parameters like mp_limitteams aren't restricting the bots from fully spawning in.
댓글 작성