There is an issue with “Game Start”, post-game update.
Account authentication and characters are authenticated and retrieved successfully.
Game will not start (appears update has bricked the game).
Blizzard please address asap or provide an acceptable work-around.
UPDATE: 25Oct2024
Fixed but then Blizzard broke it again?
This morning ~1000hrs(ACST) I successfully connected and was able “Start Game”. I didn’t have a lot time to spend on game play (5min), but by all indications worked as expected.
Then at ~1130(ACST) I logged back in to Blizzard and noticed D3 received a small update. Game is now bricked again with error code 30002 (same issue).
Blizzard, care to explain that one?
UPDATE: 25Oct2024
1300hrs(ACST) - error code 30002 was no longer present. “Game Start” successful.
3 Likes
Exact same thing happening with me 
Whereabout are you located ?
We had that error code in 2020; players in South America couldn’t launch D3 using their usual server (in Brazil, most probably) but could if they forced the use of the server in the US by adding the “OnlineService.Matchmaking.ServerPool=Default” argument.
See this post for a possible workaround: Error Code 30002 - #7 by Paton812-1159
Good luck !
adding the “OnlineService.Matchmaking.ServerPool=Default” argument
This worked for me. Thank you
1 Like
@Pepper : where are you located ? or more importantly… what server do you normally connect to ?
Glad that worked for you…
So i guess, the clients have been updated, but not the local servers? Shouldn’t they update the servers first before rolling out updates on clients?
1 Like
Yeah… I thought so… I used the « OnlineService.Matchmaking.ServerPool=AU1 » argument to connect to the Australian server and got the 30002 error:
Looks like something bad occurred to the Australian server pool. 
Not much we can do here… have to wait for Blizzard to fix it.
1 Like
Ooh boy. If they’ve switched off the Aussie servers I’ll be very slightly cross but also not surprised. There can’t be too many of us left in Au/NZ*. It must be a bit of a financial drain running servers for a few players**.
It’ll be interesting to see if this is intentional.
* don’t be offended, Cascade. 
** wHeRe Is oFfLiNe MoDe?!
1 Like
Just uploaded it and got the same thing …30002
Zurtle i seriously hope not. Cannot run D4 on my computer but still enjoy playing D3.
Have enjoyed Diablo from day 1.
i think there are plenty of us left in Aus/NZ
But I’m having this issue too
Have you tried using the NA server as I suggested above ?
It’s highly unlikely a regional node was eliminated without notice. Every time in the past when they have been combined/consolidated, Bliz overtly announced it ahead of time.
Plus it’s highly unlikely Bliz wouldn’t code them out of the client, and instead rely on a command line that the vast majority don’t know about.
It’s funny where some people’s minds immediately go.
1 Like
The ways of yesteryear are now gone… just look at the current state of technical support and compare it to what it was before the acquisition by Micro$oft.
If you haven’t heard anything through your channels… who knows what is really going on?
True.
I do concede that its possible that D3 could not receive the code changes, but something like a node cluster going away is quite a big change that would affect all Bliz games.
I haven’t heard anything yet. But I will forward these reports on in case they get overlooked here.
1 Like
Also in Australia, so experiencing the same issue. The frustrating thing is that connecting to the US server for at least the past week gives me a higher ping than it’s ever been before. I used to get a ping of maybe 250ms and now it’s typically 380. Inventory/stash won’t display immediately and can take a couple of seconds to display.
Yes… that is expected due to the increased distance the data must travel to and from the servers. Also, there is only so much bandwidth that can be carried through the undersea cables… the latency will likely increase during “peak hours”. Hopefully, this is a temporary situation.
I understand why it’s higher than being connected to the Australian server. My point is that for some reason connecting to the US server is higher than when I connected to the US server in the past. 380ms vs 250ms both to US.