JeCel reports: The moretrees oak trees genera ... #4999
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4999
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?
JeCel reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
=or= get rid of the one that is ridiculous and takes 3 days to chop down?
Maybe instead adjusting the schematic slightly to have more leaves nodes and less wood nodes? Currently it is basically a wooden sphere with a small layer of leaves on it.
Moretrees aren't schematics. They use L-System, which is some kind of turtle graphics. There seem to be two diffrent rules for creating the trees. Removing the one that does the big tree ought to help.
So the appropriate L-system needs to be modified ... although that would be a bit tricky and not as easy as changing a schematic.
moretees poplars have 2 different sizes and 2 different saplings. there's no technical reason that couldn't be provided for the oaks.
i first learned about l-system trees from kpt bryce, almost 30 years ago. minecraft's attempt is far worse than that early implementation.
minetest l-system trees are inspired by actual l-systems, but they're so terribly and arbitrarily constrained that i've never found them interesting to use. a big part of the reason they can't deliver is that the trees are only ever a few voxels in size. another reason is that leaves can interfere w/ the drawing of branches. if your tree is "reasonably" sized, the l-system rules don't give you much of a creative advantage over the schema trees, particularly when the schema make use of the ability to selectively remove certain layers.
ultimately, i want to offload tree creation to the async environment and do it in a more involved way which doesn't impact the performance of the main thread. sfan5 is working on a way to add lua code to mapgen threads, which will also aid in such a mechanism.