Slashdot Mirror
The Myth of the 40 Hour Game
Over at Wired, Clive Thompson talks about the myth of the 40 hour game, the typical length of time listed on the side of a game box nowadays. Mr. Thompsons discusses the ways in which that estimate fails to jive with reality. From the article: "This game offers about 40 hours of play. This is precisely what I was told by Eidos — and countless game reviewers — when I picked up Tomb Raider: Legend earlier this year. As I gushed at the time, Legend was the first genuinely superb Lara Croft game in years... I was hooked — and eager to finish the game and solve the mystery. So I shoved it into my PS2, dual-wielded the pistols and began playing... until about four weeks later, when I finally threw in the towel. Why? Because I couldn't get anywhere near the end. I plugged away at the game whenever I could squeeze an hour away from my day job and my family. All told, I spent far more than 40 hours — but still only got two-thirds through."
RTFA. The very least thing he complains about is length. So some cliffnotes are in order.
His points (as a person with a job, life, kids) are:
- puzzles many times take him much longer than kids in the 6-17 range he compares himself to.
- he compares in-depth games to his job, dumping information in and out of his mental RAM doesn't get him very far. See: late-night or off-shift coders who work to avoid users/meetings/interruptions.
- he understands the hardcore vs casual design problem.
TFA isn't even that long but his really good point (imho) aren't in the title (which is Gamer not Game). But if you just read the title, then you miss the point. Great read, critical hit close to home.