-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix regression introduced for Eject Button #3738
Conversation
@@ -5853,7 +5853,8 @@ static void Cmd_moveend(void) | |||
if (IsBattlerAlive(battler) | |||
&& gBattlerAttacker != battler | |||
&& GetBattlerHoldEffect(battler, TRUE) == HOLD_EFFECT_EJECT_BUTTON | |||
&& TARGET_TURN_DAMAGED |
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.
maybe better to have a BATTLER_TURN_DAMAGED macro thats the same as TARGET_TURN_DAMAGED but for a given battler id
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.
Seems like it already exists BATTLER_DAMAGED
but is only used once. Should I rename it? I like BATTLER_TURN_DAMAGED
more
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.
Went ahead and made the change.
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.
Yeah BATTLER_DAMAGED is fine
Also Renamed |
Regression introduced in #3669
Target to upcoming because the recently introduced
enduredDamage
Battle Struct field fixes a small bug that applies here as wellOther:
Fixes: #3633