IntellectualSites / IntellectualSites/FastAsyncWorldEdit
//forest and //forestgen not generating any trees
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 806
- Forks
- 394
- Avg merge
- 22h 19m
- Merged PRs (30d)
- 14
Description
Server Implementation
Paper
Server Version
26.1.2
Describe the bug
When using //forest, regardless of the selection, no trees are ever generated. No error appears, but the result message from the command says "0 trees created".
Replacing FAWE with the standard WorldEdit plugin, using the same region selection, does generate trees as expected.
To Reproduce
- Run a fresh Paper server on 26.1.2. Install the latest FAWE plugin.
- Select a region in the world including grass blocks, and ample space for multiple trees.
- Use
//forest oak - Observe that no trees are generated.
Expected behaviour
Trees should be generated in the area selected, or in the case of //forestgen, within the radius specified.
Screenshots / Videos
Here is a video of me reproducing this bug on a Paper server with no other plugins other than FAWE itself. Using the latest paper build available at the time of recording.
Error log (if applicable)
No response
Fawe Debugpaste
I was unable to paste this due to this error: "Failed to upload files: Server returned status: 413 Entity Too Large"
Are you interested in contributing a fix?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing //forest oak and //forestgen on a fresh Paper 26.1.2 server with FAWE only, using a grass-containing selection and a specified radius. Compare the result with standard WorldEdit; done when the commands generate trees in the selected area or radius.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100