This is the second time i’ve been online and in a game when suddenly the game closes to perform an update. If you’re going to update the game while people are playing it, how about broadcast a warning a little before it happens? Would be really nice…
(Don’t get me wrong, i’m happy that patches are going out to fix stuff, buuuut, im not happy that im suddenly forced out of the game in the middle of fighting a boss etc…)
That should not happen. I have been in game most of the day and have not gotten kicked to update.
In your Launcher settings you may need to adjust it not to update while you are playing games. Under Settings > Download make sure the box is checked to pause updates when playing.
seems when i installed D2, somehow the updates setting changed from “do not automatically update” to “game specific settings” with D2 having automatic updates on and the other installed games not.
Glad you found the issue! It may have been on install day where you were waiting anxiously for it to update and begin Many people changed settings that day to make sure they caught the install push - or game day push.
Yes, holy hell is it annoying!
If I had known they were about to do an update I wouldn’t have been wasting my time continuing, I would have grabbed the waypoint and logged out.
Actually, I’m certain I never touched those settings at that time. I just clicked the button when it changed from “not available” or whatever, to “Install.” (And then later from the same, to “Play” on release day)
There might have been an oversight where Blizzard ended up coding the single button clicks to override current settings for D2R so the average player would automatically get the updates instead of complaining about not being able to play. If this is true then there should have been a check regarding current global settings and apply those to D2R. However, This is just me speculating with what knowledge I have of how things are coded.
It is strange it would be on by default, but regardless. Now you know where the settings are and can make sure you have it set to NOT update when you are in a game.
You can even turn off automatic updates totally if you want.
I wonder if it wasn’t just the usual crash followed by the update starting because I wasn’t playing anymore.
I only crash a few times a day and usually when I’ve been alt tabbed for a while, so I didn’t expect that to have been the cause though.
The disconnects are what hurt the most. I can’t even play using the play button because it gives me a randomized game name and if I get disconnected (which is very painfully frequent) I can’t rejoin it. I wish you could set a few randomized game names to use when you click play instead of it just being a string of numbers.
That is certainly possible. I have been in game straight since about 11am Eastern (with lots of AFK) and have not gotten the dreaded crash or an update yet… Of course now that I say that you know what will happen.
EDIT - IT DID! It just crashed, not a few mins after I posted that. I cursed myself!
That’s how it was before, I expect what Athelwynn said may be the case- that the app turned on updates for D2 when i installed it, overriding the “no automatic updates” setting with “game specific settings” and turning updates for D2 on while leaving the others off.
It’s not a crash. It’s the exact same behavior as pressing Alt-F4. freeze for like half a second and then poof gone.
An actual crash would have triggered the crash reporter tool. it would have also been more abrupt than the slight pause (probably to update the save to the server so you can’t abuse alt F4)
And EVERY TIME this has happened, there was an update waiting. That’s not a coincidence.
Ahhhh this is awesome. I haven’t been kicked from a game due to this but if this takes care of that issue the OP has definitely good to do. I seriously didn’t know this would prevent that (unless obviously a server restart which should always be announced)
I was gonna say something similar, last 2 crashes, just had one a few hours ago(right after saying I haven’t for awhile), I had an update waiting. I assumed it’s just I wouldn’t have noticed it if I didn’t crash. It did feel like the update push crashed me but that’s just the feel.
Not always, not at all. There are lots and lots and lots of reports on Tech Support and on here about crashes to desktop without an error code. Tons.
Not every crash has a cause the tool can identify and report. Sometimes it all just goes poof.
There has been lots of little patches lately, but they did not cause the crash. That would be a terrible game mechanic if the launcher did that! All players in all Blizz games would be furious.
Possibly. But again, Each and every time this happened, t here was an update just waiting to be installed. I don’t think that’s a coincidence.
The difference between this and other games is they generally necessitate server maintenance for updates, so you never really run into this situation. But Diablo II can get client side updates that don’t require a server change.
This doesn’t happen in other games because you generally can’t be in the game when an update is happening.
Ironically, if you leave auto-updating turned on, it can do just that and screw you with the background download which it then tries to live patch (often ending up with corrupted files as a result). My guess on why we don’t have a system warning before an update is because VV hasn’t actually finished the social feature set that is tied into Battle.net. It’s all held together with chewing gum and fishing line right now.
Three rules to follow if you want the most problem free experience in all Blizzard games:
Turn off automatic updates and disable background downloads of future patches. Leaving those two things active is a surefire way to get booted ungraciously and/or end up with corrupted files which can cause crashes that the error reporter tool can’t pick up on (i.e. you get booted to the desktop out of the blue).
Set the Battle.net desktop app to shut down when launching a game. Leaving it open in the background has the same effect as using an overlay - it makes the game unstable. This is a problem on both Windows and macOS.
Never, ever, ever click the Play button until patching or installing is 100% done and there is no longer any update activity happening. Failing to heed this rule will corrupt your files at some point. It’s only a matter of time. It’s one of the pitfalls of CASC. Do. Not. Click. Play. During. Updates.
Patience is a virtue that is extraordinarily beneficial here. The time you spend waiting for the patching or installing to completely finish is less than the time you lose in queues or having to scan and repair due to corrupted files.