Warning: Code 30

There was an error code just now.

I clicked OK thinking I was going to get logged out but instead the game continued.

Should I close the game? What to do?

I honestly have no idea. I have not seen that code before and can’t find it in the Support Knowledge base or the internet.

If nothing bad happens just keep going. It may be related to battlenet communications protocols that sometimes flake out and DC. It won’t impact your game. If your game is having issues you would not be able to play at all.

I got the same code when I opened my first post-patch bounty cache. I went on to collect Cain and Aughild plans over the next 6 bounty caches, but 12 caches after those plans dropped…still no Captain Crimson. Exited out and logged back in, and first bounty cache had the CC plans! Probably coincidence and RNG, but that was my experience.

1 Like

i’ve got it sitting in menus. Friends have got it in-game. Doesn’t seem to affect anything. Click ā€˜OK’ and continue.

I had this error too. It was logged in the D3Debug.txt log file.

2019.08.21 00:36:08.387708200 ProcessClientRequest RPC failed with error:30, request:attribute { name: ā€œVersionā€ value { string_value: ā€œ2.6.6.61291ā€ } } attribute { name: ā€œCustomMessageIdā€ value { int_value: 271 } }
2019.08.21 00:36:08.393689400 WARNING: SendWarden3Custom error:30 attribute_spaceused:16481 msg:attribute { name: ā€œVersionā€ value { string_value: ā€œ2.6.6.61291ā€ } } attribute { name: ā€œCustomMessageIdā€ value { int_value: 271 } }
2019.08.21 00:36:08.398408900 >>> asdfasdf ---------------- ModalNotificationManager::SetOkNotification: There was an error. (Code 30)

Kinda looks like ā€œError 30ā€ is the new take on the classic BB8 from the Battle.net client, i.e. it’s the ā€œcatch-allā€ now.

They missed a golden opportunity not making it Error 42.

3 Likes

I got it too during a GR.

Got error 30 after clicking on stash. Was enchanting Wailing Host at Mystic, then unsocket amulet. Was moving to stash.

Googled ā€œdiablo3 error 30ā€ to come across a 2012:

The Diablo 3 Error LIST!!!
…
Error 28: Go outside
Error 29: We aren’t peddling the servers fast enough
Error 30: The error between 29 and 31
Error 31: We spent all our money on t.v. ads
Error 32: It’s ok we are calling Comcast about the issue
…

5 Likes

I got that too, while doing GR…
Apparently, it show up everytime i open the game, approximately 5min after start playing, and show only once per session.

Alright, this is odd indeed. Seeing what I can find out. Maybe another MVP has heard of this or I can get a TS response. Also a new Error 80 in the TS forum which I have not heard of either.

I’ve got the error 30 twice. Yesterday a few minutes after logging in sitting in town and today about 30 seconds after logging in and starting a bounty run.

I got the error code 30. Afterward I noticed that my health globe did not show lost health due to damage. I even had cheat death passive trigger and it still showed full globe (CDeath always empties my globe).

4 times last night. Once while in town, swapping gear. The other three in GRs.

Got it several times yesterday while playing Season end stash tetris.

Getting them frequently since patch . Not sure what it is but it’s beginning to be annoying as hell

1 Like

I’ve seen Error 30 popup several times since the patch but I didn’t think about reporting it because I assumed it was related to the wife’s Disney Circle device monitoring my every move on the interwebs. Glad to know it’s not just me. :slight_smile:

You never know! One of the most common crash causes in D3 is overlays and outside software. If it went from crashing to codes then that is an improvement?

Maybe?

I have run this through the Tech Support chain and a second Data Analyst person. It has been pushed forward, but given it is not stopping game play I don’t know that I will ever hear back.

Exactly what i thought, something like, an exception was captured and threw and error message. Not treated exception (not fixed, but circumvented)

I think its odd that didn’t happened on ptr…

I do too, but Blizzard sometimes works in mysterious ways. All I could do was push it to folks who could escalate. I don’t expect a fast fix. I am pleased it is not crashing games or corrupting data though.

To be honest don’t bother me at all.
Only happens once per session with me, usually 2-5min after i logged on, i could not notice any changes in game (reason or trigger for the error).
As it show a code, blizzard sure knows where to look.