What this means for cheat users
This Counter-Strike 2 patch is focused on the Script API: resource precaching, hostage-related objects, console variables, round rules, HUD, and radar behavior. The announcement does not list an anti-cheat change, report bans, or state that any cheat has been affected.
That means the notes cannot confirm either a detection issue or a lower-risk launch. Do not treat the lack of an anti-cheat line as a product status update. Every cheat carries a risk of a ban.
API changes in the announcement
The update adds CSPrecache, including methods for checking resource loading states and releasing resources. It also introduces CSHostage, with methods for pickup, carrying, rescue status, rescuer details, and pickup timing. CSPlayerPawn.GetHostage was added as well.
New events cover the start of a hostage pickup, an aborted pickup, a completed pickup, a drop, a rescue, and a hostage kill. There is no listed event for carrying a hostage. CSHostage.IsBeingCarried is a status method, not an event.
A top-level Console export is now available. ClientCommand, ServerCommand, and RegisterCheatCommand moved there, while Instance.Msg was renamed to Console.Log. The new console methods can read several convar types and set convars; SetConvar runs synchronously and is not restricted by sv_cheats.
GameRules now has new StartWarmup, EndWarmup, GetTeamScore, AddTeamScore, and TerminateRound methods. Separately, IsWarmupPeriod, IsFreezePeriod, IsTeamIntroPeriod, GetRoundsPlayed, GetRoundRemainingTime, SetRoundRemainingTime, and AddTeamMoney were moved to GameRules. The original locations of moved and renamed methods still work, but are deprecated.
The notes also say radar elements can appear in every game mode, add HUD layout classes, and improve script warning output with call stacks and bad-argument details.
Launch now or wait?
If you use CS2 cheat software, check the status of your specific product with its developer or support team. This announcement alone reports neither broken compatibility nor confirmed support for the current game build.
After a game update, first confirm that your product has a version for the current build. That applies to Aquila for CS2 and Soft HUB alike: patch notes are not a substitute for a product status notice. Do not launch an older build simply because anti-cheat is not mentioned.
Before starting the game, check the version, download source, and the developer’s instructions. Our safe launch checklist covers the basic routine. It does not remove ban risk, but it can help avoid user-side mistakes.
If the game or software behaves differently after the update, do not try random file replacements or disable game protection components. Wait for a compatibility notice and use the official software update. For context on why game updates and other factors can precede detections, see Why cheats get detected.
Original source developer announcement