your-land/bugtracker
your-land/bugtracker
41
22
Issues 3.6k Projects 4 Wiki

ethereal.old_biomes disabled healing tree placement #7704

New Issue
Open
opened 2024-11-23 14:44:07 +01:00 by AliasAlreadyTaken · 1 comment
AliasAlreadyTaken commented 2024-11-23 14:44:07 +01:00
Owner
Copy Link

Upstream text:

Looks like the setting ethereal.old_biomes disabled healing trees in the biome they were previously generated in the "old biomes"

Wherever in my world I do deleteblocks at a position that previously was populated with those trees, they are now gone and replaced by pine trees.

https://codeberg.org/tenplus1/ethereal/issues/24#issuecomment-2463528

This was an accidental find. There may be more differences. Please test ALL biomes.

Last good for my world was 71adf29ddd07edab7d01ebea43df30de3b1caebf if you want to compare yourself. Or join the YL testserver on address your-land.de port 30001 and I'll show you there

--

Since my comment in Since my comment in wasn't apparently, I opened a new issue in https://codeberg.org/tenplus1/ethereal/issues/26 wasn't seen apparently, I opened a new issue in https://codeberg.org/tenplus1/ethereal/issues/26

Upstream text: Looks like the setting `ethereal.old_biomes` disabled healing trees in the biome they were previously generated in the "old biomes" Wherever in my world I do deleteblocks at a position that previously was populated with those trees, they are now gone and replaced by pine trees. https://codeberg.org/tenplus1/ethereal/issues/24#issuecomment-2463528 This was an accidental find. There may be more differences. **Please test ALL biomes.** Last good for my world was `71adf29ddd07edab7d01ebea43df30de3b1caebf` if you want to compare yourself. Or join the YL testserver on address your-land.de port 30001 and I'll show you there -- Since my comment in Since my comment in wasn't apparently, I opened a new issue in https://codeberg.org/tenplus1/ethereal/issues/26 wasn't seen apparently, I opened a new issue in https://codeberg.org/tenplus1/ethereal/issues/26
AliasAlreadyTaken added the
1. kind/bug
2. prio/critical
1. kind/breaking
 labels 2024-11-23 14:44:15 +01:00
AliasAlreadyTaken added this to the 1.1.126 milestone 2024-11-23 14:44:19 +01:00
AliasAlreadyTaken added the
3. source/mod upstream
 label 2024-11-23 23:18:26 +01:00
AliasAlreadyTaken commented 2024-11-24 21:28:19 +01:00
Author
Owner
Copy Link

Let's postpone ethereal and freeze on 71adf29ddd07edab7d01ebea43df30de3b1caebf or shortly after.

We'll update ethereal once it was fully tested upstream.

Let's postpone ethereal and freeze on 71adf29ddd07edab7d01ebea43df30de3b1caebf or shortly after. We'll update ethereal once it was fully tested upstream.
AliasAlreadyTaken removed this from the 1.1.126 milestone 2024-11-24 21:28:25 +01:00
Niklp self-assigned this 2024-12-14 20:11:21 +01:00
Sign in to join this conversation.
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)

  
3. source/petz

yet another petz bugz.

  
3. source/testserver

Originates on the testserver, no effect on main yet

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

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/possible close

Should be closed, but a second opinion is asked

  
4. step/QA main

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

  
4. step/QA NOK

Fix didn't yield the expected results

  
4. step/QA OK

tested

  
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.

  
kind/standalone

issues that don't depend on internal access and can be implemented as a stand-alone project

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/petz
3. source/testserver
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/possible close
4. step/QA main
4. step/QA NOK
4. step/QA OK
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
kind/standalone
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Niklp
1 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#7704
No description provided.
Delete Branch "%!s()"

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?