Change ExtInf to a struct #792
Merged
Conversation
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
Kewlan
approved these changes
Jan 9, 2026
Collaborator
Kewlan
left a comment
Kewlan
left a comment
There was a problem hiding this comment.
Excellent use case for a union!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This changes the type of
extInffrom a u8 array to a generic struct, in order to make it easier to add bitfields containing more than 8 flags, without having to add more functions to the multiplayer implementation because anything added toextInfwill be synced automatically.I also moved the
hasTimeTraveledflag out of the struct because it was intentionally skipped in the syncing code.