poppyasdan reports: my stuff didnt go into bones j ... #6044
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6044
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?
poppyasdan reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Clearly a bug, the items were refunded. Still, why didn't the bones generate, although the log says so?
was there gravel or sand that was in that area ? last time my bones didn't generate there was gravel where they should have been.
apparently
set_node
failed somehow - the items got added to the metadata of the air node at that position:i'll add a check to ensure that the node is actually a bones node before doing anything further.
hopefully this will fix such a problem:
77f1cc7c17
i'm not sure how to test this. trying to modify even unloaded mapblocks should end up modifying them anyway... unless perhaps there's a race condition while cuz the mapblock is already loading?
i'm assuming this is live, even though we don't really have a way to test it