RoTW Bug - character list empties every time I leave the lobby

Hi

Are you also having this problem?

Every time I leave the lobby, my character list empties
In D2R (non-RoTW), switching tabs (Online -> Offline then Offline -> Online), reloaded the character list...
But now on RotW, this "trick" doesn't work... I need to click "Create New" and then "Back", for the character list to reload...

Every now and then I run into this error. But it’s always been a one-time thing.

It used to happen occasionally, now it happens all the time

fredkid wrote: 2 weeks ago

Hi

Are you also having this problem?

Every time I leave the lobby, my character list empties
In D2R (non-RoTW), switching tabs (Online -> Offline then Offline -> Online), reloaded the character list...
But now on RotW, this "trick" doesn't work... I need to click "Create New" and then "Back", for the character list to reload...

I've never seen that one before. I would generally ask what operating system you're using, because then it's usually Microsoft's fault, but since D2r RoTW was recently patched by Blizzard, it gets confusing over which one to blame, unless this has been gong on since before pre-RoTW, and then I would just blame them both.

Windows 11

Yes, this issue happens to me occasionally when I dared to venture onto EU servers.

mhlg wrote: 2 weeks ago

fredkid wrote: 2 weeks ago

Hi

Are you also having this problem?

Every time I leave the lobby, my character list empties
In D2R (non-RoTW), switching tabs (Online -> Offline then Offline -> Online), reloaded the character list...
But now on RotW, this "trick" doesn't work... I need to click "Create New" and then "Back", for the character list to reload...

I've never seen that one before. I would generally ask what operating system you're using, because then it's usually Microsoft's fault, but since D2r RoTW was recently patched by Blizzard, it gets confusing over which one to blame, unless this has been gong on since before pre-RoTW, and then I would just blame them both.

But... Blizzard is Windows now.. Heheh.

Twice faster than my method

Myrana wrote: 2 weeks ago

I have this issue every 3rd or so login myself. I used to close and restart the game to fix it, until I figured out that I could simply click on "Create New" -> Escape and then it loads the characters correctly.
At least so far it worked for me every time.

torshakle wrote: 2 weeks ago

mhlg wrote: 2 weeks ago

fredkid wrote: 2 weeks ago

Hi

Are you also having this problem?

Every time I leave the lobby, my character list empties
In D2R (non-RoTW), switching tabs (Online -> Offline then Offline -> Online), reloaded the character list...
But now on RotW, this "trick" doesn't work... I need to click "Create New" and then "Back", for the character list to reload...

I've never seen that one before. I would generally ask what operating system you're using, because then it's usually Microsoft's fault, but since D2r RoTW was recently patched by Blizzard, it gets confusing over which one to blame, unless this has been gong on since before pre-RoTW, and then I would just blame them both.

But... Blizzard is Windows now.. Heheh.

Exactly!

Same issue. I find that it occurs if I press ESC too quickly after leaving a game. Something about not letting the Lobby load so it doesn't load your Characters when you back out cuz something was broken.

I found that if you just delay your Exit by half a second, the issue typically goes away. *Moreorless, wait for the lobby to load before backing out.

Happens all the time.
Also happened all the time before RotW though.

"Create New", ESC
is the way to go

Myrana wrote: 2 weeks ago

I have this issue every 3rd or so login myself. I used to close and restart the game to fix it, until I figured out that I could simply click on "Create New" -> Escape and then it loads the characters correctly.
At least so far it worked for me every time.

If you made/joined the game via the lobby, then when exiting a game you first get back to the lobby screen. If you try to exit the lobby back to the character select screen before your own character has finished loading in the center of the lobby screen (your own character is standing in the center of the lobby screen, other players hanging out in the lobby are displayed at the bottom), then you get this issue. It happens more commonly when you’re not in your usual region cause loading the lobby screen is slower with higher ping. There’s an easy fix with create char > esc as others have noted, but you can also make sure to wait on the lobby screen until your own character loads before hitting esc to get back to the character select screen. It shouldn’t take more than a second or two tops, just a fraction of a second usually on your home region (but you can still be too fast with that esc

Key sometimes).

Its just a lag between the servers and your client. I panicked the first time got it, thought I had lost all my darn characters. Luckily they were there after a quick restart :'D

I think this wasnt a thing in original diablo 2, at least cant remember it happening there.

ShadowHeart wrote: 2 weeks ago

If you made/joined the game via the lobby, then when exiting a game you first get back to the lobby screen. If you try to exit the lobby back to the character select screen before your own character has finished loading in the center of the lobby screen (your own character is standing in the center of the lobby screen, other players hanging out in the lobby are displayed at the bottom), then you get this issue. It happens more commonly when you’re not in your usual region cause loading the lobby screen is slower with higher ping. There’s an easy fix with create char > esc as others have noted, but you can also make sure to wait on the lobby screen until your own character loads before hitting esc to get back to the character select screen. It shouldn’t take more than a second or two tops, just a fraction of a second usually on your home region (but you can still be too fast with that esc

Key sometimes).

Ah, okay. So it's specifically the character loading. Makes sense. Always knew it was from something not finishing the load.