-
Notifications
You must be signed in to change notification settings - Fork 46
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
code_8073CF0 #212
code_8073CF0 #212
Conversation
Ready for review |
@@ -108,4 +108,12 @@ enum DungeonID | |||
NUM_DUNGEONS | |||
}; | |||
|
|||
static inline bool8 IsClientOrTeamBase(s32 joinedDungeon) |
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.
This function occurs in a number of other places under the name JoinLocationCannotUseItems
. Perhaps those usages can be combined here too?
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.
Sure, I could do that. What about the name, which one you find better? Or maybe you have a better idea for the name : D
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.
I went with IsClientOrTeamBase
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.
I originally named JoinLocationCannotUseItems
for an inline function related to items, but we've now found other occurrences that aren't item-related, like determining whether a Pokémon can gain experience. I'm not sure where DUNGEON_RESCUE_TEAM_BASE
is used, so I like a literal name like IsClientOrTeamBase
better as well.
WIP