Fix: "-q" displays NewGRF IDs in the wrong byte-order #12397
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.
Motivation / Problem
Although
-q
is puzzling to me, at least one serious issue was spotted when using it for the first time: NewGRF IDs were wrongly displayed.For example, it shows
0200434A
instead of4A430002
.Description
It always kinda makes me wonder if
-q
is ever used by anyone, and if the author actually tested it for "usefulness" :D Either way, fixed the issue.Limitations
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.