Skip to content

CS2 spec, dictionary and changelog: player_status.is_silent_reload - #77

Merged
billfreeman44 merged 2 commits into
masterfrom
silent-reload
Nov 1, 2026
Merged

billfreeman44 merged 2 commits into
masterfrom
silent-reload

Conversation

@billfreeman44

@billfreeman44 billfreeman44 commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

What

The CS2 CSDS spec, data dictionary and changelog pages gain player_status.is_silent_reload, from csgo-rushb#139. It's true while the held weapon reloads silently: CS2's update of 2026-09-22 lets a player reload silently, and more slowly, by holding the reload key.

Files:

  • spec.md: a paragraph in the player_status section, and the row in its table. The type, nullability and origin come from the manifest csgo-ppp 9.0.1 wrote for a build-10924 match parsed with that branch (bool, nullable, replay). The converter's own column reference: csgo-ppp#228.
  • csds_dictionary.csv: one row, with when it's null.
  • changelog.md and changelog-by-channel.md: rendered from igl-gotv-v2's scripts/csds-changelog/changes.yaml. The render adds only this entry.
  • CHANGELOG.md: one line under Unreleased.

npm run build passes. Prettier's --check warns on spec.md only for line endings (this checkout has CRLF), as it does on master's copy; the content matches Prettier's output.

The date is provisional

The parser release that carries the column isn't cut yet. The changelog entry is dated 2026-10-31, the day it was written. When the release reaches production, changes.yaml gets the real date and the release name, and the pages are re-rendered.

Production lock: igl-plant#144 holds this repo until that csgo-rushb release is in production, so subscribers don't read about a column their data doesn't have.

Where the numbers come from

Measured on 14 demos recorded after the update (docs/active_work/rushb_silent_reload_column.md in igl-gotv-v2). The flag comes on 14 or 15 ticks into the reload on build 10924, and 17 on build 10955: "about a quarter of a second". Silent reloads' magazines land 1.1 to 2.0 times as late as normal ones': "up to twice as late". Every demo before build 10924 lacks the flag.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Two active nit findings remain because the is_in_reload documentation uses incomplete wording that leaves the boolean condition ambiguous in both the CSV and specification.

2 open issues
What changed in this PR

This pull request documents the new nullable CS2 player_status.is_silent_reload field across the specification, data dictionary, generated changelogs, and repository changelog. The release date remains provisional pending parser production availability. Minor wording nits remain in the field descriptions.

Changes:

  • Added the field’s behavior, type, nullability, and replay origin to the CS2 specification.
  • Added dictionary metadata and nullability details.
  • Updated both CSDS changelog pages and the repository’s Unreleased changelog.
File Description
docs/​datascience/​adx/​cs2/​csds/​spec.md Documents player_status.is_silent_reload and adds it to the player_status schema.
docs/​datascience/​adx/​cs2/​csds/​changelog.md Adds the provisional column-addition entry.
docs/​datascience/​adx/​cs2/​csds/​changelog-by-channel.md Adds the corresponding player_status change entry.
docs/​datascience/​adx/​cs2/​csds/​assets/​csds_dictionary.csv Adds the field’s dictionary metadata and behavior description.
CHANGELOG.md Records the documentation update under Unreleased.

Review effort: Lite

Comment thread docs/datascience/adx/cs2/csds/spec.md Resolved
From Copilot's review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@billfreeman44
billfreeman44 merged commit 80bd986 into master Nov 1, 2026
5 checks passed
@billfreeman44
billfreeman44 deleted the silent-reload branch November 1, 2026 01:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants