Changing EVO_NONE from 0xFFFE to 0 #5547
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
AsparagusEduardo
approved these changes
Oct 21, 2024
AsparagusEduardo
added
category: pokemon
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.
Changing
EVO_NONEbecause index 0 is unused, matching it withSPECIES_NONE,ITEM_NONE, etc.Feature(s) this PR does NOT handle:
I thought about adding a
EVO_COUNTdefine but if it isn't already in the expansion is because the base code doesn't need it, and adding it is sure easy for anyone who wants it.Things to note in the release changelog:
There could be a case for out of bounds errors if arrays or iterations are happening where you're using + 1 or - 1, as
EVO_FRIENDSHIPused to be the first index although it started with 1.Discord contact info
@GhoulMage