Shadow reports: death due to timeout/lag durin ... #4821
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#4821
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?
Shadow reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Seems like there was some disconnect on the network side of things. If that happens not on the YL network and more people are disconnected at the same time, that's not much YL can do about it.
I still don't like that people suffer disadvantages from bad network, most often they can't do anything about their network, too. "Move into an area with better network" or even "place your PC closer to the wifi router" is much harder to accomplish than buying a better PC or replacing a faulty hardware thing.
There was an idea to roll back death or similar disadvantages when the person gets disconnected, but that could be gamed: Simply rip out the network when you die. Means: Currently no good solution.
we're currently running some code that relays messages sent to players if they time out - measured as 60 seconds before they disconnect w/ a "timeout" flag. that could be re-worked to automatically refund XP if the player dies while timed out, though that'd be a bit complicated. open a new issue if you think that's what we should be doing.