Fix parsing of certain dc6 found in casc #116
Merged
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.
Normally, the frame data starts at the beginning, and has Length bytes, and after that there are several (3 or 4) bytes filled with Termination e.g. EE EE EE, before the next frame header starts
But in the new buysellbtn.dc6 there's no termination, and instead the data is aligned to the right: first several bytes are 00 00 00, which are noop, but if to just take the first Length bytes, the last bytes (which were previously just before the termination area) are now outside the Length range
Old file (from MPQ):
New file: