mod request: more cool trees? #2086

New Issue

Closed

opened 2022-06-17 19:34:41 +00:00 by flux · 3 comments

flux commented

2022-06-17 19:34:41 +00:00

Member

Copy Link

we've got the modpack, but only mahogany is enabled? why not more of them, particularly ones that aren't redundant w/ existing trees?

e.g.

baldcypress
cacaotree
cherrytree
chestnuttree
clementinetree
ebony
hollytree
jacaranda
larch
maple
plumtree
pomegranate

we've got the modpack, but only mahogany is enabled? why not more of them, particularly ones that aren't redundant w/ existing trees? e.g. * [ ] baldcypress * [ ] cacaotree * [ ] cherrytree * [ ] chestnuttree * [ ] clementinetree * [ ] ebony * [ ] hollytree * [ ] jacaranda * [ ] larch * [ ] maple * [ ] plumtree * [ ] pomegranate

flux added the

1. kind/enhancement

label 2022-06-17 19:34:41 +00:00

AliasAlreadyTaken commented

2022-06-17 23:04:32 +00:00

Owner

Copy Link

Some time ago we had considered adding new trees, with a tree show on the testserver to see how they look like.

The drawbacks are that only newly emerged areas get their spawn and we haveto integrate them in the "wood supply chain", like fences and stuff.

Some time ago we had considered adding new trees, with a tree show on the testserver to see how they look like. The drawbacks are that only newly emerged areas get their spawn and we haveto integrate them in the "wood supply chain", like fences and stuff.

flux commented

2022-06-20 01:29:22 +00:00

Author

Member

Copy Link

The drawbacks are that only newly emerged areas get their spawn and we haveto integrate them in the "wood supply chain", like fences and stuff.

generalized tree regrowth logic is something that's still planned, right? i think we can do that w/ an ABM that doesn't cost too much.

the "wood supply chain" is certainly an issue - players will ask for node variants. but we can just say "no" if it's too much.

> The drawbacks are that only newly emerged areas get their spawn and we haveto integrate them in the "wood supply chain", like fences and stuff. generalized tree regrowth logic is something that's still planned, right? i *think* we can do that w/ an ABM that doesn't cost too much. the "wood supply chain" is certainly an issue - players *will* ask for node variants. but we can just say "no" if it's too much.

flux added this to the flux's TODO list project 2022-07-02 22:23:47 +00:00

flux added the

1. kind/node limit

label 2022-09-11 00:22:24 +00:00

flux added a new dependency 2022-10-30 20:27:27 +00:00

your-land/administration#147 - Nodecount

flux added the

5. result/wontfix

label 2024-03-11 18:15:03 +00:00

flux removed this from the flux's TODO list project 2024-03-11 18:15:06 +00:00

flux commented

2024-03-11 18:17:37 +00:00

Author

Member

Copy Link

closing this as we've discovered that at least some cool_trees assets are ripped from other sources with incompatible licenses, and we'll have to remove them. see your-land/administration#209

closing this as we've discovered that at least some cool_trees assets are ripped from other sources with incompatible licenses, and we'll have to remove them. see https://gitea.your-land.de/your-land/administration/issues/209

flux removed a dependency 2024-03-11 18:17:45 +00:00

your-land/administration#147 - Nodecount

flux closed this issue

2024-03-11 18:17:50 +00:00

AliasAlreadyTaken added the

3. source/license

label 2024-03-12 01:46:00 +00:00

No Branch/Tag Specified

Branches Tags

Labels

Clear labels

1. kind/balancing

Depends on balancing

1. kind/breaking

something that alters or disables an existing game mechanic

1. kind/bug

Something is not working

1. kind/construction

A build needs fixing

1. kind/documentation

Needs proper documentation

1. kind/enhancement

New feature

1. kind/griefing

players despoiling builds or nature

1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

1. kind/meme

issue is mostly a joke

1. kind/node limit

something which works for or against the node limit

1. kind/other

Something not within the other kinds

1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

2. prio/controversial

not likely to happen w/out a lot of discussion

2. prio/critical

Very important

2. prio/elevated

something players are eager to have fixed

2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

2. prio/low

Not so important

3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

3. source/engine

Issue is due to a bug or feature of the minetest engine

3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

3. source/license

A licensing problem is involved

3. source/mod upstream

Problem is upstream (not engine/client)

Alias has approved this feature, someone should implement it

4. step/at work

Being worked on

4. step/blocked

we plan to do this, but other work has to be finished first

4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

4. step/help wanted

Need some help

4. step/needs confirmation

4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

4. step/question

More information is needed

4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

5. result/cannot reproduce

5. result/duplicate

This issue or pull request already exists

5. result/fixed

problem is fixed

5. result/maybe

not planned currently, but maybe some day

5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

ugh/petz

yet another petz bugz.

ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

ugh/QA NOK

Fix didn't yield the expected results

No Label

1. kind/documentation

2. prio/controversial

2. prio/critical

2. prio/elevated

2. prio/good first issue

3. source/integration

3. source/lag

3. source/license

3. source/mod upstream

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

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

2 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#2086

Reference in New Issue

Repository

your-land/bugtracker

Title

Body

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?