-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assert using Hex value #12
Comments
This is not a simple issue, because the codebase actually expects $100 as written, even though |
Yeah, fixing the design flaw would be appropriate, like the many applied bugfixes which were relevant to the 16-bit features. |
That design flaw was already fixed in @aaaaaa123456789 's commit 03414e5. |
Great, then yes, the extra footprints are no longer necessary. |
This has been resolved in the latest rebase. |
gfx/footprints.asm uses $100 for assert, instead of using a constant like NUM_POKEMON.
The text was updated successfully, but these errors were encountered: