AspireMint reports: Drowned in nether because of s ... #6655
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6655
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?
AspireMint reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
And no, its not in my internet connection.
Great i can look at my bones.
max lag: 1.94s ... something was going on there, enough to kill. Let's refund xp and items and investigate.
No idea what max lag means, but this lag was like 20-30 seconds long. I could swim around my bones taking pictures.
Max server lag.
I saved the items, they are in the Haven Town Hall
I and Pilo also reported a massive lag spike around that time, although max_lag didn't seem to reflect it. I personally assumed it was tied to something like the memory issues.
i wonder what could cause an apparent 30 second lag spike that doesn't show up on in either
max_lag
ormax_rtt
. maybe packetloss? there might be a way to measure that with a protocol change - everything packet musk SYN-ACK and ACK like TCP, and we record a count of anything that doesn't? but we only track those states for statistics, so as to not make transmissions even laggier?to be sure, i don't want to accuse AspireMint of lying or exaggerating, this isn't the first time this has happened, and i've also had "surprise" deaths that didn't add up w/ the metrics.
but i do want to opine that trying to survive the nether by swimming under the lava with a gilly staff should not be considered predictably safe. the nether is dangerous in many ways. intentionally, one of those is that it's less predictable because of lag. go slow, be super cautions, have escape plans. i haven't taken down a dragon in years, but it was hellish when i did, and i died a lot. killing dragons and balrogs are just not things that advanced players can do safely unless they time things to just after a level up.