The player Swisher publicly asked the CS2 developers to fix a bug that, according to him, has been in the game for 750 days. The description is simple. A smoke grenade sits in a doorway or narrow passage. An HE grenade explodes right next to it. The screen stays gray. Step back a couple of paces and repeat the same move, and everything works as intended.
For beginners, a quick explanation: HE is a fragmentation grenade, and smoke in CS2 reacts to explosions, parting around them and briefly opening up visibility. This underlies familiar tactics: "punching through" smoke with a grenade to see who is standing behind it, or clearing a path before pushing out. If this mechanic breaks in a tight spot, a player counting on visibility is left with a gray screen at the most critical moment.
Why a small bug hits rounds hard
Narrow passages and doors on CS2 maps are exactly where smoke is thrown most often: controlling a lane, closing off an angle, cutting off vision before a push onto a site. That is precisely where the bug triggers. The player throws the grenade right up close because they are standing at the very edge of the doorway, which means they land in exactly the conditions under which the smoke does not react.
The danger is not the bug itself but the expectation. A round built on the idea that "I'll blow the smoke and see the target" turns into a blind push if the screen stays gray. The decision is made in advance, and the bug is exposed at the most expensive moment.
How to test it on a practice server
You can reproduce the situation in a few minutes on your own server with cheats enabled:
1. Place a smoke grenade in a narrow passage or doorway.
2. Stand right up close and detonate an HE right next to the smoke. Note whether visibility cleared.
3. Move back a few paces and repeat the same throw.
4. Compare the results and try different distances to find the threshold beyond which the mechanic works again.
This gives you not a rumor from chat but your own knowledge: from what distance, and in which doorways on your map, smoke behaves predictably.
Position: don't patch the bug with a habit, remove the dependency
In the community, bugs like this are usually discussed as a reason for outrage. We believe a different view is more useful for player preparation: the bug itself is uninteresting; what is interesting is the habit it exposes.
If a push is built on a grenade thrown right next to smoke in a doorway, it is a fragile plan. It is not only about this bug: any unstable mechanic behavior, whether an unexpected collision or server lag, breaks such a round. It is more reliable to separate the decisions. Smoke recon is better done from a distance where you have personally verified how the grenade behaves. And a grenade should be treated not as a guarantee of visibility but as one option that has a backup.
A sensible approach for a team: agree that in tight spots, visibility does not depend on a single throw. One player throws from a distance, another backs up with a separate method, and a third does not push out until they have information. That way the round survives this bug and any future one.
Until the developers respond, this remains a matter of preparation for each player. The check takes five minutes, and behind it stands a rule that is useful in any version of the game: the mechanic a round depends on must be known from your own experience, not from a belief that "this is how it should work."
