debian44 reports: Dupe: If a cottages:pitchfork ... #670
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#670
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?
debian44 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Hi,
looks like I cannot reproduce the bug, can you show me again how to do it?
Gretings, Alias
Compare #717
I cannot reproduce this. Possibly this was just lag? I can't reproduce it when there's lag either, though.
Suggest:
source/lag
andresult/cannot reproduce
.I can reproduce if I place and dig in quick succession. From the dtimes you can see there is no terrible lag.
I was able to replicate this too now, and the fix to #717 doesn't change this behavior.
I pushed some code to yl_commons that I think fixes the issue, though I never really found a great way to replicate the duplication reliably.
8996fa3a25
Alias, could you test whether the duplication still happens when using that commit?
In a low lag environment it seems to be fixed :)
seems fine to me, and live now.