I have played Counter-Strike since it was a Half-Life mod, and I have played every version since. From Source through CS2, it became an addiction. I kept coming back even when I knew the next match would probably piss me off.
CS2 finally annoyed me enough that I made a serious effort to stop. That took about a year, maybe more. I still play occasionally, but nothing like I used to.
I called CS:GO a good game with problems. CS2 is a shitpile of what CS:GO was. The shooting feels less dependable to me, suspicious matches have become exhausting, and Valve replaced the game I preferred rather than letting the new one stand beside it.
My CS2 gameplay
Watch my Counter-Strike 2 gameplay playlist directly on YouTube.
Valve replaced the game and kept its history
Valve announced CS2 on 22 March 2023 as a free upgrade, then released it on 27 September 2023. CS:GO’s supported live version was replaced inside the same Steam application, app 730. My library entry became Counter-Strike 2.
The Steam page still displays 21 August 2012 as its release date. That is CS:GO’s date. The review history includes reviews written for GO, and time spent in GO remains attached to the application now called CS2. Steam does identify reviews written before the change as reviews of CS:GO, but they still sit under CS2’s name.
Think about doing that outside a game. I have a girlfriend, then get a new girlfriend. I go through the photographs, take the old girlfriend out and put the new one in. I keep the posts and the history, but now everything points to the new girlfriend as though she had been there the whole time. Even an old post mentioning the previous girlfriend leads people back to the information about the new one.
If somebody did that, I would not touch it with a ten-foot pole. It would be fucking creepy. Put the same sort of substitution into a game library, though, and suddenly people defend it as a normal update.
I think Valve wanted all the hype, attention and people around CS:GO to go straight into CS2. It could inherit the audience and the public history immediately, instead of having to attract people to a separate release. That is the explanation that fits the decision for me.
In its October 2023 interview with PC Gamer, Valve said GO’s ageing technology was limiting development and that rewriting it in Source 2 would make longer-term support possible. The team also said so much had changed that it could no longer regard CS2 as the same game. Replacement and inventory continuity had been planned from early in development.
For the timing of the switch, Valve pointed to the shrinking, self-selecting Limited Test audience. It argued that making progress on networking, performance and core gameplay required “everyone playing the same game.” That put the people who wanted to carry on playing GO into the live development process for its replacement.
Players disagreed about that choice from the start. In a September 2023 Steam discussion, some defended keeping one community and one item economy, while others wanted separate games. ropz supported pushing the transition forward, although he also said the launch version was not ready for competition. Wanting everyone to move over was a position people could support. I wanted the choice to stay.
The legacy version does not undo the replacement
GO survived in a frozen legacy build, without official matchmaking. Support for that build ended on 1 January 2024. Players on macOS and older unsupported systems also lost access to the supported successor; Valve later admitted that it should have communicated the requirements earlier.
In March 2026, a separate, unlisted CS:GO Steam application made that older build easier to obtain. Valve described the change as easier access to the existing legacy version. It did not bring back official GO matchmaking or the old supported service. The new application also starts separately from the years of history left attached to app 730.
What I wanted was CS:GO continuing as a game I could choose to play. A frozen client, made easier to download years later, is a much smaller thing.
Even some of my headshots feel wrong
The strangest part of my shooting complaint is that it includes kills I got. On Dust II, I jumped from catwalk down towards CT spawn, fired and got a one-shot headshot. The other player appeared near the edge of my screen, nowhere near where I thought I was aiming.
Another time, I peeked B site from upper dark, the upper tunnels. I saw somebody behind a box, fired once and moved back behind the wall. The headshot seemed to register after I was already back in cover. It felt as though the bullet had travelled in slow motion.
I got the kills, so this is hardly a complaint that the game refused to let me win. I want the shot and the result to make sense together. Getting a headshot I cannot connect to what I saw is annoying too.
Official matches use dedicated, server-authoritative game servers. My computer predicts actions and displays the fight, while the server decides the accepted result and sends information back. Subtick records when an input happened within a server update interval. It still takes time for commands, results and the screen to catch up with one another.
Valve advertised that system with “What you see is what you get”. My experience has too often been a result arriving in a way that makes what I just saw difficult to understand.
The fixes show several different problems behind that feeling. In October 2023, Valve corrected hitbox-alignment issues. Its November 2023 updates addressed lost shooting commands under poor network conditions, misleading firing effects and the timing of shot feedback. The same period brought client/server shot-spread synchronisation changes.
On 6 February 2024, Valve said it had reduced steady-state peeker’s advantage by 16 milliseconds and dealt with cases where a command queue could make it worse. That is a concrete timing change in the fights players were having.
Later, damage prediction allowed the client to show certain hit feedback before server confirmation, with Valve acknowledging that the prediction could be wrong. A fast visual response and a confirmed server result are separate stages of the exchange.
I play on Linux and have fibre internet. Stutters, frame drops and moments where somebody seems to kill me before I have properly seen the fight still get on my nerves. A fast connection does not remove every timing problem: packet jitter, frame pacing and delayed feedback can all affect the experience.
Valve’s Source 2 telemetry guidance explains the buffering trade-off: extra buffering can absorb irregular packet arrivals, but adds delay. The latest 14 October 2026 patch still includes Vulkan stability improvements. These systems have continued changing long after release.
Tapping, small bursts and that bloody AK
Tapping and short bursts feel far too unreliable to me in CS2. I try to place a shot, or fire a small burst, and it feels more random than it used to. Too often I feel better off spraying and praying.
I already hated the AK before. Now there are times when I would rather try to kill the other player with a Glock. That is how bad aiming with it can feel to me.
Recoil, spread, movement inaccuracy and recovery between shots all affect where bullets go. A short burst still needs time to recover, and a crosshair sitting over somebody is not a guarantee that a moving or recently fired weapon will put its next bullet in the centre. The camera’s movement adds another part to what I am trying to read.
That last part became especially obvious in Valve’s 21 April 2026 update. It adjusted recoil-camera motion to resemble GO more closely while saying bullet trajectories should continue to match CS2. It also changed the visible camera response to being shot so players would receive the full aim-punch motion regardless of latency; the server was already applying the trajectory effect immediately.
The September 2026 crosshair changes needed a follow-up fix to the visualisation of weapon inaccuracy and spread, too.
Brighter maps and different smokes
Some CS2 maps look too bright and clean to me. The lighting has changed the mood, and I find the bright effect around the start of a round irritating. I preferred the look of GO in a lot of places.
The new smoke system also changes something players had spent years learning. Smoke fills space and responds to the environment; bullets and HE explosions can open it up. That changes the usefulness of a lineup, the timing of a peek and what can be seen through a gap.
In GO, I knew smokes through their lineups, fades, gaps and timings. A technically more advanced smoke does not automatically make me prefer playing around it. I have to learn a different set of behaviours in the game that replaced the one I already knew.
Deathmatch also feels worse to me. I miss the older team-based structure and would rather use that for practice than the version CS2 gives me. Add the frustration of fast, run-and-gun SMG fights to the shooting issues and it becomes another mode I enjoy less.
Expecting a cheater before the match has started
Cheating and smurfing feel so bad now that I can go into a match already expecting trouble. An opponent peeks, I die, and the immediate thought is that they are cheating. That expectation was already there in GO, and CS2 has done nothing to get it out of my head.
The annoying part is that I know the explanation can also be the server, the game or me. Somebody can simply be better. A much stronger player on another account can ruin the balance of the match without using a cheat. When I am already struggling to read the shooting, it gets harder to tell which problem I am looking at.
We have become used to the idea that hackers are everywhere. Then a strange death comes along and fits what we expected. I do it too. I would like to get back to being able to recognise a good shot without first wondering what the fuck happened.
Prime matches Prime players with other Prime players, but that has not made matches feel protected to me. Valve has worked on anti-cheat: April 2024 brought Overwatch for trusted partners, and limited testing of VACNet 3.0 began that August.
I preferred GO’s ranks
I liked the distinct rank badges in GO. The way rating and progression are presented in CS2 feels much more same-looking to me. Changing a label or number does not give me the same feeling as those old badges.
CS2 also splits progression across different systems. Premier has a numerical CS Rating; Competitive uses map-specific Skill Groups, while profile XP levels track a separate kind of progress.
| System | What it represents |
|---|---|
| Premier CS Rating | A numerical rating used for Premier and its leaderboards. |
| Competitive Skill Groups | Separate competitive ranks for individual maps. |
| Profile XP level | Account progression from earned XP, separate from competitive skill. |
The underlying ranks have changed as well. Valve overhauled per-map Skill Groups in June 2024, then expired and recalibrated them again in January 2026. The interface can show a rank, but the match still has to feel reasonably matched. Too often mine do not.
Three years of changing the replacement
CS2 launched without all of GO’s modes and content ready. Players had to wait for parts of the older game to return after it had already been replaced.
Arms Race returned in February 2024, Train in November 2024, and Retakes in October 2025. Cache returned in April 2026 for Casual, Competitive, Deathmatch and Retakes. Those returns happened over years.
There have also been new gameplay changes. March 2026 changed reloading: replacing a magazine now discards its remaining ammunition and takes a fresh magazine from the reserves. Limited map guides became available during the first five rounds of a half in Competitive and Retakes.
September’s Rush update added a queued 3v3 mode built around successive small arenas. Premier also changed from banning down to a single map to picking four candidates and randomly selecting one. Holding reload now gives a slower, silent reload, and unscoping is silent.
That is a lot of change to follow when I only play now and then. I wanted a dependable Counter-Strike that I enjoyed playing. I did not want to keep checking which part had returned, which rule had changed and which bit of feedback had been fixed this time.
I stopped caring about skins
I sell the drops I get. I do not care about building up a skin collection anymore, and selling a drop is a lot more appealing to me than paying to open it.
The Armory arrived in October 2024 with paid passes, credits earned through XP, collections and weapon charms. More ways to earn items through playing, once I had paid for the pass. Even detaching charms has its own consumable system.
I went through my account history because I wanted to compare what went out with everything that came back from selling loot, cards, packs and other items.
Across the recorded history through 5 August 2026, Community Market purchases plus Counter-Strike in-game purchases exceeded all Community Market credits by €1,933.25 (approximately US$2,175.49 / £1,631.37). That comparison covers the wider Steam market and both Counter-Strike eras, with unsold inventory unvalued. It even gives the sales side credit for cards and items from other games.
CS2-era in-game purchases alone came to €140.20 (approximately US$157.77 / £118.31). The longer breakdown is in my CS:GO review.
Somebody showing an expensive drop does not tell me what they have earned overall. I want to know what they paid to get there, what earlier openings cost and what they actually received when they sold. In my own history, counting the sales still left more going out.
The useful thing for me now is selling what drops for free and using the credit on something else. Steam Wallet credit stays inside Steam; it is not money I have withdrawn to my bank account.
Approximate currency equivalents use the ECB reference rates for 16 October 2026: €1 = US$1.1253 / £0.84385. The euro totals are the recorded amounts.
And now there are pets
They have added pets. Really. I got an egg and have not been back in to see what came out of it. I think it is stupid, and I have no interest in looking after a Counter-Strike chicken.
The egg can appear among the weekly rewards, taking both drop selections, and the system lets players hatch and care for a chick. Valve’s October updates already refer to its pet photobook. There is now another thing to come back and check on in Counter-Strike.
I am still annoyed with the shooting and the matches. I open the game and there is an egg. That says plenty about how far CS2 has gone from what I wanted to play.
The one good thing it did for me
CS2 pissed me off enough that I really worked at getting out of the addiction. It was hard. I would say it took a year, maybe longer, before I reached the point I am at now.
These days I play once or twice a month, and some months I do not play at all. I think I could count last year’s CS2 sessions on one hand, although I was also away on trips a lot that year.
I still play sometimes. I am more or less out of the habit, rather than completely finished with the game. Compared with how I played from Source onwards, that is a big difference.
I would take CS:GO back. The only positive I can give CS2 from my own experience is that it finally made me try hard enough to stop playing Counter-Strike all the time.
Related gameplay and image credits
My CS:GO gameplay playlist accompanies the earlier game and review.
Dust II comparison images and the smoke and Premier demonstration frames: © Valve, CS2 introduction. Pet-chick screenshot: Valve, via the linked PC Gamer report.