The latest CS2 update brought not only technical fixes into the game, but also a new problem that very quickly turned into one of the community’s main topics. After the patch, burst weapons started behaving abnormally, and now the FAMAS and Glock in their respective modes fire as if the entire burst is released almost at the same time.
Burst fire stopped looking normal after the patch
The core of the problem is simple: in burst-fire mode, the weapon no longer feels like a classic controlled burst with a short internal delay between bullets. According to player observations, the FAMAS now fires all three bullets almost in a single instant. The same applies to the Glock, which in this state has already jokingly started being called a “pocket shotgun.”
And that is exactly what makes the situation so loud. Bugs like this do not hide somewhere in rare scenarios or complicated mechanical interactions. They are very easy to feel literally in the very first rounds, which means the problem immediately affects Premier, standard matchmaking, and the general perception of the update as a whole.
Why this bug looks so dangerous
The problem is not only that the weapon fires “strangely.” The problem is that this kind of burst fire sharply changes the entire combat logic. If three bullets are released with almost no delay, the weapon temporarily gets a completely different power profile: at close range or medium distance, this can turn the FAMAS and Glock into a much more dangerous tool than they were supposed to be in a normal balance model.
That is exactly why this bug feels not like a funny little issue, but like a real break in the match environment. When one button effectively compresses a burst into an almost instant volley, the game at certain ranges starts behaving in a way nobody is used to anymore — from ordinary players to people who read timings and damage output very sensitively.
The irony is that Valve had just already fixed burst fire
The most interesting part here is the context of the update itself. Valve had already recently released a patch that restored the delay between bullets in burst fire, removing a bug related to this mechanic. And now the scene has once again found itself at a point where burst fire itself looks broken again.
That makes the story even louder. Because the community sees not just another random issue, but a problem in the exact same area that had already been targeted for repair. And that means, in the eyes of players, this automatically becomes a symbol of an unsuccessful update: not simply “something broke somewhere,” but “Valve touched a mechanic again that still had not become stable.”
The community sees it as a bug, but is using it to the fullest for now
Player reactions to things like this are always predictable: first shock, then memes, then quick adaptation. And that is exactly the second-to-third phase CS2 is currently in. People are already openly calling this one of the most broken updates in a long time, but at the same time they are not hiding that, until it gets fixed, they are having fun using this anomaly in Premier.
And that is very typical for Counter-Strike. The community almost never waits for a problem to be “properly” assessed from above. If a mechanic gives an advantage here and now, people start testing it, abusing it, and spreading it through clips within the first few hours after the patch.
This does not look like a new feature — it looks like an urgent fix candidate
That is exactly why the main question in the headline — “bug or feature?” — already has an answer in essence. The current behavior of burst fire deviates far too clearly from the normal logic of the game to be perceived as an intentional balance change. This is not a new firing style, not a hidden weapon rework, and not a reinterpretation of the FAMAS or Glock. It looks exactly like a broken mechanic that will most likely have to be rolled back or fixed very quickly.
And the longer this state remains in the live version, the more it will damage trust in the update itself. Because players are willing to laugh at moments like this for a few hours, but they are not willing to live for long in an environment where burst fire effectively turns into a different weapon.
read more
The update has once again hit one of the most sensitive areas of the game
The latest CS2 update has once again hit a very sensitive mechanic — burst fire. After the patch, the FAMAS and Glock in burst mode began firing almost like an instant volley, and this already looks not like a funny side effect, but like a serious break in balance.
Until Valve release a fix, the situation will live in two modes at once: for some, it is temporary chaos and a meme; for others, it is yet another reminder that even small technical fixes in CS2 can still suddenly affect the very foundation of gunplay.
