Counter-Strike 2 reworks Cache map

Counter-Strike 2 didn’t just bring Cache back and call it a day. Valve spent April 28, April 29, and April 30 shipping follow-up fixes that sand down the rough edges almost immediately. That matters because Cache is one of those maps players know by feel — if a corner clips weirdly, a shadow breaks, or a dropped bomb gets stuck, people notice fast. So the real story here isn’t “Cache exists again.” It’s that Valve is tuning the remake in public, patch by patch. ### What actually changed after Cache came back? Cache returned to CS2 on April 28 and went straight into Competitive, Casual, Deathmatch, and Retakes. Then Valve followed with two more updates: April 29 changed map geometry and visibility in several named spots, and April 30 focused on map-wide clipping, geometry polish, shadow fixes, surface sounds, and cases where the first release was the foundation, not the finished version. ### Why is Cache such a big deal? Cache is a classic three-lane Counter-Strike map, which sounds simple but is exactly why players care so much. The whole thing depends on clean lines, readable cover, and predictable movement. If a box gives too much vision, if a sign blocks a jump, or if footsteps sound wrong on a crate, that changes fights in ways. Valve leaned into that nostalgia in the launch note, basically saying veterans should feel at home right away. ### Which parts of the map got touched? The April 29 patch is where the named edits show up. Valve increased the bomb explosion radius, adjusted lighting around Vent, removed a lamp by squeaky, disabled player collision on a sign, reworked e-box on A for better visibility, lowered the Checkers entrance frame at B Main, moved pipes, removed an AC unit, and adjusted grenade paths. That’s not one bug fix — it’s a full pass on how the map reads and plays. ### What’s the non-map gameplay change? The big one is aimpunch. Valve capped it at 90 degrees in the April 30 update. In plain English, getting tagged won’t throw your view into absurd angles the way it sometimes could before. That doesn’t reinvent CS2’s meta, but it does make damage feedback more controlled and less chaotic in edge cases — especially in scrappy fights where visibility and recoil are already messy. ### What about animation and technical fixes? There are two buckets here. One is feel — Valve fixed hand popping while counter-strafing with a grenade equipped, after already doing minor viewmodel and knife-holding cleanup in the April 28 patch. The other is stability — the April 30 patch fixed a shader compilation fatal error affecting some older GPUs. That kind of error could prevent some players from finishing a match at all. ### Is Cache in the main competitive pool now? Not quite. Cache is live in standard core modes, but Valve’s own wording says “for now,” and the map has not been announced as part of Premier or Active Duty in these notes. So this is more like a live shakedown. Players get the remake, Valve gets real match data, and the map gets cleaned up before any bigger competitive commitment. ### Why patch it this fast? Because map remakes break in tiny ways that only thousands of players can expose. A dev team can test geometry, but live players will find the bomb spot that traps the objective, the angle that feels off, or the crate that sounds wrong underfoot. Cache is especially sensitive to that because so much of its identity lives in small details — the map can look perfect, but if the floor has one dead spot, everyone notices. ### Bottom line? Valve’s real move here was not just reviving Cache. It was reviving Cache and then immediately tightening the screws. That makes this a polish story, not a content-drop story — but for a map this beloved, polish is the whole point.