Key takeaways
- Cache in, Overpass out — confirmed in Valve's 8 July 2026 update notes.
- Your veto is wrong before your map knowledge is; fix that first.
- Cache got collision, gap and boost fixes on 3 August, so specific tricks have a short shelf life.
The map pool changed under you, and the first thing it broke is not your map knowledge. It is your veto. Everyone in your lobby now has one fewer map they are confident banning and one more they cannot honestly claim to know, and that uncertainty is decided in about fifteen seconds before anybody fires a shot.
What Valve actually changed#
In the 8 July 2026 update, alongside the start of Premier Season Five, Valve added Cache to the Active Duty map pool and removed Overpass from it. The same update carried the reworked C4 explosion damage and two new Armory collections, which is where most of the attention went.
Cache has not been left alone since. In the 3 August update, Valve listed four fixes to it: gaps in the map closed, collision corrected in various spots, flickering assets fixed, and a boost spot removed in Outside A. That last one is worth reading twice — a boost that existed on 2 August does not exist now.
Everything above is what the notes say. What follows is our reading of it.
Fix the veto before you fix the map#
A pool swap does not change your skill on nine maps. It changes the odds of which one you end up playing. If Overpass was a map you banned on sight, that ban is now free, and you will be spending it somewhere you have not thought about. If Overpass was a map you picked, you have lost a comfort pick and have not yet earned a replacement.
Decide now, away from the queue, which map absorbs the freed ban. The default answer for most players is: ban the map where you are least sure what the opening thirty seconds look like. That is usually not the map you dislike most. It is the one where you cannot describe your team's default setup without guessing.
Cache itself is the awkward case. Banning it is defensible while you do not know it, but it is also the map your opponents are least likely to know either, and that symmetry is temporary. It closes as everyone learns.
Learn the layout, not the tricks#
The 3 August fixes tell you something about where Cache is in its life cycle. Geometry that Valve is still adjusting is geometry you should not be building habits on. A boost, a pixel gap or an off-angle that depends on collision behaviour can be removed in a patch, and then you have spent your practice time on something that no longer exists — plus you carry a reflex to a position that is now nothing.
Layout does not move that way. Rotation timings, where the map is loud, which crossings are covered by one player and which need two, and what a default setup looks like when nobody has information yet — those are stable, and they are the parts that transfer when the map gets patched again.
What is worth practising now#
Spend the time on the things that are portable. Crosshair placement at the common angles you already cross. Utility that buys time rather than utility that requires a lineup you found this week. Knowing which of your team's buys are actually affordable, and which are the force buys that lose you two rounds instead of one.
Those habits pay on Cache, they paid on Overpass, and they will pay on whatever replaces the next map. Map-specific knowledge is worth having, but on a map still receiving fixes it depreciates faster than the fundamentals do.
What we are not claiming#
Valve has not published anything about which side Cache favours, what its round win rates look like, or how the reworked bomb damage behaves on it specifically. We are not going to invent those numbers. Site strength on a freshly added map is also the claim most likely to be wrong early and repeated anyway — treat confident statements about it, including ones you find elsewhere, as untested until a few months of play have been behind them.
Sources
Topics
- patch analysis
- map pool
Found something wrong or out of date? Tell us — we correct errors in place and label material changes. Read our editorial standards.




