Fix #6803: CargoMonitorID bit packing updated to handle 64 cargo types. #7175
Conversation
This file contains 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
PeterN
force-pushed
the
cargomonitor-bit-packing-fix
branch
from
09a02f4
to
338deed
Compare
LordAro
previously approved these changes
Feb 4, 2019
…go types. This requires a saveload bump to change the bitpacking on loading older saves.
PeterN
force-pushed
the
cargomonitor-bit-packing-fix
branch
from
338deed
to
eda2dbc
Compare
LordAro
approved these changes
Feb 4, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the update from 32 to 64 cargo types, the bit packing used by CargoMonitorID was not updated, so cargo types beyond 32 could not be monitored. This is fitted in by moving cargo type down into a free bit.
assert_compile()s added for sanity.
This requires a saveload bump to change the bitpacking on loading older saves.