55s don’t currently drop on live or are so rare no one that I know of has gotten a single 55 item.

This post was edited by FirstDoorFail on Aug 29 2018 08:18pm

wheres the 55s?

This post was edited by Apot on Aug 29 2018 08:24pm

Yeah I'm pretty sure he's still looking at everything in this thread and working on them. I'm sure he'll have an answer for the 55 issue soon .

Here's whats causing development problems in my opinion:

1 person says he has a problem.
2nd person says he has the same problem. (this should be enough for Paul to look into it, posting more is just whining at this point)

3rd person says he's perfectly fine, no problem whatsoever. This guy usually hasn't played nearly as much as everyone else (either you have the problem or you don't, no need to know about the people who don't).

4th person states he has the problem to prove that it's actually real.
5th person states he has the same problem or something similar to show that we're not just making this up.

Njag sees the problem (I presume) and determines if it's relevant or not. Meanwhile the 3rd guy triggers everyone else to post about it and by the time Njag looks at the post again we all look like whiners.

Let's not be that 3rd, 4th or 5th person.

Paul gets irritated and we all get left out of the loop from what he's doing.

Solution: 1 or 2 posts about a problem should be enough. Exception: I do think it is valid to say that most of the people I've talked to or played with in LS in the past few days have been suffering from spontaneous instant disconnects. Not that this necessarily has anything to do with Paul's work or the LS server at all. It could be the middle man. It is something that is happening and solutions come with time.

This post was edited by Bob888 on Aug 29 2018 08:36pm

Could be a number of issues. Firewall settings, ISP routing...a bunch of things. My point was mostly that using Logical Troubleshooting you can determine that the issue is not server side as it's only happening to random people at random times. This means that the client is dropping itself from the server for reasons unknown to me. If we had issues where everyone was dropping all at the same time we could determine that it is a server side issue.

I would go to the link Paul provided and do some research on Cloudflare and see if anyone else has had similar issues. There is a fix out there, I'm not sure what it is for each individual user, but if you mess with your settings enough, eventually you will see better results.

Thanks Paul, but that proves basically that everyone was right. As you stated it is not the LS server itself, but your change to use websockets with cloudflare for the rewritten code. And people are right because connections may drop due to cloudflare terminating websockets. I already was suspecting something like this, because the report of occasional drops happened from all over the world and not just one region. As being an IT professional myself I know what a hassle it is to pinpoint network issues.
You are maybe not able to do anything about it and we are unable aswell, buy this holds a major problem for doing mirror maze. Currently it is a raffle because no one knows if you drop or when you drop,but for my observation it happens to at least one random guy per climb.

Maybe you can do something like when connection ia dropped an reestablished within 2minutes you get a prompt upon login to rejoin your group and directly to catacomb while everything else is blocked to use until you answer it. That would make mirror maze possible again without having to deal with the problems cloudflare is causing to everyone

Nowhere did Paul say they weren't disconnecting and they were making it up. He did repeatedly say that it wasn't his fault, the d2jsp servers or network. This proves them wrong, because this topic is a beta bugs report topic specifically about the LS server, and they keep posting here telling him to look into it, and/or fix it, when it's 100% outside of his control.

The technical implementation of what you're suggesting to reconnect and save the state after a disconnect is hideously complex to the point where it is very unlikely it will ever be done. I can see some mirror maze specific changes being possible but nothing as drastic as you suggested. Paul is already looking into this.

Please keep all "connection issues" and single user drops OUT of this thread. Unless everyone on the entire server gets disconnected this is a NETWORK issue not a ladder slasher bug and should not be posted in this thread. Take this as your final warning, this has already been addressed multiple times, further posts/complaints about this will lead to suspensions.

Thanks for fixing 55s Paul

Amen

I know that this would be complex and maybe too much for this game and this playerbase, but I only wanted to bring up the point that mirror maze is a problem, because of the problem-we-are-not-supposed-to-talk-about-any-longer.
But it is really nice to hear, that he is working on a more doable solution.

Btw. that fix for the char select thing after mq seems to be fixed. Tried to replicate it the last mqs I did, but couldnt do it anymore.

Same I think it’s gone