Cherrypick: Use a separate tree registry for tree placement#3501
Open
Cherrypick: Use a separate tree registry for tree placement#3501
Conversation
* Use a separate tree registry for tree placement * Initialize the registries on the other platforms * Add the tree type system to the registry converter * Allow CoralTree features * Add 1.21.9 adapter changes * Apply PR feedback * Re-add existing Bukkit implementation (cherry picked from commit c561b0d96cec44c1038ff3b3b9d3e07baee963e5) Co-authored-by: SirYwell <hannesgreule@outlook.de>
NotMyFault
approved these changes
Apr 5, 2026
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
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.
Overview
Description
This change makes it easier to adapt support for modern MC versions from WE.
Note that we're now initializing registries differently. There might be more cleanup work possible in that area.
Submitter Checklist
@since TODO.