sndpp: VDAT chunk support - #131
Open
erysdren wants to merge 1 commit into
Open
Conversation
erysdren
force-pushed
the
vdat
branch
2 times, most recently
from
August 8, 2026 21:35
c3b07a9 to
f664080
Compare
erysdren
marked this pull request as ready for review
August 9, 2026 00:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
not done yetthe parsing code is nasty, but it works fine for Valve-authored VDAT chunks. if any quotation marks were introduced around any text, it would probably break. thankfully Valve's tooling didn't add any...
also, i'm wondering if the version should be a float (as it is represented in text by the string
VERSION 1.0) or a major/minor pair. open to suggestions!