Gamer fails STAM roll, dies after 40-hour Diablo III stretch
Way to go, dude
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 without food or naps.
When an employee came in on Sunday morning to make sure everything was in order, Chuang was found slumped over a table, seemingly from sheer exhaustion. The gamer stood up after being woken but suddenly collapsed. He was rushed to hospital where he later passed away.
Chuang's death has yet to be explained, however authorities suspect it was caused by cardiovascular strain or a blood clot, a result of spending such long period of time sitting immobile.
I see dead people
Then again, with Diablo III so repetitive towards the end of the game - a fact even Blizzard admits - perhaps the poor lad was simply bored to death, literally.
The developer released a statement in regard to Chuang's demise. "We're saddened to hear this news, and our thoughts are with his family and friends during this difficult time. We don't feel it would be appropriate for us to comment further without knowing all of the circumstances involved," it said, before commenting further:
"While we recognise that it's ultimately up to each individual or their parent or guardian to determine playing habits, we feel that moderation is clearly important, and that a person's day-to-day life should take precedence over any form of entertainment."
Earlier this year, another Taiwanese gamer was found dead beside an internet cafe' PC after a similar marathon stint on the popular League of Legends game. ®
COMMENTS
Doesn't meet the criteria.
Darwin awards are for people who improve the gene pool by removing themselves from it.
I don't think the sort of guy who plays Diablo III for 2 days straight was ever likely to be contributing much to that pool.
Bloody kids
The youth of today have no understanding about how their bodies work.
It's a bloody Fortitude save, not a STAM roll. Jesus.
Re: Died of shock
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
Re: Some responsibility on the game developer
BULLCRAP! How about a little PERSONAL RESPONSIBILITY?
If the idiot was so stupid to not sleep or eat for 40 hours...then too f*cking bad. The world is better off without him.
A bit tragic but if it wasn't D3, it would have been some other than game or interest. He obviously thought, like a lot of kids that he was invincible. The same reason boy racers wrap their twatmobiles round trees!
