-
-
Notifications
You must be signed in to change notification settings - Fork 884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forest generation works bad in 1.18.1 #2008
Comments
this is an issue with changes in mojang's tree generation code. unsure if this was intentional but we may have to do extra validity check that they did previously and don't now. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Hi, I was wondering if there's any work around for this issue? |
Me too. The command //forest works fine on flat area... but as soon as the terrain gets difference in elevation, trees start stacking on top of eachother. Super annoying to get rid of haha :D Maybe a solution would be to only allow a tree to spawn on an existing grass_block. Without giving it permission to create one on its own. All the stacked trees have created dirt beneath them... |
this is also a problem in 1.19.2, does anyone know how to get around this? |
There is no workaround AFAIK, fixing this is quite involved because the checks are no longer straightforward. I've taken multiple stabs at it without results. |
Same thing happening to me on the latest version on MC 1.20.2... Additionally, the trees also generate on water surfaces not just on top of each other... |
WorldEdit Version
7.2.9-SNAPSHOT+6045-3fa364b
Platform Version
git-Paper-141 (MC: 1.18.1)
Confirmations
Bug Description
/forestgen
generates new trees above existing ones.Expected Behavior
Before update to 1.18.1, in version 1.17.1, it worked correctly and doesn't place dirt blocks inside leaves. I expect that in the new version it should work the same way.
Reproduction Steps
/forestgen
multiple timesAnything Else?
No response
The text was updated successfully, but these errors were encountered: