Bla reports: [testserver] choppy cuts nearb ... #3876
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3876
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?
Bla reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
it cuts nearby trees of the same type, but only within a (tree-dependent) box. this is because this is the simplest way to limit how far it searches, while still guaranteeing it'll completely cut down individual trees. teaching it how to identify individual trees is possible but certainly difficult and somewhat laggy. it's something i'd like it to do, but i'm probably not going to implement that for quite a while.
ah ok I thought you already did that with choppy.
Still strange that it cut around half of the public farm after I started with a tree next to the furnaces.
But from my side this can be closed.
choppy is extensible and better heuristics can be added easily, but currently, those heuristics don't exist. and the "ideal" heuristics will require machine learning, and that stuff is still had to code up right.
part of the issue is that several kinds of trees use the same "trunk" node, and choppy currently has to assume that the target tree is the largest possible one of those. also, the box bounds are perhaps a bit over-lenient. if we do the work to better express the approximate boundaries of a tree, we can do better.