D2R never fails to surprise

I was about to start an online non-lobby game, and after I clicked Hell labeled button to select the difficulty I got this error message I've never seen before.
As far as I know the game name was supposed to be automatically assigned by the server following this format Gamennnnnnnnnn. I clicked Ok labeled button and attempted again with the same result. Selecting Nightmare and Normal difficulties did not alleviate the problem. What's up with that, huh?

Edit: Starting the game from the lobby didn't help either.

i switch to different server asia/na, login successfully then switch back to original and be able to start game

I had the same issue on xbox trying to make a private game (where it also auto-generates the game name). I close D2R, loaded a different game, and reloaded D2R and it worked.

I just decided to give the game and myself a break for now.

Or you could just not make game names with profanity in them

…

I am kidding of course!

Regardless - keep in mind that this game was made by a small indie company.

(I’ve seen others having this problem on NA too recently - bloody weird server bug if I ever saw one lol)

It's been happening to me, seemingly arbitrarily, the past few weeks(tops) even on private games that I've been making for years. I just relaunch the entire game and it fixes it.

I really understand how frustrating and inconvenient this situation must be, and I’m not trying to downplay that at all. That said, maybe simply changing the game name could help ease things, and it might not be quite as serious as it feels right now. I’m just hoping we can find a way to look at it from a calmer place.

Got the same issue a couple of days ago as well, restarted game and bnet and went fine.

I had the same issues for 3-4 times recently. All attempts from character page and from lobby with game name all failed at the same info.

It only solves when I closed game entirely and reopens (I didn't change server)

just quit game and launch again xD

MintBlancmanche wrote: 2 weeks ago

just quit game and launch again xD

I did that to no avail. After I closed the game again, but this time along with the battle.net app, I got back to normal.

bigbikefan wrote: 2 weeks ago

I did that to no avail. After I closed the game again, but this time along with the battle.net app, I got back to normal.

maybe you just got unlucky 2 times in a row, relaunching usually is enough.

Knappogue wrote: 2 weeks ago

I had the same issue on xbox trying to make a private game (where it also auto-generates the game name). I close D2R, loaded a different game, and reloaded D2R and it worked.

Same here. After 4 attempts with different chars, closed the game and it come back to normal.

ShadowHeart wrote: 2 weeks ago

Or you could just not make game names with profanity in them

…

I am kidding of course!

Regardless - keep in mind that this game was made by a small indie company.

(I’ve seen others having this problem on NA too recently - bloody weird server bug if I ever saw one lol)

I get the message and I don't have any builds with anything even close to profanity in their names, and yesterday I got hit with the same message repeatedly. Even took a screenshot. Notice the build and game name is Sagi?

Dnasty225 wrote: 2 weeks ago

I really understand how frustrating and inconvenient this situation must be, and I’m not trying to downplay that at all. That said, maybe simply changing the game name could help ease things, and it might not be quite as serious as it feels right now. I’m just hoping we can find a way to look at it from a calmer place.

No, it's been happening to me, and it has nothing to do with the actual game name. Some kind of server-side bug. You just have to wait it out.