Have Tree Lopper place saplings with Mangrove Roots

Open
#1,354 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
game-dev

Research direction

Start by locating the TreeLopper implementation and its configuration handling in both CraftBook 3 and CraftBook 5, then trace how mangrove roots and logs are identified and lopped. Done means mangrove roots produce saplings and a configuration setting controls whether connected mangrove logs are lopped with them in both versions.

Written by the indexing model from the issue text.

Description

status:accepted type:feature-request
The Problem

Currently the TreeLopper feature doesn't place saplings when lopping Mangrove roots. Also, there's not a way to lop both the mangrove roots and the mangrove logs, so the player still ends up doing several lops instead of benefitting from a single "lop".
This is true for both Craftbook 3 and 5

A Solution

Have TreeLopper place saplings when lopping Mangrove Roots.
Have configuration setting for TreeLopper that lets you toggle if the Mangrove logs can be lopped with the roots.

Alternatives

Place the mangrove sapling when lopping mangrove roots.
Just lop all the Mangrove roots and wood together automatically without a configuration setting.

Anything Else?

No response

Dominant language
Java
Stars
320
Forks
165
Avg merge
6d 21h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EngineHub/CraftBook

All issues in EngineHub/CraftBook

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.