CS2 Update (Oct 4, 2026)

This update quietly restructures a lot of under‑the‑hood CS2 content: several legacy tools maps and sample addons are being removed or relocated, old shader and engine configuration files are cleaned out, and some UI scripts and protocol definitions are retired. Competitive gameplay content is unaffected, but modders, Workshop creators, and tool users may notice changes in where certain resources live or how they’re accessed.

Modding and Community Addon Cleanup

• Legacy community addons removed from core game files: The directory manifests for cs_alpine, de_sanctum, de_stronghold, and de_warden under game/csgo_community_addons have been deleted, along with thousands of referenced assets (models, materials, particles, sounds, skyboxes, and map text files).
  • This confirms that these addon maps are no longer packaged as built‑in community content in the base install.
  • In practice, this likely means these maps will only be available through Workshop or separate downloads rather than shipping as bundled examples.
• Addon asset cleanup details: Removed paths include:
  • Map files and skyboxes such as maps/de_sanctum.txt, maps/de_sanctum_skybox.vpk, maps/prefabs/skybox_night2.vpk, and maps/prefabs/de_warden/de_warden_skybox.vpk.
  • Large sets of environment art for each addon (e.g., materials/de_gibraltar/*, materials/alpinemesh/*, materials/de_warden/*).
• Impact on creators and servers:
  • Community server operators and mappers who relied on these pre‑bundled assets may need to ensure their own Workshop items or server content packs include all required resources themselves.
  • This cleanup suggests Valve is separating core game content from example or third‑party addon content, which may help keep the main install leaner and reduce confusion about what is officially supported.

Editor “Zoo” Script and Training Content Removed

• Editor zoo scripts removed from content and packed game: A set of JavaScript helpers for the maps/editor/zoo tools map have been deleted in both source and packed form, including:
  • chess.js (a complex demo script that embedded a chess engine and other logic)
  • trace.js (hit‑trace visualizer using TraceLine, TraceSphere, TraceBox, TracePlayer, and TraceBullet)
  • grenadetraining.js (HE grenade training mini‑game logic)
  • mdlchange.js (live model swapping and scaling demo)
  • setup.js and input.js (warmup / bot setup, custom HUD and input debug overlays)
  • UI assets welcome.css and welcome.xml, plus a small hello.js sample.
• Why it matters for modders:
  • These scripts were effectively built‑in examples of the cs_script/point_script API used in tools mode. Their removal from the shipped game suggests they’ve been moved or superseded by updated examples elsewhere.
  • Map script authors who depended on these specific files being present at maps/editor/zoo/scripts/* will need to keep their own copies in their projects instead of referencing the engine copy.
• Player impact:
  • These changes are all under editor and tools locations; regular players shouldn’t see any change to normal gameplay, training modes, or official maps.

Panorama UI: Honor Icon and Buy Menu Preview Scripts

• honor_icon.js removed:
  • The dedicated Panorama script that handled “honor icon” visuals—XP streak coloring, particle effects, and Prime badge fallback—has been deleted from panorama/scripts.
  • The file drove color/particle choices based on an xptrail_value tier and Prime status.
  • Its removal strongly suggests the honor icon logic has been moved elsewhere (possibly into layout XML, a different script, or backend code), or that the specific effect is being retired or redesigned.
• buymenu.js character preview script removed:
  • A small script used to update the agent preview in the buy menu (BuyMenu_UpdateCharacter handler) has also been deleted.
  • It used CharacterAnims and ItemInfo to show your current agent and weapon.
  • This points to an internal refactor: the functionality may now be handled by shared vanity/character preview code instead of a bespoke script.
• HUD layout node removed:
  • hud/infohudlayouts.xml, which wrapped a CSGOInfoHudLayouts element, has been removed.
  • This likely reflects a simplification or relocation of how per‑mode HUD layouts are defined, rather than a visible change on screen.
• Expected effect on players:
  • Because these scripts are small and tightly scoped, players are more likely to see subtle UI behavior changes (e.g., how honor/XP visuals or buy‑menu preview refresh) rather than large visual redesigns.
  • The underlying functionality is likely preserved via new code paths, but some edge‑case behaviors could change as part of the refactor.

Engine Configuration and Legacy GameInfo Files

• Core engine gameinfo.gi files for CS:GO removed:
  • game/csgo_core/gameinfo.gi and game/csgo_imported/gameinfo.gi have been deleted.
  • These files described the old Source 2 configuration for “CSGO Core” and “CSGO Imported”, including search paths, render pipeline modes (CsgoForward, tools modes), Hammer defaults, baked lighting and navmesh settings, and various engine toggles.
• Associated branch‑specific configs cleaned up:
  • gameinfo_branchspecific.gi in both game/csgo_core and game/csgo_imported has been removed.
• What this implies:
  • CS2 appears to be consolidating onto a single, updated configuration path rather than inheriting from csgo_core / csgo_imported layers.
  • Modders using internal engine tools or legacy CS:GO import paths may need to rely on new CS2‑specific documentation and configs instead of these older gameinfo files.
  • For ordinary players this has no direct impact; it’s structural rather than gameplay‑facing.

Shader and Render Pipeline Clean‑Up

• Large set of Vulkan shaders removed from csgo_core:
  • Around 35 shader source files under game/csgo_core/shaders_vulkan_dir/shaders/vfx have been deleted, including:
    • Material shaders: csgo_character.slang, csgo_customglove.slang, csgo_customweapon.slang, csgo_lightmappedgeneric.slang, csgo_vertexlitgeneric.slang, csgo_unlitgeneric.slang, simple.slang, generic.slang, spritecard.slang.
    • Specialized passes and tools: csgo_tools_wireframe.slang, csgo_tools_shading_complexity.slang, tools_solid.slang, tools_wireframe.slang, various composite and debug shaders.
• Additional shader manifests removed:
  • game/csgo_core/shaders_vulkan_dir.txt and shaders_pc_dir.txt have been removed, along with their path lists.
• CS2 weapon StatTrak shader removed from game/csgo:
  • shaders_vulkan_dir/shaders/vfx/csgo_weapon_stattrak.slang has also been deleted.
• Core engine shader helpers updated:
  • A couple of generic shader utilities in game/core/shaders_vulkan_dir/shaders/vfx (e.g., GPU particle initialization, aggregate culling) have been removed in their previous form.
• Likely impact:
  • These files were part of an older internal shader pipeline. Their removal strongly suggests the live game is now using a newer, unified shader set elsewhere in the tree.
  • Players shouldn’t see obvious visual downgrades; this looks like a migration away from CS:GO‑branded shader modules toward consolidated CS2 equivalents.
  • Modders who were hooking or reading these exact shader names for tooling will need to update any hard‑coded paths.

Tools, Editor Art, and Asset Manifests

• Old tool UI images removed:
  • Several PNGs used by internal tools were deleted:
    • valve_style radio button and tab graphics
    • vconsole/ping.png
  • This points to a refresh or simplification of the tool UI skin; it doesn’t affect in‑game visuals.
• Tool asset info manifests pruned:
  • readonly_tools_asset_info.txt in both csgo_core and csgo_imported have been cleared out.
  • Removed items include materials and textures for light cookies (materials/effects/lightcookies/*), dev/placeholder materials, tool helper materials like materials/tools/tools_cs_place.vmat and invisible ladder materials, and a startup_background material.
• Pack file manifests adjusted accordingly:
  • pak01_dir.txt for csgo_core and csgo_imported were updated to drop the compiled (_c) versions of the same materials and textures.
• Effect on Workshop and tools users:
  • Mapmakers who relied on Valve’s stock light cookie textures or some of the more obscure dev/tool materials may need to provide their own equivalents.
  • Because these entries lived in tool‑oriented manifests, this mostly affects Hammer and internal tooling rather than live servers.

Protocol and Integration Changes

• steammessages_gc.proto removed:
  • The Protobufs/steammessages_gc.proto definition file has been deleted.
  • It previously described a wide range of Game Coordinator and Web API messages, including:
    • Web API key and HTTP request/response messages (CMsgWebAPIKey, CMsgHttpRequest, CMsgHttpResponse, CMsgWebAPIRequest).
    • Account/license and stats queries.
    • Memcached operations and SQL stats.
    • Email templates and partner microtransactions.
    • Routing and session update messages.
• What this suggests for plugin developers:
  • Public protocol descriptions for these internal GC/WebAPI messages are no longer shipped in this location.
  • Any third‑party tooling that parsed this .proto from the game’s files will no longer find it and should instead rely on separately maintained protocol definitions.
  • This does not by itself prove that the underlying GC behavior changed; it indicates the schema file is no longer exposed here.

Build Manifests and Branch Metadata

• New manifest files added:
  • Several small text manifests under manifests/ (e.g., manifest_731.txt–manifest_735.txt, manifest_2347772.txt, manifest_2347774.txt) have been added.
  • These appear to be build/packaging markers used to describe content bundles or depot layouts, not gameplay content.
• Impact:
  • These changes are entirely behind the scenes, helping organize how the game is packaged and updated on the platform.
  • Players and server operators won’t interact with these files directly.

Overall Impact

This update is focused on housekeeping, refactors, and the removal of legacy or CS:GO‑era assets and configs rather than on visible gameplay changes. The main takeaways:

• Community addon maps (cs_alpine, de_sanctum, de_stronghold, de_warden) are no longer packaged as built‑in addons, reinforcing a clearer separation between official CS2 content and community maps.
• Tools and example content for the editor (the editor/zoo scripts, some dev materials, and internal UI art) have been removed or relocated, which modders and Workshop creators should account for in their pipelines.
• UI and shader code is being consolidated and modernized; most of this should be invisible to players but may change edge behaviors in honor icons, buy‑menu previews, or developer tools.
• Publicly shipped protocol and config files tied to the old CS:GO stack are being retired in favor of newer internal structures.

For everyday CS2 players, gameplay, matchmaking, and the economy appear unchanged. The update primarily cleans out legacy layers as CS2 continues to move further away from its CS:GO foundations and toward a more self‑contained, streamlined engine and content structure.