daydream reports: I just placed a chest and it d ... #5292
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#5292
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:
I went and got another one and put it in the spot and the original chest reappeared and the new one I was attempting to place remained in my inventory.
STRANGE.
There was sorta bad lag at the time which I noticed while using replacer (stone -> clay) and moving stuff around... it was probably that. Not likely able to recreate the anomaly as if it was commonplace I would have run into it before... and I may have? like one other time in 18 months? Sign, pedestal and shop loading are pretty slow right now too... really over due for mem leak reboot I suspect.
meh
I did the /bug when the chest disappeared - if I knew it was going to-reappear when I tried to put another one there, I probably wouldn't have bothered tbh.
Ah! You thought you had placed a chest - but it was a mime which had slipped into your inventory and went away after you released it.
Seriuosly: If there was bad lag that might really have been the reason. Your client probably didn't receive the update of the mapblock with the chest having been placed.
This was 100% because of lag. Around that time the server was lagging horribly.
I agree, I just never really saw that before, but I think it was just lag... this can be closed.