FallingTree Tree Scanning and Cutting Guide

FallingTree decides what counts as a tree, how much of it to remove, and in what style the blocks come apart. Every setting below lives in the mod's configuration, and the mod itself is triggered through its own interface and hotkeys rather than through crafting.

Breaking modes

The breaking mode controls how the tree comes apart once it has been detected.

• INSTANTANEOUS removes the whole tree in a single action.
• FALL_ITEM removes the whole tree in one action with an animation.
• FALL_BLOCK drops the logs to the ground while leaves are released as items.
• FALL_ALL_BLOCK makes the entire tree topple to the ground.
• SHIFT_DOWN makes the tree drop as you chop, so the blocks still have to be broken one by one, but you do not need to climb.

Several related options only apply in INSTANTANEOUS mode: the order logs are broken, the leaf count required around the top log, the force-break leaf radius, spawning logs at the break point, and the speed modifier.

Cut regions

The cut region decides which portion of the tree is removed.

• WHOLE_TREE removes everything.
• ABOVE_CUT removes only blocks connected above the point where you cut.
• ABOVE_Y removes only blocks sitting above the height of the cut point.

Size limits

Scanning and cutting are bounded by several numbers.

• The maximum scan value caps how many blocks are examined. Beyond it, the tree is not scanned further and a "tree too big" message appears with the limit shown.
• The minimum size skips small trees, producing a "tree too small" message.
• The maximum tree size triggers the max size action once exceeded: ABORT leaves the tree alone, while CUT still cuts it and leaves part untouched. A "tree too big" message appears with the limit shown.
• The search area radius limits how far from the broken log the tree is searched. Anything outside is ignored. A negative value behaves like an unlimited radius.

Leaf rules

Leaves are handled through allow and deny lists, plus distance and count rules.

• Additional leaf blocks can be allowed; blocks carrying the leaves tag are already accepted. A deny list overrides the allow list.
• allowedNonDecayLeaves covers leaves that must be broken rather than decaying.
• maxLeafDistanceFromLog sets how far a leaf may sit from the tree; this affects scanning only.
• minimumLeavesAroundRequired sets how many leaves must surround the topmost log for the mod to treat the structure as a tree, and only applies in INSTANTANEOUS mode.
• includePersistentLeavesInRequiredCount decides whether persistent leaves (placed or sheared by a player) count toward that minimum.
• leavesBreakingForceRadius force-breaks leaves within a radius measured from one of the topmost logs, even if another tree still holds them or they are persistent. break_leaves must be on, and this only applies in INSTANTANEOUS mode.
• breakNetherTreeWarts and breakMangroveRoots extend breaking to those blocks alongside the trunk.

Log rules and adjacent block checks

Log handling uses similar allow and deny lists, with blocks carrying the log tag already accepted and the deny list taking priority. allowMixedLogs permits any log type within one trunk; otherwise the trunk is treated as a single log kind.

allowedAdjacentBlocks lists blocks permitted beside the trunk. If an unlisted block is found, the outcome depends on adjacentStopMode: STOP_ALL cancels the whole cut, while STOP_BRANCH ends only the current branch and continues elsewhere, stopping at the offending block. An empty list means no restriction. When detection halts, a "search aborted" message reports the reason, such as finding a disallowed adjacent block.