Fixes mistreatment of int return from Asura Strike fixes #2630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Prelude
Changes Proposed
This changes the check added in #2248 for the return from
unit->movepos
so it accepts anything!= 0
astrue
(as it originally was) instead of only the return value1
.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