Crystal Cluster Placement Tweaks + Refactor VoxelShapes #1502
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
…nate model datagen for crystal cluster
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
These changes implement the old behavior of Crystal Clusters, where they could be placed in multiple orientations. It also changes their support behavior, causing them to break when they lose their supporting block. It also changes their blockstate datagen in order to have them display properly.
Additionally, these changes refactor the VoxelShapes class, cutting more than half the code that was left unused, and including the new VoxelShapeUtils subclass in order to make existing shapes less redundant.
fixes #1496