Skip to content

Cherrypick: Use a separate tree registry for tree placement#3501

Open
SirYwell wants to merge 1 commit intomainfrom
cherrypick/treegen
Open

Cherrypick: Use a separate tree registry for tree placement#3501
SirYwell wants to merge 1 commit intomainfrom
cherrypick/treegen

Conversation

@SirYwell
Copy link
Copy Markdown
Member

@SirYwell SirYwell commented Apr 5, 2026

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

  • Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
  • Ensure that the pull request title represents the desired changelog entry.
  • New public fields and methods are annotated with @since TODO.
  • I read and followed the contribution guidelines.

* 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>
@SirYwell SirYwell requested a review from a team as a code owner April 5, 2026 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants