Choppy ignores parts of tree #4656

Closed
opened 2023-06-01 16:14:18 +00:00 by niceride · 6 comments

Choppy does not see the node where the sapling sprouted into its tree form, when chopping this it doesn't reliably start choppy and chopping Y+1 from the sprout node doesn't always chop both up and down, so ending up with stumps.

Choppy does not see the node where the sapling sprouted into its tree form, when chopping this it doesn't reliably start choppy and chopping Y+1 from the sprout node doesn't always chop both up and down, so ending up with stumps.
niceride changed title from Choppy ignores sprout node to Choppy ignores parts of tree 2023-06-01 16:18:41 +00:00
Member

If you aim at the lower block at the start, the whole tree will be cut down. So I don't see a problem.

If you aim at the lower block at the start, the whole tree will be cut down. So I don't see a problem.
flux added the
1. kind/bug
3. source/mod upstream
labels 2023-06-01 19:15:07 +00:00
Member

if you turn the tree into two or more disconnected parts, there's not a whole lot choppy can do. if it's just the stump, it's also trivial for the player to just cut it down themselves. i'm not sure this is worth any sort of "fix".

one thing i've been meaning to do, is to not have choppy stop the process when the tool wears out, and instead "pause" and wait for the player to repair the tool.

if you turn the tree into two or more disconnected parts, there's not a whole lot choppy can do. if it's just the stump, it's also trivial for the player to just cut it down themselves. i'm not sure this is worth any sort of "fix". one thing i've been meaning to do, is to not have choppy stop the process when the tool wears out, and instead "pause" and wait for the player to repair the tool.
Author

How is it that woodcutting got this (mostly) right? Or I am remembering poorly.

How is it that woodcutting got this (mostly) right? Or I am remembering poorly.
Member

How is it that woodcutting got this (mostly) right? Or I am remembering poorly.

woodcutting didn't start at the top of the tree and go down.

i've figured out a way to solve this though: 348b252253

> How is it that woodcutting got this (mostly) right? Or I am remembering poorly. woodcutting didn't start at the top of the tree and go down. i've figured out a way to solve this though: https://github.com/fluxionary/minetest-choppy/commit/348b2522532c52833e373405c821dbcf35c552df
flux added the
4. step/ready to QA test
label 2023-06-02 20:28:28 +00:00
AliasAlreadyTaken added this to the 1.1.122 milestone 2023-12-06 13:52:51 +00:00
AliasAlreadyTaken added the
ugh/QA OK
label 2023-12-06 13:52:56 +00:00

QA

Most likely in since some updates, but only now in QA

QA Most likely in since some updates, but only now in QA
flux added
5. result/fixed
and removed
4. step/ready to QA test
labels 2023-12-17 23:15:13 +00:00
Member

this is live

this is live
flux closed this issue 2023-12-17 23:15:48 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#4656
No description provided.