Choppy ignores parts of tree #4656
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4656
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 ignores sprout nodeto Choppy ignores parts of treeIf 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 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.
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
QA
Most likely in since some updates, but only now in QA
this is live