Ok, so, I’m not one of those guys who goes to notify devs, or direct comments to devs (outside of my great Ghostbaning comments), but I thought I’d post something about an issue I’m having with the game.
For a while now, I’ve been having issues when I transition from one area to the next. Say, for example, I’m running quests in Gianthold. I transition from the Marketplace to Gianthold just fine. I transition from the public area to the private area just fine. Then, I go to step in a quest, I get the status screen, and then…nothing. I just close off the program (I run in windowed mode), and re-log. When this happens, I end up in the area that was my destination. So in the example above, I would be in the beginning of the quest that I entered. This seems to be random. It doesn’t always happen at the same time, or the same transitions. There has been nothing to really hang my hat on when it comes to seeing a pattern.
If I were to sit on that transition screen, the connection would eventually time out and I’d get booted from the game. I tested this in the past.
I’ve been wondering for a while now what it was that was causing the problem. I tried re-installing. I tried switching to a different wireless router. The only thing I haven’t done was connecting via wired Ethernet which I haven’t done for various reasons. The problem is annoying its worst.
So, last Friday I’m running with some guildies and friends. Sure enough, I had to re-log three different times over something like 5 quests. However, two other people in the group had the same EXACT problem, with the same EXACT transitions. One of them was going from the Gianthold wilderness area to Maze of Madness.
Three people. Three “lock-ups” on the same three transitions…all in a row. That’s TOO much of a coincidence.
Anyhow, I know there are people out there experiencing the same thing. I thought I’d throw this post out there to see if any of the devs are interested in possibly resolving this. But what I have determined is that this pretty much rules out the client machines as being a source of the problem. I’d also rule out the actual game client, given the conditions needed to create this same issue client-side.