Skip to content

Conversation

@CharlesFolz4
Copy link
Contributor

Document Gym scripts
Add macro for GoToIfBadgeAcquired

.endm

.macro ScrCmd_176 arg0
.macro SunnyshoreGymButton arg0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

polish: PressSunyshoreGymButton (note that it's Sunyshore, not Sunnyshore).

.endm

.macro ScrCmd_2CA
.macro EternaGymAdvanceClockState
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: AdvanceEternaGymClock

"movement_type": "MOVEMENT_TYPE_LOOK_NORTH",
"trainer_type": "TRAINER_TYPE_NONE",
"flag": "FLAG_UNK_0x01B2",
"flag": "FLAG_CANALAVE_RIVAL",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought: Should flags have some verbiage attached to them? e.g., does this flag designate that you've spoken to your rival? Fought your rival? etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't entirely sure how to document the "flag" fields, because "flag" seems to be an active-low indicator for the object's presence. To me, that means that this field would make more sense to rename as "hidden", rather than append _HIDDEN to every one of these flag variables. I'm not sure if that would have any further reaching implications though.

Copy link
Collaborator

@lhearachel lhearachel Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the flag being set to non-0 means that the object should be hidden. What if we just use a verbiage of FLAG_HIDE_X?

Comment on lines 562 to 563
"_comment": "this is right above the kid at the bottom of the stairs",
"script": 3,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: I don't think that this comment adds much value long-term; the goal is for events to be edited in some kind of GUI, anyways.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops, that was supposed to be a debug/note thing, forgot to delete it before committing.


AcuityCavern_CheckShouldUxieBeRemoved:
GoToIfSet FLAG_UNK_0x008E, AcuityCavern_RemoveUxie
GoToIfSet FLAG_MAP_LOCAL, AcuityCavern_RemoveUxie
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: Is this really local...? If so, what does "local" mean?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can tell, this is being used in the same way as the VAR_MAP_LOCAL_ variables are, except it's a boolean value written to and read from like a flag, instead of being an integer like the VAR_MAP_LOCAL_ variables, so that terminology was copied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants