Skip to content
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

Fixes mistreatment of int return from Asura Strike fixes #2630

Closed

Conversation

guilherme-gm
Copy link
Member

Pull Request Prelude

Changes Proposed

This changes the check added in #2248 for the return from unit->movepos so it accepts anything != 0 as true (as it originally was) instead of only the return value 1. unit->movepos currently only returns 0/1, but as noted by @skyleo in #2248 (comment) , it could introduce an unexpected side-effect.

Issues addressed:
Fixes #2629

@Kenpachi2k13 Kenpachi2k13 added this to the Release v2020.03.08 milestone Feb 24, 2020
@Kenpachi2k13 Kenpachi2k13 added codereview:accepted Code review was positive and the pull request can be accepted as is component:mechanics:skills Affecting the skills' game mechanics labels Feb 24, 2020
@MishimaHaruna
Copy link
Member

This was included as part of #2546 merged earlier today, thank you!

@guilherme-gm guilherme-gm deleted the fix/movepos-check branch February 24, 2023 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codereview:accepted Code review was positive and the pull request can be accepted as is component:mechanics:skills Affecting the skills' game mechanics
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Possible silent break of custom code and unintended side-effects by asura strike fix.
4 participants