-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Identify more bit flags #465
Conversation
100cfb9
to
25bc910
Compare
@@ -27,7 +27,7 @@ VictoryRoad2FCheckBoulderEventScript: | |||
call VictoryRoad2FReplaceTileBlockScript | |||
pop af | |||
.not_on_switch | |||
bit 7, a | |||
CheckEventReuseA EVENT_VICTORY_ROAD_2_BOULDER_ON_SWITCH2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol
wCurrentMapScriptFlags 5 and 6 are both "new map was just loaded" flags used to ensure map scripts only run a function once when the map is loaded. I think the idea was that they could be re-set individually to re-trigger specific map load functions on a map, but I don't think that's ever done in a place where them being separate matters. |
Thanks, Vortyne. Yeah, I had noticed some of that after giving them |
* Identify more bit flags * Space
After this PR, there are two types of unidentified bit flags remaining: hardware register bits (for which I'm considering how much to edit/refactor hardware_constants.asm based on hardware.inc), and
wCurrentMapScriptFlags
bits 5, 6, and 7 (which need more case-by-case investigation).