Gamer fails STAM roll, dies after 40-hour Diablo III stretch A sleep-deprived gamer has died after playing Diablo III for 40 hours without a break, prompting advice from developer Blizzard about moderating one's gaming habits. A Taiwanese teen known only as Chuang booked himself into an internet cafe's private room on Friday and spent the next two days playing Diablo III, apparently …
My son's of this minecraft generation. He'd play for days straight if we let him. The saving grace of that game (for me) is that it allows you to run your own server. I set up a VM on my machine, taught him how to do remote desktop, poked a port in the router, and said "there ya go". He's now admin of his 'own server' for him and a few buddies, and he's got it running pretty well. So he's not just playing a game, he's learning how to run a box. Little steps...
Of course, now he wants me to move it to a real box with lots of RAM... Thankfully I don't have any nearby elevator shafts, large safes, or raised floor rooms... he's a bit of a PFY right now, but one day...
Hour #1: "The servers are busy at this time. Please try again later (error 37)"
Hour #2: "The servers are busy at this time. Please try again later (error 37)"
Hour #3: "The servers are busy at this time. Please try again later (error 37)"
Hour #4: "The servers are busy at this time. Please try again later (error 37)"
Hour #5: "The servers are busy at this time. Please try again later (error 37)"
Hour #6: "The servers are busy at this time. Please try again later (error 37)"
Hour #7: "The servers are busy at this time. Please try again later (error 37)"
Hour #8: "The servers are busy at this time. Please try again later (error 37)"
Hour #9: "The servers are busy at this time. Please try again later (error 37)"
Hour #10: "The servers are busy at this time. Please try again later (error 37)"
Hour #11: "The servers are busy at this time. Please try again later (error 37)"
Hour #12: "The servers are busy at this time. Please try again later (error 37)"
Hour #13: "The servers are busy at this time. Please try again later (error 37)"
Hour #14: "The servers are busy at this time. Please try again later (error 37)"
Hour #15: "The servers are busy at this time. Please try again later (error 37)"
Hour #16: "The servers are busy at this time. Please try again later (error 37)"
Hour #17: "The servers are busy at this time. Please try again later (error 37)"
Hour #18: "The servers are busy at this time. Please try again later (error 37)"
Hour #19: "The servers are busy at this time. Please try again later (error 37)"
Hour #20: "The servers are busy at this time. Please try again later (error 37)"
Hour #21: "The servers are busy at this time. Please try again later (error 37)"
Hour #22: "The servers are busy at this time. Please try again later (error 37)"
Hour #23: "The servers are busy at this time. Please try again later (error 37)"
Hour #24: "The servers are busy at this time. Please try again later (error 37)"
Hour #25: "The servers are busy at this time. Please try again later (error 37)"
Hour #26: "The servers are busy at this time. Please try again later (error 37)"
Hour #27: "The servers are busy at this time. Please try again later (error 37)"
Hour #28: "The servers are busy at this time. Please try again later (error 37)"
Hour #29: "The servers are busy at this time. Please try again later (error 37)"
Hour #30: "The servers are busy at this time. Please try again later (error 37)"
Hour #31: "The servers are busy at this time. Please try again later (error 37)"
Hour #32: "The servers are busy at this time. Please try again later (error 37)"
Hour #33: "The servers are busy at this time. Please try again later (error 37)"
Hour #34: "The servers are busy at this time. Please try again later (error 37)"
Hour #35: "The servers are busy at this time. Please try again later (error 37)"
Hour #36: "The servers are busy at this time. Please try again later (error 37)"
Hour #37: "The servers are busy at this time. Please try again later (error 37)"
Hour #38: "The servers are busy at this time. Please try again later (error 37)"
Hour #39: Logged in!
Hour #40: RIP
Hmm, got an old copy of diablo 2 recently, found a certain similarity.
(install).
Click.
Click. Click.
Click.
Click. Click. Click.
Click click click click click click click click....
...click click click click clickclickclickclickclickclickclick clickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclick clickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclick clickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclick clickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclick clickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclickclick clickclickforseveralhours
"lord, this is brain-destroyingly dull. People paid for this?"
(uninstalls)
Anyway, I feel sorry for the guy's family.
This post has been deleted by its author
It might be reasonable for the game server to kick you off for a certain amount of time (say 30 minutes) if your account has been active beyond the safe limits stated in their games terms and conditions: I'm sure they must have some sort of guidance on this kind of thing? Obviously you would need to be (moved to) somewhere 'safe' in the game. Or perhaps all the NPCs should start shouting "You must drink some water" and "Go eat something" or "Get some sleep"
Or is there a fear that this might be the developer accepting some sort of legal responsibility? If somebody dies because they fall asleep at the wheel of their car from driving for too long then I assume it's not the car manufacturer's fault?
whats strange is how these people can go on ignoring the bodys signals. i.e needing to pee/eat/drink. sure we have all lost a couple of hours thinking "i'm thirsty i should get a drink but one more turn/level/round first" but 40 hours of dehydration/hunger/ cramping up? and all this for what? a few extra bits of loot that would have still been just as likely to drop if you took a 5 min bathroom break every few hours?
I recall playing several older games that put up a nag screen or similar if you were playing after 12 or had been playing for more that 4 or 5 hours (I'm pretty sure Dungeon Keeper was one of them). Haven't noticed any recent games doing that, though.
John, since you're here commenting, you must be much more intelligent, or at least have an understanding of the nutritional needs (etc.) of your body. The recently deceased-because-he-was-stupid gamer deserves nothing.
My personal record is 156 hours awake; of course, I ate/drank/etc during that 6 1/2 day stretch.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
