Productive Trees Exploration Sapling Recipes #596
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This addresses an issue where certain saplings that are usually obtained from structures don't really have another way. So I'm shoehorning Ender Crafting once again to solve it.
Most of the saplings used as a base were chosen randomly, except for Blue Yonder and Firecracker.
Uses a different approach compared to other custom Ender Crafting recipes. Figured I could use KubeJS' Custom data capabilities, letting me handle each sapling in one file.
Fixes #558
(Note: The top recipe uses Flawed Solar Gems. The bottom recipe uses Perfect Solar Gems.)