daydream reports: one of my lociked chests says ... #4304
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#4304
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?
daydream reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
that indicates that the chest was "constructed" but not "placed"
1e237b8d18/mods/default/chests.lua (L93-L104)
this can be done by e.g. the following lua code:
i'm not sure how the chest ended up like that though, i don't think daydream was placing chests via lua. node replacement tools seem to properly initialize them.
one thing to beware, this probably means that the chest doesn't actually have an owner, and so is not actually locked - anyone will be able to use it.
@daydream what are the approximate coordinates of the chest, so i can take a look at it? there was nothing where the bug was reported.
hm, i found some of these weird chests, they do have an owner, so my previous theory isn't right...
The replacer goes around the usual "on_place" mecahnics, could this tool be responsible?
This could have also been caused by the shared chest function which let's you change the chest type on left click on a chest while wielding a shared chest. At least in the past this used to cause shared chests created through this way to not have the "owned by..." part in the infotext.
EDIT: cf. #3287
i tested that, and it doesn't seem to be responsible. JeCel's explanation sounds plausible.
yeah that's exactly the issue. steps to re-create: