Custom collision whitelists #148
Merged
Conversation
This file contains 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
MattSturgeon
force-pushed
the
config/custom-whitelist
branch
2 times, most recently
from
d9df80b
to
7dcbf20
Compare
MattSturgeon
force-pushed
the
config/custom-whitelist
branch
2 times, most recently
from
bff248e
to
b93a4b3
Compare
MattSturgeon
force-pushed
the
config/custom-whitelist
branch
from
b93a4b3
to
ac8c127
Compare
hashalite
approved these changes
Apr 21, 2024
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Building on #137, this PR adds the ability to configure a custom block collision whitelist.
As usual, I'm not super happy with my naming/translation text...
Has the same list entry GUI issues as #146, namely it isn't obvious you can click on & edit list entries.
Currently includes everything in #137.