wVirtualOAM->wShadowOAM as per convention #103
Merged
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
This was referenced Jun 26, 2022
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.
ISSOtm, as he pointed out in pret/pokecrystal#943 (comment), noticed that the WRAM constant
wVirtualOAMis, by most usage and convention elsewhere, known aswShadowOAMinstead.This PR aims to rename this particular WRAM constant so that it matches this convention.
pokecrystal companion PR: pret/pokecrystal#971
pokegold companion PR: pret/pokegold#99
This also works toward bullet point 1 in #69 (nice) by syncing this OAM constant across all Gen 1 and 2 main series pret repos