Fix bug in collision masking bits example #7646
Merged
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skyace65
approved these changes
Jul 13, 2023
skyace65
added
bug
area:manual
Contributor
|
Thanks! |
mhilbrunner
pushed a commit
that referenced
this pull request
Aug 1, 2023
Fix bug in collision masking bits example
mhilbrunner
pushed a commit
that referenced
this pull request
Aug 1, 2023
Fix bug in collision masking bits example
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In the example for setting collision mask bits by script, it is explaining how to set the bits for layers 1, 3, and 4 but the code example is also enabling layer 32, which it shouldn't. Layer 32 should also be
0instead of1to following what was explained above it and below it.