mrminer reports: more ongen sapling here ... #6307
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6307
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?
mrminer reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
vote: should we report defunct ongen saplings as an issue upstream (fixed via ABM/LBM), or just manually use admin powers to re-place them?
Is that an ongoing mapgen bug in .... wherever they come from?
If yes, then other servers and worlds suffer from the same issue and we need to report it upstream.
If no, why does it happen in ours?
If this is only a local phenomenon (those 20 map blocks north of Aqueron), then we can do it manually.
If they could happen in places we don#t know of, we should fix codewise.
I’ve done a good bit of exploring recently and there are definently more areas other than that one
couldn't one write a script that replaces all detected ongen saplings in the world with their regular counterparts?
Aren't ongen saplings replaced by trees eventually anyway as soon as they get the time to grow? Or was something changed so that they can't anymore? It ought to be normal to find ongen saplings in newly generated areas. If the player moves through fast enough then the sapling won't have time to grow.
It means players could pick up those ongen saplings and use them elsewhere. It might also help to "drop" a normal sapling if an ongen sapling is dug and to place a normal sapling if an ongen sapling is placed by something other than mapgen
That's already the case...
9a6c64d163/node_defs.lua (L501)
That's what I experienced too: I've dug quite some ongen saplings so far, but never got one. It's always the normal one...