whostand reports: unknown node under Heaven "ill ... #4694
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4694
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?
whostand reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
set up an LBM to remove old illumination nodes:
9c9f19e224
QA: The "unknown block" is still present at the location indicated by whosit. There is no trace of the LBM running in the profiler. maybe we should add logging to it, where it replaced something?
Maybe
run_at_every_load = false
prevents it, because somehow the LBM already ran on the mapblock without this? Where is it stored that a LBM already ran here?there's a file called "env_meta.txt" in the world folder, which has a record called
lbm_introduction_times
, with name/timestamp pairs for when various LBMs were introduced. these timestamps are compared against the modification timestamp for the mapblock in the map DB.i visited the location where the bug was recorded and couldn't find the node. i don't see the LBM listed in the profiler output, but the test server's only been up for 8 days when i write this, so it might have run on an earlier boot?
this is live - the unknown nodes are gone.