Valve Improves Cache and Updates Demo Chat in CS2

Valve released a Counter-Strike 2 update on September 10, 2026. The main changes affected Cache, tools for map creators, and how chat messages are handled in demo files.

On Cache, the developers fixed several technical issues and adjusted player spawn points. A separate part of the update focused on map scripting, custom HUD functionality, and camera systems for spectators.

Cache

The following changes were made to the map:

• fixed various holes in the map;

• removed a wallbang spot on the B site;

• added a missing CT spawn point in Competitive mode;

• added additional T spawn points.

Map Scripting

Valve also reworked several tools available to custom map creators.

The changes include:

• CSPlayerCamera was renamed to CustomPlayerCamera;

• added the GetPlayer, GetMode, SetMode, and SetFollowConfig methods;

• IsEnabled, SetEnabled, and SetIsControllingAngles were deprecated;

• added the observable property to custom_hud_layout;

• observable determines whether a spectator sees the interface in the same way as the player they are following;

• observable is set to false by default;

• fixed issues where an old custom_hud_layout state could remain active after switching the observed player;

• added client-controlled HUD_BUYMENU_VISIBLE and HUD_SCOREBOARD_VISIBLE classes;

• custom_hud_layout is now always displayed above the standard HUD.

Miscellaneous

The update also changed how chat is recorded and played back in demo files.

• demo chat is now recorded in encrypted form, similar to how it worked in CS:GO;

• team chat can no longer be read during demo playback;

• global chat is available only when watching demos through the in-game interface.

The September 10 update was primarily technical. Valve fixed several issues on Cache, expanded the tools available to custom map developers, and changed how chat messages are stored and displayed in demo files.

Valve Publishes September VRS Ranking After Delay

Earlier, Valve delayed the VRS ranking update by one day. The company then had to backdate the table, which led to incorrect point calculations for some teams. The delay may have been related to the developers taking time off for Labor Day in the United States.