Valve’s decision to bring Anubis back and remove Train from the Active Duty pool sparked an immediate backlash. The Counter-Strike 2 community reacted fast and emotionally. Expectations for Cache were extremely high. Because of that, any other option felt like a step backward. This was especially true for a map that had only recently left the pool.
“WHERE IS CACHE?” — the community’s main outcry
Most reactions focused on one thing: Cache was missing. After Valve bought the remade version from FMPONE, many expected its return. For most fans, it felt inevitable. That is why the Anubis announcement frustrated so many people. The community saw it as Valve ignoring clear expectations.
ren: WHERE THE F*** IS CACHE
read more
Train: a premature farewell
Train’s removal divided opinions. Some fans believe Valve removed the map too early. They also argue that it never received serious improvements. Others reacted with irony or open relief. For them, Train never worked well in modern CS2.
Graham Pitt: Removing the map you barely added 12 months ago with no significant changes to improve it — ??
Anubis: no changes, no update
Anubis returning already surprised many players. The lack of visible updates made things worse. After six months outside the pool, players expected changes. Instead, they saw the same version return. A sarcastic reply from the official CS2 account only increased frustration.
CS2: The answer is either ‘yes’ or ‘no’.
Timing — another major issue
The timing of the announcement caused further criticism. Pro players and analysts questioned the decision. Valve revealed the change right before the new season. Teams had already started preparing. As a result, the update created confusion and extra pressure.
dust: Why are you waiting so late to announce this just before events are about to start?
Players and analysts react: mixed views and timing criticism
Reactions from pro players and analysts were more measured than the broader community backlash, but still largely critical. Most agreed that Anubis itself is not the core issue. Instead, concerns focused on the timing of the change, the absence of Cache, and the short lifespan of Train in the pool. Analyst Thorin suggested that Cache is still part of Valve’s plans, but that the developer is taking a cautious approach before reintroducing it to Active Duty:
Thorin: Cache is coming, but it will stay in Competitive for a few months before returning to the Active Duty map pool.
Former in-game leader cadiaN supported seasonal rotations, but criticized the timing of the announcement:
cadiaN: I enjoy the rhythm of changing one map per season, however let’s make it a thing that you announce it at the end of each Major cycle.
Analyst Mauisnake pointed out that Train was only beginning to show promise at the top level, while Anubis could benefit from recent gameplay changes:
Mauisnake: Train was just getting interesting in the pro scene… Anubis coming back is a welcome sight with the CT economy buff.
Veteran analyst Kasper Straube Hansen echoed the criticism around timing and preparation:
Kasper Straube Hansen: Changes to the active map pool should always occur right after a Major, in my opinion.
Former pro and analyst Pimp offered a more balanced take, welcoming Anubis while expressing disappointment over Train’s unfinished potential:
Pimp: I’ve always liked Anubis more than most people. Train has so much potential, but it felt like it only reached about 80% of it.
Broadcast talent James Banks summed up the emotional side of the reaction, while still looking ahead to Cache:
James Banks: Removing Train makes me sad. Anubis needed changes, and hopefully Cache will be ready next season.
Among active professionals, opinions were similarly split. b1t accepted Anubis’ return, but questioned the logic behind removing Train:
b1t: It’s okay that Anubis is back, but removing Train doesn’t make much sense to me.
read more
What went wrong
Replacing Train with Anubis became one of the most controversial map rotations in recent years. Fans expected Cache. Valve delivered Anubis without updates. The late announcement added fuel to the fire. What should have been a routine change turned into a major community backlash.
CS2 Community: WHERE IS CACHE????
