moretrees' giant jungle trees leave floating nodes when cut w/ the electrumese axe #2211
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2211
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?
perhaps the real question is, why does moretrees even define its own jungle trunk?
Maybe they wanted to do "something special" later, but never came to. Or they tried to be independent from MTG.
62cab1b1d9/node_defs.lua (L609-L611)
it's literally an exact replica.
there's some code that suggests that perhaps it's an attempt to keep too many moretrees "giant" jungle trees from spawning in an area? but the logic for that is redundant...
i'm gonna try aliasing them and see if anything weird happens.
i aliased them, but the issue doesn't seem to be due to there being random wrong nodes in the tree:
(i have no idea what's up w/ the flying item drops)
the real issue seems to be that moretrees giant jungletree models have "nubs" on the branches which the electrumese axe "treecapitator" code can't handle.
upstream issue (question) https://github.com/mt-mods/moretrees/issues/12
committed the alias just to reduce the node count by 1:
b4f6d3acfe
moretrees:jungletree_trunk is not cut down via woodcuttingto moretrees' giant jungle trees leave floating nodes when cut w/ the electrumese axewill rewrite treecapitator logic later