BlueTracker

Hello everyone!

Reset is coming up quickly and we wanted to give some insight into some things players will hit.

1. Servers will most likely come down between 4:00PM and 4:30PM PST for players and come back up roughly at 5:00PM PST.
2. Once the update is complete players might have to start the client with “Run as Administrator” to pick up the Ladder correctly

We’ll update once the Ladder Reset is live and ready! Have fun!

Hello!

There’s no patch, just a ladder reset on the servers itself. Just in case people haven’t updated in a long time, that’s why we put the note for #2.

Ladder should be reset and good to go.

Have fun slaying demons >=)

Hey!

We’re looking into some issues with our game servers not liking us at the moment.

We’ll let you know asap when we’re back up and stable!

Hello again!

Some of our servers were getting slammed with players and were hanging a bit. We’ve restarted those and should be coming up, if not already up.

Let us know if anything out of the ordinary is happening.

Thanks again

Hey JaeDong,

We’re going through each realm right now and fixing up the servers that were getting hit hard by players logging in. With the legacy system of Diablo II, it doesn’t offer great error codes to the players. For example: Unable to Connect to Battle.net, could be numerous things, but in the end to the player, it means they can’t login right now.

As we go through the individual servers on each realm, some might come down and come back up over time. To the player, this means that they’ll get a disconnected message but then be able to join a game again once back in the main menu.

This manual process will take a little bit as we stabilize the servers. Once stabilized, we should be clear of any issues outside the norm of Diablo II

Thanks for sticking through this with us

Hey!

We’re looking into some issues with our game servers not liking us at the moment.

We’ll let you know asap when we’re back up and stable!

Hello again!

Some of our servers were getting slammed with players and were hanging a bit. We’ve restarted those and should be coming up, if not already up.

Let us know if anything out of the ordinary is happening.

Thanks again

Hey JaeDong,

We’re going through each realm right now and fixing up the servers that were getting hit hard by players logging in. With the legacy system of Diablo II, it doesn’t offer great error codes to the players. For example: Unable to Connect to Battle.net, could be numerous things, but in the end to the player, it means they can’t login right now.

As we go through the individual servers on each realm, some might come down and come back up over time. To the player, this means that they’ll get a disconnected message but then be able to join a game again once back in the main menu.

This manual process will take a little bit as we stabilize the servers. Once stabilized, we should be clear of any issues outside the norm of Diablo II

Thanks for sticking through this with us

Hey Olivie and others,

We’re still looking into some areas to stabilize the game servers a bit. I would suggest after every game waiting 5-10 seconds before starting a new one.

There’s a multitude of old legacy bugs that are a pain point for the community.

• Temp restrictions when spamming games/chat
• CD key restrictions or used by self from numerous random occurrences
• Failed to Join game when entering and leaving too fast

Probably not the best answers in the world. The CD restrictions and being used by “Self” should clear up anywhere from 15min to a day, there’s unfortunately no way to purge this on an individual or large scale with the legacy system.

I hope this clears up some and provides answers. We’ll have more updates once we stabilize things further.

Understood Olivie!

We’ll check it out and report back, thanks for the update and more information

Hey Olivie and others,

We’re still looking into some areas to stabilize the game servers a bit. I would suggest after every game waiting 5-10 seconds before starting a new one.

There’s a multitude of old legacy bugs that are a pain point for the community.

• Temp restrictions when spamming games/chat
• CD key restrictions or used by self from numerous random occurrences
• Failed to Join game when entering and leaving too fast

Probably not the best answers in the world. The CD restrictions and being used by “Self” should clear up anywhere from 15min to a day, there’s unfortunately no way to purge this on an individual or large scale with the legacy system.

I hope this clears up some and provides answers. We’ll have more updates once we stabilize things further.

Understood Olivie!

We’ll check it out and report back, thanks for the update and more information

Se aparece que este hilo es un poco viejo así que vamos a cerrar este hilo en particular, pero si quieres continuar esta conversación o empezar una conversación nueva, puedes crear un hilo nuevo. ~ El Equipo de Moderadores