What changed in the patch
Valve’s official announcement lists several Cache fixes: gaps on the map were addressed, a wallbang spot on B site was fixed, a competitive CT spawn point was added, and further T spawn points were introduced.
The more technical portion concerns CSPlayerCamera. It is now called CustomPlayerCamera and has gained GetPlayer, GetMode, SetMode, and SetFollowConfig. IsEnabled, SetEnabled, and SetIsControllingAngles are now deprecated.
Valve also changed custom_hud_layout. The new observable property controls whether an observer sees the same UI as the player being watched. The patch adds client-state-driven classes for the buy menu and scoreboard, resolves stale HUD state when switching spectator targets, and places custom HUD layouts above the base HUD.
Demo chat behavior has changed as well. Chat is encrypted in demo files under the same rules used in CS:GO. Team chat cannot be read during playback, while global chat is available only when a demo is watched through the in-game watch UI.
What this means for software
The announcement does not mention an anti-cheat update, a detection event, a ban wave, or account enforcement. It also does not state that any specific cheat is incompatible. There is no factual basis in these notes to claim that this patch detected software or that every product must be taken offline.
The camera and custom_hud_layout work is mainly relevant to spectator tools, custom interfaces, and demo playback. If your software does not interact with those areas, the announcement itself gives no reason to expect a feature change. Likewise, the Cache fixes describe map adjustments, not third-party software behavior.
Still, patch notes are not a compatibility report. Check the current status of the product you use before launching. That applies equally to Midnight for CS2 and Aquila for CS2: no anti-cheat line in Valve’s post does not confirm that a product is ready for the current game build. The product status and its support channel are what matter.
Launch now or wait?
Based on the published notes alone, there is no announced anti-cheat event or ban wave that requires everyone to stop. At the same time, Valve’s post does not confirm that any cheat has been updated for the current build.
Update the game, verify the product’s status, and wait if its status is unknown, marked as updating, or its support team asks users to hold off. Use the safe launch checklist before starting a session. It reduces avoidable mistakes but does not remove the risk of a ban; no cheat is risk-free.
For demo reviewers, missing team-chat messages are now an expected result of Valve’s encryption rules. Do not automatically treat that as a broken demo or evidence that outside software affected the file.
What to monitor next
Watch for notices from the developer of your own product instead of inferring software status from the camera and HUD changes. Pay attention to post-update status reports, launch issues, and any official request to wait. For context on why functioning software can still be detected after updates, during detection waves, or because of in-match behavior, see Why cheats get detected.
Original source developer announcement