- Counter-Strike 2 update from September 10, 2026: Cache fixes, camera tools and demo chat changes
Valve shipped a Counter-Strike 2 update focused on three areas: Cache cleanup, map scripting tools, and demo privacy. For most players, the headline is simple: Cache got a few competitive fixes, and demos now hide chat more like CS:GO did. For mappers and custom HUD creators, though, this Counter-Strike 2 update has a lot more going on under the hood.
Counter-Strike 2 update tightens up Cache for competitive play
The map changes are all on Cache, and they target the kind of stuff players notice once a map settles into regular play: bad gaps, awkward spawn setup, and cheesy penetration angles.
Valve fixed various gaps in the map, which usually means those tiny visual or collision issues where you can spot slivers you probably should not see, or where utility behaves strangely. Those fixes rarely look flashy in patch notes, but they matter. A weird one-way pixel gap can change a round.
The more direct gameplay change is the removal of a wallbang spot on B site. That line alone will catch the eye of anyone grinding Cache. If a B-site spam angle gave defenders or attackers too much free damage through cover, cutting it out makes rounds cleaner and less gimmicky.
Spawn logic also got adjusted. Valve added a missing competitive CT spawn point and additional T spawn points. That sounds minor, but spawn distribution affects early round timing, who reaches a lane first, and how often the same opening setup repeats. On a map like Cache, where early map control around mid and B can snowball fast, spawn consistency matters more than people admit.
Scripting and custom HUD work got the bigger upgrade
The map scripting side is where this Counter-Strike 2 update gets more technical. Valve reworked CSPlayerCamera and renamed it to CustomPlayerCamera, which is a cleaner name and, honestly, a more accurate one.
Along with the rename, Valve added four functions:
- GetPlayer
- GetMode
- SetMode
- SetFollowConfig
At the same time, Valve deprecated:
- IsEnabled
- SetEnabled
- SetIsControllingAngles
That usually signals a cleanup pass rather than a simple feature drop. Valve is clearly pushing camera behavior toward a more structured setup, which should help creators building custom modes, observer tools, or scripted sequences. If you work with CS2 maps or custom experiences, this is probably the part you care about most.
HUD scripting also got several practical updates. Valve added an observable property to custom_hud_layout, which decides whether an observer sees the UI exactly as the spectated player sees it. The default is false. That gives creators more control over spectator presentation, especially in custom game modes or event setups where player HUD and observer HUD should not always match.
Valve also fixed several bugs tied to stale custom_hud_layout state when switching spectator targets. If you have ever seen UI elements hang around when they should have refreshed, you already know why this matters. Spectator bugs like that make custom presentations feel scuffed fast.
Two new top-level custom_hud_layout classes now react to client state:
- HUD_BUYMENU_VISIBLE
- HUD_SCOREBOARD_VISIBLE
That opens the door to cleaner HUD behavior without ugly workarounds. A custom layout can now respond directly when the buy menu or scoreboard appears, instead of faking state checks elsewhere.
One more detail: custom_hud_layout now always draws on top of the base HUD. For creators, that removes a common source of layering headaches. You can argue about taste later, but technically it is much easier to reason about.
Demo chat now follows stricter privacy rules
The last part of the Counter-Strike 2 update changes how chat is stored and shown in demo files. Valve now encrypts chat in demos using the same rules as CS:GO.
That means:
- Team chat is no longer readable during demo playback
- Global chat is only readable when the demo is played through the in-game watch UI
For regular players, this is mostly a privacy and anti-drama fix. Scrubbing through a demo file should not expose team comms through text that was never meant for everyone reviewing the match later. For tournament admins, demo reviewers, and content creators, the global chat limitation also draws a clearer line between what is visible in the official viewing flow and what is exposed in raw playback contexts.
It is not a flashy update. No rifle changes, no economy shake-up, no smoke behavior tweaks. But Valve cleaned up Cache, gave scripters better camera and HUD tools, and locked demo chat down in a more familiar way. That is a pretty standard maintenance patch, and for the people affected by each part, it is the kind that actually saves time.
Full changelog (Valve patch notes)
[ MAPS ] Cache
-
Fixed various gaps in map.
-
Fixed a wallbang spot on B site.
-
Added a missing competitive CT spawn point.
-
Added additional T spawn points. [ MAP SCRIPTING ]
-
Reworked CSPlayerCamera:
-
Renamed it to CustomPlayerCamera.
-
Added GetPlayer, GetMode, SetMode, and SetFollowConfig.
-
Deprecated IsEnabled, SetEnabled, and SetIsControllingAngles.
-
Added an 'observable' property to custom_hud_layout that controls whether an observer sees the UI as the spectated player sees it. Defaults to false.
-
Fixed several bugs related to stale custom_hud_layout state when changing spectator targets.
-
Added top-level custom_hud_layout classes driven by client state:
-
HUD_BUYMENU_VISIBLE
-
HUD_SCOREBOARD_VISIBLE
-
custom_hud_layout now always draws on top of the base HUD. [ MISC ]
-
Chat is now encrypted in demo files using the same rules as CS:GO :
-
Team chat is no longer readable when playing back demo files.
-
Global chat is only readable in demo files when played back via the in-game watch UI.
Polski
English
Українська
Deutsch
Español
Türkçe
Português (BR)
Français
Čeština