You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ClassInfo code name changed structuretype -> treetype
Renamed class from StructureType to TreeSpecies (went with this to not clash with Bukkit "TreeType")
Switched to use an EnumClassInfo
Added all the new trees we've gotten over the years
Removed old code used to handle enum stuff that the EnumClassInfo will handle
Removed comparator, handled by EnumClassInfo
Removed parser, handled by EnumClassInfo
Testing Completed
I grew a few trees in game.
They're pretty... wanna see?
No? Too bad.. here they are anyways:
Supporting Information
I did a big renaming of the tree types in the lang file, but since this has never been documented, I don't think anyone will miss the weird ones I took out.
I went with names that better match the actual names of the trees vs. weird names Bukkit used from 15 years ago.
sovdeeth
added
bug
An issue that needs to be fixed. Alternatively, a PR fixing an issue.
enhancement
Feature request, an issue about something that could be improved, or a PR improving something.
breaking changes
Pull or feature requests that contain breaking changes (API, syntax, etc.)
labels
May 11, 2026
Is it possible to test growing a tree? Or do we already have a test for that? I think on grow may do something similar.
My fear is since internally its attempting to place a configured feature,
if the feature for whatever reason fails to place, the effect will be unsuccessful.
Is it possible to test growing a tree? Or do we already have a test for that? I think on grow may do something similar.
My fear is since internally its attempting to place a configured feature, if the feature for whatever reason fails to place, the effect will be unsuccessful.
yeah that's why the test should ensure the conditions for the tree to be grown should be valid (eg clear an area, place a dirt block, etc
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
breaking changesPull or feature requests that contain breaking changes (API, syntax, etc.)bugAn issue that needs to be fixed. Alternatively, a PR fixing an issue.enhancementFeature request, an issue about something that could be improved, or a PR improving something.
3 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.
Problem
The TreeType class info was super duper outdated:
Solution
Give TreeType some new life:
structuretype->treetypeTesting Completed
I grew a few trees in game.

They're pretty... wanna see?
No? Too bad.. here they are anyways:
Supporting Information
I did a big renaming of the tree types in the lang file, but since this has never been documented, I don't think anyone will miss the weird ones I took out.
I went with names that better match the actual names of the trees vs. weird names Bukkit used from 15 years ago.
Completes: #8634
Related: none
AI assistance: none