Counter-Strike 2: the August 24 update doesn't touch your matches — it gives community maps a HUD, a camera, and the ability to abort a bomb plant

Valve released a Counter-Strike 2 update on August 24, and if you've been looking for what it changes about your matches, the answer is: nothing. Not a single weapon tweak, not a modified map, not a gameplay fix. Every single line falls under one heading: MAP SCRIPTING.

That doesn't make it an inconsequential update, though. It gives community maps two things they didn't have before — their own interface and control over the player's camera — and opens the door to game modes that, until now, could only exist outside of Counter-Strike 2.

Here's what it contains, and what that means for what you'll find in the Workshop in the coming months.

Valve has not published these update notes in French. The passages in quotation marks in this article are our translation: they are not official wording from the French client.

First new feature: maps can display their own interface

Valve is adding an entity named custom_hud_layout, described as "the entry point allowing scripted maps to provide a custom interface".

What it allows, in the exact wording of the notes:

• four element types: Panel, Label, Image, and Button;
• CSS-based styling;
• state persistence during reloads in tools mode — a development convenience, not a gameplay feature.

Until now, a community map that wanted to display a score, a timer, or an objective had to place it in the 3D world, or hijack the existing display. It can now build a genuine on-screen interface, with clickable buttons — the Instance.OnCustomHudClicked event appears in this same update.

The limitation worth reading carefully

Valve immediately sets a boundary: "Client-side events and scripts are not supported." All the logic stays on the server. This means these interfaces won't be able to react instantly to a local player action: every interaction makes a round trip. For a menu or a dashboard, that doesn't matter. For an element that needs to track a shot down to the millisecond, it won't be suitable.

Second new feature: controlling the view without moving the player

The second entity is called cs_player_camera, and its description is short but carries heavy implications: it "gives control of a player's view without moving their character". It can also "be configured to let the player look around from the scripted position".

In other words: a map can now take control of the player's eyes — an intro cutscene, a top-down view, a forced spectator camera, a fixed shot on an objective — while leaving their body right where it is. Three functions come with it: CSPlayerCamera.IsEnabled, SetEnabled, and SetIsControllingAngles.

This is the missing piece for an entire category of content: narrative maps, guided tutorials, phase-based modes. It's now possible to show a player something without teleporting them.

The bomb block: four new observable moments, and the power to cancel

This is the most interesting part for anyone designing a game mode. Before this update, a script knew that a bomb had been planted or defused. It now knows that a plant or a defuse starts and that it is interrupted:

• Instance.OnBombPlantStart — the plant starts;
• Instance.OnBombPlantAbort — the plant is interrupted;
• Instance.OnBombDefuseStart — the defuse starts;
• Instance.OnBombDefuseAbort — the defuse is interrupted.

To these are added three C4-side functions: C4.GetPlantStartTime, C4.GetPlantFinishTime and above all C4.AbortPlant. The last one doesn't observe anything: it acts. A script can cancel a plant in progress.

Concretely, this makes possible rules that didn't exist before: a zone where planting is forbidden, a countdown that cancels the plant if it expires, an objective to complete before being able to arm the bomb. This is the kind of mechanic that sets a game mode apart from a simple map.

Finally, three functions give the script a direct read on a player's state: CSPlayerPawn.GetC4 (who is carrying the bomb), CSPlayerPawn.GetDefuseTarget (what they are defusing) and CSPlayerPawn.IsBuyMenuOpen (whether they have the buy menu open).

Entity movement becomes controllable

Three additions round out the picture: Entity.Move, Entity.GetMoveType, Entity.SetMoveType, along with a new CSMoveType enumerator. A map can therefore change the way an object moves during a match, and not just teleport it.

Added to this is Instance.Delay, which allows scheduling a delayed action without cobbling together a timer, and Instance.IsDedicatedServer, which lets a script know whether it is running on a dedicated server or locally — useful for cleanly disabling anything that doesn't make sense offline.

Two deprecations: existing scripts need checking

The update removes two parameters:

• planter is removed from the Instance.OnBombPlant event;
• defuser is removed from the Instance.OnBombDefuse event.

This isn't trivial: these two parameters identified the player behind the action. Any map that used them — to assign a score, trigger a reward, display a name — needs to be revised. The new CSPlayerPawn.GetC4 and GetDefuseTarget functions cover the need differently, but the relevant code must be rewritten.

Developer convenience, handled better than usual

Four lines concern error diagnostics, and they say something about the tool's maturity:

• errors encountered on a script's first run are now displayed in the console;
• unhandled promise rejections are also logged there;
• the column number is added to errors detected when compiling a module;
• the types of several events have been fixed, "where parameters could be undefined."

Debugging that goes from silence to a localized error message does more for the amount of content published than any new entity.

What players should take away from this

1. Your match tonight doesn't change. No weapon, no map, no economy is affected by this update.
2. Community maps are going to gain interfaces. Scores, objectives, clickable menus: what used to be a workaround becomes an official feature.
3. Game modes with proper rules become possible, particularly around the bomb, thanks to the four new observable events and the ability to cancel a plant.
4. Some existing maps are going to break until their authors replace the planter and defuser parameters.

A note on language

Valve usually translates its update notes into French: those from August 19, which covered Boulder, Poseidon and model speed against walls, were indeed published under the title "Mise à jour de Counter-Strike 2". Those from August 24 stayed in English, even for a player whose client is set to French.

The entity and function names mentioned here are code identifiers: they aren't translated into any language, and never will be. They're written as-is in a script, and that's how they need to be searched for.