Decompile revision 0xA changes for wireless_communication_status without fakematch#744
Open
AZero13 wants to merge 1 commit into
Open
Decompile revision 0xA changes for wireless_communication_status without fakematch#744AZero13 wants to merge 1 commit into
AZero13 wants to merge 1 commit into
Conversation
AZero13
force-pushed
the
fixthematch
branch
3 times, most recently
from
976776a to
651e84f
Compare
AZero13
changed the title
AZero13
changed the title
Contributor
Author
|
Whole 0xA version should be UBFix because none of this seems emulation related and Nintendo wouldn't change a line of code without a reason. |
AZero13
force-pushed
the
fixthematch
branch
2 times, most recently
from
2f3c5a7 to
5db9393
Compare
Contributor
Author
|
Should I just put the entire Revision A version of this function under UBFix or BUGFIX? |
AZero13
force-pushed
the
fixthematch
branch
2 times, most recently
from
24f6cf8 to
15b9b04
Compare
…tatus So one of the emerald UBFixes mentions that 0xFF can happen, and mentions that GROUPTYPE_NONE is 0xFF, and shouldn't be used as an index into groupCounts. It mentions that int theory the only activity with this group type (ACTIVITY_SEARCH) wouldn't satisfy the condition below, but not necessarily. Well, revision A of FRLG fixes this but has an even broader check, by skipping ALL invalid values by adding a range check. For this reason, I have also opted to do || UBFIX.
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.
So one of the emerald UBFixes mentions that 0xFF can happen, and mentions that GROUPTYPE_NONE is 0xFF, and shouldn't be used as an index into groupCounts. It mentions that int theory the only activity with this group type (ACTIVITY_SEARCH) wouldn't satisfy the condition below, but not necessarily.
Well, revision A of FRLG fixes this but has an even broader check, by skipping ALL invalid values by adding a range check. For this reason, I have also opted to do || UBFIX.